There are several scripts available on line and if you Google for smart index rebuild scripts, I'm sure you'll find them. I use Andrew Kelly's script from SQL Magazine (with...

We implemented this by using an auto startup stored procedure that reads the computer's physical name and compares it to the last record stored in a table. If the names...

I do this all of the time using two batch files. The first one contains a %1 value for the server name, similar to below:

run.bat:

sqlcmd -S %1 -E -i "X:\script.sql"...

From the name of it, I'd have to take a wild guess and think that it's something a DBA came up with the gather wait stats of some sort. If...

After you take the transaction log backup, issue a CHECKPOINT statement in that database to flush the buffer to disk before you attempt to shrink it. I've had success in...

One other thing you can do is run a scheduled job to capture the output of sp_lock or it's equivalent dynamic management view. If the database is in use, a...

select * from loan where branchoffice NOT IN ('01','02')

I've used SQL Safe and LiteSpeed and have had very positive results with both doing backups directly to database disk files.

The only horror stories I've ever had related to this...

The other thing you might want to look at is usage of tempdb. SQL 2005 placed a significantly increased burden on tempdb and if the job is using a lot...

I still have SQL 2000 running one production system, most are SQL 2005 and a handful of my vendors are starting to support SQL 2008. Regardless of how quickly MS...

Have you applied the service pack to your client tools as well? And if it's a clustered server, you need to patch the client tools on the second node as...

It really depends on what you are trying to accomplish. Mirroring is a great disaster recovery solution, but because it works at the database level, you need to be careful...

All BACKUP LOG with truncate_only does is remove the commited transactions from the log. It doesn't do anything to make the size of the log data file smaller. You'll need...

Yes, I've added many of the same indexes to solve the same problem with deleting backup history data from msdb. Without the indexes, it took forever. With them, it ran...

Run the output of this script:

select 'sp_update_job @job_name = ' + ''''+ name + ''','

+ ' @owner_login_name = ''sa'''

from msdb..sysjobs

That should change them all to...