• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Need a 1st Contract

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #11
    Blimey spacecadet, you mean you're a DBA who actually makes it easy for people to use the data in your databases?

    I think that's where you're going wrong. Everybody knows a DBA's supposed to think up every excuse to forbid that sort of thing wherever possible.

    Comment


      #12
      Originally posted by thunderlizard
      Blimey spacecadet, you mean you're a DBA who actually makes it easy for people to use the data in your databases?

      I think that's where you're going wrong. Everybody knows a DBA's supposed to think up every excuse to forbid that sort of thing wherever possible.
      That is why the data is there
      First DBA i worked under was a right grumpy sod though, unhelpful to the point where its the only thing i really remember about him - promised myself to be the opposite to everything he was when i got to DBA status.
      Coffee's for closers

      Comment


        #13
        Originally posted by cswd
        Thats usual from DBAs - they have to be nazis and have that persona permanently as the company tends to rely on them more than anyone else. One cock up means you lose the DB since the last transaction log backup/nightly which could be a fatal for an ecommerce company for example.

        Your personality will slowly change to that over the years.

        When I'm doing my DBA thang, I'm equally as Nazi. Mind you the same when I'm writing code.

        I tend to not let people near a DB by security restriction unless it's via stored procedures I've thoroughly tested myself.
        OK, you mentioned the nazis. Stop this thread!

        Comment


          #14
          Err...

          How secure is it getting IIS and SQL working together to blat out XML....always scared the hell out of me....?!
          (not talking about the FOR XML obviously) but the IIS extensions....

          Comment


            #15
            Originally posted by Perhentian
            How secure is it getting IIS and SQL working together to blat out XML....always scared the hell out of me....?!
            (not talking about the FOR XML obviously) but the IIS extensions....
            OK - its not very secure by default but then this is Windows :P

            Theres two other things that I did with the XML support for IIS in SQL Server

            a. Set the config so that only the XML templates that you define yourself as DBA may be accessed. The XML templates contain the SQL queries to run and handle any incoming parameters. This is actually pretty good as the templates allow you to do a lot of XML type stuff and pass the parameters the URL easily. However the templates are just stored on the disk and not within the database structure.

            b. If its only 1 server (or computer) that needs access you can lock down access to limited IPs
            Coffee's for closers

            Comment

            Working...
            X