Reputation
10,538
Top tag
Next privilege 15,000 Rep.
Protect questions
Badges
18 44
Newest
 Revival
Impact
~536k people reached

Jul
31
comment Should I update to sql server 2008 sp2 before restoring the db's or do the update after?
Not an answer but a suggestion: if you can I would push to 2012 or 2014 rather than just to 2008r2 (especially if you have yet to fully test your code against 2008r2). This will save you needing to test your application against a new version again when 2008r2 falls out of support and gives you access to 2012's nice additions (lag and lead window functions which can make certain report type queries massively more efficient, and so forth) should you need them.
Jul
30
comment SQL Server storage limits on Azure
Of course then you've got to work out how you are going to manage backups of that data...
Jul
29
awarded  Revival
Jul
28
awarded  Nice Answer
Jul
28
answered Primary Key choice on table with unique identifier
Jul
28
awarded  Caucus
Jul
27
comment Dividing in SQL
Avoid the use of FLOAT and REAL unless that is explicitly what you want, or you will fall into traps due to floating point approximations. See theregister.co.uk/2006/08/12/floating_point_approximation and docs.oracle.com/cd/E19957-01/806-3568/ncg_goldberg.html (amongst other references) for more information.
Jul
27
comment How to do superscript in SQL Server 2012 query?
Good catch @MarkSinkinson. BTW: you can edit resposes directly to fix errors like that. If you don't have the reputation required to make the change directly your edit will be proposed and other users asked to confirm it.
Jul
27
revised How to do superscript in SQL Server 2012 query?
edited body
Jul
27
answered How to do superscript in SQL Server 2012 query?
Jul
24
revised How can I optimize a mysqldump of a large database?
Extra words to make clear that buffering through pv or similar can be done either as well as compression or separately.
Jul
16
comment SQL Server - Alter table vs drop and create
@AaronBertrand: That rings a bell, it was certainly views using SELECT * where we experienced problems if a view (or table?) they depended on changed such that column ordering or types differed. IIRC it wasn't a problem if ALTER VIEW was used instead of DROP followed by CREATE.
Jul
15
comment SQL Server - Alter table vs drop and create
I've certainly seen the problem of queries returning incorrect columns after views have been dropped and recreated, until the affected views were forced to be reassessed (via sp_refreshview), though off the top of my head I can't name an example where it has happened with a table drop and rebuild so perhaps the issue is more specific than I have stated above. This may also be something that has improved in recent versions though: most of our clients are still running 2008r2 or in some cases 2005. I shall have to research further when time permits and update my response.
Jul
15
answered SQL Server - Alter table vs drop and create
Jul
15
comment SQL Server Slowdown?
I would suggest a larger value than 64Mb. Small a values could result in significant external (filesystem level) fragmentation which could impact performance. While 64Mb isn't exactly small, it is far from large these days.
Jul
15
answered SQL Server Slowdown?
Jul
15
comment SQL Server Slowdown?
Regarding memory use for each instance: if explicit settings have not been configured all the instances will try grab all the memory they think they need and won't really cooperate with each other when it gets full: so if dev and stage instances are using a lot of RAM then the production instances may not be able to allocate what they need. Set the production instances to allocate at least as much as they need for good running and set the others to make sure that much is always spare for the live instances to take. Or separate production systems from dev/stage/test ones.
Jul
15
revised Database size - MDF too large?
Added not about the potential space wasting effect of bad clustered key/index choice
Jul
15
revised When is it OK to shrink a Database?
Altered "PK order" recommendation to the more correct "clustered index order"
Jul
9
awarded  performance