Reputation
Next tag badge:
367/400 score
84/80 answers
Badges
5 50 92
Newest
 Good Answer
Impact
~1.2m people reached

May
29
revised Execute output from query
added 404 characters in body
May
29
answered Execute output from query
May
29
revised Restoring database backup file gives access error
added 14 characters in body
May
29
revised Restoring database backup file gives access error
edited tags; edited title
May
29
answered Restoring database backup file gives access error
May
28
awarded  Nice Answer
May
28
revised Query without having to specify table's schema
added 4 characters in body
May
28
revised What's the point of WHERE 1=2 for SELECT INTO table query
added 49 characters in body
May
28
comment SQL Server 2008 sp_send_dbmail
Take a look at the sysmail_allitems table (msdn.microsoft.com/en-us/library/ms175056.aspx). What is the sent_status for that test email to the bad email address?
May
28
revised Copy database to local from server
edited title
May
28
answered Copy database to local from server
May
28
revised Check server activity with code
edited title
May
27
answered How to restore SQL Server database with mirroring
May
24
revised Query without having to specify table's schema
deleted 2 characters in body
May
24
answered Query without having to specify table's schema
May
24
comment Partial rollback doesn't decrement trancount
+1 for "there is no such thing as a nested transaction."
May
23
comment When should I use the shrink option
No problem, glad to help!
May
23
comment When should I use the shrink option
file continues to be 10 GB. In that case, you may want to shrink that file in order to reclaim space to have free space left on that drive. Again, this is just a simple example.
May
23
comment When should I use the shrink option
It's not that the log is no longer usable (as it'll always be so). Say your transaction log is on a 10 GB volume. During normal operations and routine log backups, your log file is usually 500 MB. But say a transaction log backup job fails consistently, or there is an open transaction. These situations will prevent SQL Server from reusing the transaction log, and depending on your autogrowth settings your log file could fill up the drive (also depends on the maxsize setting). So say your log file grows to 10 GB filling up the drive. You alleviate the problem, but your physical NTFS 1/2
May
23
revised Dropping and recreating indexes
edited title