If the user has read-only access to the database(s) they will have read-only permissions regardless of the tool they use to connect.

I am not a lawyer, and I don't play one on TV, but I think public forums and newsgroups are in the "public domain."  But while there may not be legal...

It's been a while since I have dealt with log shipping, but when we were using it, we decided that it would be easier to reconfigure the application to point...

Yes, and no.  Generally speaking you don't need to keep transaction log backups that were made prior to the last GOOD full backup.  However, some mistakes aren't caught in a...

I generally limit my resume to relevant experience.  That doesn't mean that only those jobs in the same field make it on the resume.  But I try to highlight experience...

If I understand your question correctly, you would be better off parsing the xml using an xml parser (strangely enough) rather than using string functions in SQL Server to do...

I'd be willing to bet that the table is anything but "properly normalized", but taking your assertion at face value...

SQLDMO (which is what EM and QA Object Explorer use) is...

I have seen this before, the following article might shed some more light on the subject.

http://support.microsoft.com/kb/328551/en-us

How big is the database?  The transaction log will have to grow large enough to accomodate the largest transaction.  In many cases this winds up being reindexing. 

Generally, you don't...

Job security is nice, but in my experience, there are too many truly productive things that don't get done because so much effort goes into supporting junk systems.

I'm much more...

That depends on what you are trying to accomplish...  You can set up a linked server to 2005 just using the oledb client.  We have encountered some strange behaviour when...

You will not be able to connect to 2005 via the 2000 client tools (Enterprise Manager, Query Analyzer, SQL Profiler etc...)  You can use the 2005 tools to connect to...

Actually, I shouldn't have used the term "problem" as it is a "feature" that really does increase flexibility, but that power does come at a cost.

If anything this problem is worse in 2005.  With the user/schema separation, you will have to plan and think about security much more than previously.

Never seen that one... but for something like that, it doesn't take much of your time to be lost before the call to PSS is well worth it...