Reputation
1,956
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
4 23
Newest
 Yearling
Impact
~71k people reached

Jul
8
revised Is select * still a big no-no on SQL Server 2012?
added 16 characters in body
Jul
8
comment Is select * still a big no-no on SQL Server 2012?
@CraigYoung The performance problem may be simplified in my description, but I don't think that it is an over-simplification. Performance problems from * can only occur if the * appears in the top-level select. As long as the top-level select explicitly lists only the columns desired, * appearing anywhere else cannot cause performance problems. However, I will edit my reply to clarify that it is only a potential performance problem.
Jul
8
comment Is select * still a big no-no on SQL Server 2012?
@CraigYoung Yes0, the View's Columns issue is the binding problem I mentioned in the footnote.
Jul
3
answered TSQL- Column DataType Length
Jul
3
revised TSQL- Column DataType Length
code formatting
Jul
3
suggested approved edit on TSQL- Column DataType Length
Jul
2
comment Is select * still a big no-no on SQL Server 2012?
@Damien_The_Unbeliever Agreed, good point.
Jul
1
awarded  sql-server
Jun
30
revised Is select * still a big no-no on SQL Server 2012?
added 235 characters in body
Jun
30
revised Is select * still a big no-no on SQL Server 2012?
added 1596 characters in body
Jun
30
answered Is select * still a big no-no on SQL Server 2012?
Jun
12
comment Cannot add foreign key constraint while creating table
If you have solved this yourself, do not change the title. Rather, post what you did to solve it as an answer, then ACCEPT your own answer.
May
14
comment SQL agent job, why is the job history showing that a step is still running even though the job has completed
What's the actual query to you are executing that is giving these results?
Apr
23
comment Fixing a corrupt Log File in small downtime window
That worked great, thanks!
Apr
23
accepted Fixing a corrupt Log File in small downtime window
Apr
22
comment Fixing a corrupt Log File in small downtime window
@MarkStorey-Smith Not a problem, they are aware in great detail and in writing of my position on this matter. At the moment, the hosting provider is on the hook.
Apr
22
comment Fixing a corrupt Log File in small downtime window
@MarkStorey-Smith Perfectly right. Unfortunately, disputes with the hosting provider are limiting the options. That's about as diplomatic as I can put it.
Apr
22
comment Fixing a corrupt Log File in small downtime window
@AaronBertrand Yes, those qualification are true and intended as implicit in my statement above. (I had qualified these originally, but ran out of room and had to edit for brevity)
Apr
22
comment Fixing a corrupt Log File in small downtime window
However, the ATTACH_REBUILD_LOG option is attractive as it seems like this approach could be both faster and smaller. thanks..
Apr
22
comment Fixing a corrupt Log File in small downtime window
That's not quite right. If a DB full backup backed up both the entire data and log files, then they would have to be almost twice as large in most cases. From size alone you can tell that a BAK does not have both the MDFs and all of the LDFs too. The article says that the full backups only contain "sufficient transaction log records" to allow rolling forward the active transactions and to roll back the uncommitted ones. So, it should only be capturing the current transactions in the backup, though I suppose there's the chance that old corrupt log records are also be picked up.