Reputation
28,205
Next tag badge:
92/100 score
25/20 answers
Badges
5 53 93
Newest
 Enlightened
Impact
~1.4m people reached

Apr
24
answered How best to maintain SQL log file sizes
Apr
24
comment Rebuilding, truncating etc SQL Server 2008 maintenance
Let the DBA do these DBA tasks... (just my opinion)
Apr
23
comment Can I drop and recreate a system extended stored procedure?
+1 wish I could +10 this answer.
Apr
22
comment Does SQL Server place shared locks on scanned records when using REPEATABLE READ
If what you're asking is if SQL Server places shared locks (S) on the data to be updated during an UPDATE, then the answer to that is no. SQL Server utilizes update locks (U) in order to read the data, and those are converted to exclusive locks (X) to modify the data. If a shared lock (S) was used, and wasn't relinquished for the duration of the transaction, the data modification part of the UPDATE would never happen.
Apr
22
comment Does SQL Server place shared locks on scanned records when using REPEATABLE READ
If you have an UPDATE statement, the exclusive locks (X) should be held for the duration of that transaction. Therefore, no, other transactions shouldn't be able to update any rows that have the exclusive lock.
Apr
22
awarded  Enlightened
Apr
22
awarded  Nice Answer
Apr
22
comment Can I shrink the transaction log file on a mirror database?
You can't connect to the mirrored database, therefore you can't run the DBCC SHRINKFILE on it. As for if you can fix your mirror session without removing mirroring on that database, there's a little more investigation that would have to take place there. It seems like it was suspended because of the file size. Have you tried resuming the partner?
Apr
22
answered Can I shrink the transaction log file on a mirror database?
Apr
22
comment How do I shrink the physical Transaction Log file when it's the principal in a mirror?
What does the secondary server have in the SQL Server error log? You should have a few error log messages dictating what happened to cause the mirroring session to be suspended.
Apr
19
revised Clustered vs Nonclustered Index
added 5 characters in body; edited title
Apr
19
comment Why use separate databases for high traffic/volume tables?
Also, the concurrency gains from separating reporting workloads vs. OLTP workloads can be significant. Not to mention the handful of points that @AaronBertrand brought up. In order to know they "why" of that database design, you need to talk to the developers that designed it.
Apr
19
comment Clustered vs Nonclustered Index
The gains that you will see from having the predicate on the index as well as filtered statistics will depend largely on how filtered it is. Without seeing more information regarding your table and data, it is hard to give exact recommendations. But my comments (and answer) are food for thought.
Apr
19
answered Clustered vs Nonclustered Index
Apr
19
revised Clustered vs Nonclustered Index
edited tags
Apr
19
comment Clustered vs Nonclustered Index
What RDBMS are you using? SQL Server? This sounds like a good candidate for a filtered index. Does the application really do a full column select (*)? Unless your nonclustered index is covering, you'll have key lookups.
Apr
19
comment IIS takes longer to run queries than SMSS
Capture the post execution plans of both the queries run through IIS and through SSMS. Post them here, if possible. But look for discrepancies and performance degraders.
Apr
18
revised Reducing Log Impact During Re-Indexing
edited title
Apr
17
comment Migrating from SQL Server 2005 to SQL Server 2008 R2 on a different box
+1 Great info. I personally revert to the SSIS solution. Between it's simplicity (it is extremely simple, even if you never work with SSIS), options, error handling, and reusability. Handles more than just logins and jobs for server-object migration. Thought worth mentioning. Again great answer, Aaron, as I've used to this process many times without a single issue.
Apr
17
comment Querying number of subscription to each publication
Is MSmerge_subscriptions what you're looking for? msdn.microsoft.com/en-us/library/ms188905(v=sql.110).aspx