Set up a unique index if this is really important.

Agree with Sergiy. The error tells you the problem.

The other thing is this allows for scalability. If one client grows a lot, or becomes a query resource hog, you can easily move them to their own server.

This runs a query as a READUNCOMMITTED isolation level (http://www.sqlnewsgroups.net/group/microsoft.public.sqlserver.server/2007week16.aspx).

It allows you to read changed data as it doesn't set up locks on the tables, essentially dirty reads. Not necessarily...

You should read and understand what the log is doing. It protects your database and ensures integrity.

If this is production data, you should be running with full recovery mode and...

I see a note here about a post SP2 fix: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1481112&SiteID=17

https://forums.microsoft.com/technet/showpost.aspx?postid=1565323&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=1

It's a good point and we try to link back, though sometimes articles come with some time between them and many part series, so it's hard to link them all...

I'm always amazed how many people are weeded out from a simple test/quiz beforehand. At one point I made sure that I only interviewed people that got 75% or better...

SQL2K5 doesn't have compressed backups without a third party tool. SQL 2008 will have them in Enterprise Edition.

The hard part about seeing value in features is having a place where they can be used. This is where I think the developers and designers of SQL Server need...

First, you shouldn't grant sysadmin privleges. That's a huge security hole and unnecessary.

When replication runs, the account on the distributor logs into SQL Server just like any other user. So...

You should never shrink the data files if you can avoid this.

Shrinking the t-log does not invalidate the backup chain. http://msdn.microsoft.com/en-us/library/ms190749.aspx

The log file does not shrink after a log backup....

Here's another article: http://msdn.microsoft.com/en-us/library/ms190749.aspx

sorry to be late getting back, but I think IN reads better, especially when other people will see the code. Easy to make mistakes with OR.

If someone says OR is...

Please post the code and errors or results here. I don't really want to download and open a .doc from the forums.

You can use CHARINDEX/PATINDEX to find the $ signs....