Viewing 15 posts - 8,971 through 8,985 (of 22,226 total)
Not sure without seeing what is being blocked. One recommendation, get rid of the drop table statement entirely. Let SQL Server clean it up on its own. Not saying that...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2014 at 5:45 am
On any query while looking at the execution plan, the costs will add up to about 100% (sometimes a little less, occasionally a lot more, it's a bug). So seeing...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2014 at 5:37 am
Thanks for all the excellent replies about the clustered index/heap thing. You've all more or less reinforced my opinions of things through some great factual discussions. That's why I love...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 10:41 am
sqlmunkee (2/4/2014)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 8:44 am
It works fine on 2012. You might also consider other 3rd party products for compression such as Red Gate SQL Backup[/url].
By the way, there is native compression of backups on...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 7:54 am
I'm not aware of hitting issues with ms_foreachdb skipping databases. But, you're right, it's technically unsupported by Microsoft, so could go away at any time. It's just a cursor, so...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 7:51 am
Not that I'm aware of. Generally, for full backups, I do one of two things, run DBCC before them, or use them to run DBCC (and then run a physical...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 7:41 am
lisa.randles (2/4/2014)
Grant, I'll see what I could do with the brackets, although I'm pretty green...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 7:39 am
Over my head. Could use some help here. I truly hate the hardware aspects of SQL Server, especially when combined with VMs.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 6:33 am
Oh, we've got a VM on top of this... yikes. That does complicate things. Now I'm really unsure. Your explanation may be accurate, but... let's see if I can get...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 6:29 am
It really depends on what you're attempting to audit. If you want to see data changes, the best bet is to implement change data capture (CDC). If you want to...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 6:03 am
After the fact like this... You can try querying sys.dm_exec_query_stats to see if you have any queries that stand out as using a lot of CPU. Otherwise, the best bet...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 6:00 am
If the inconsistencies are internal to the database and not an external storage problem, your approach might (huge, huge, word) be a good approach. Running repair_allow_data_loss is a complete gamble...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 5:58 am
Why not modify the code to use brackets. That will narrow down the issues around naming & special characters.
And I'm with the others. What is the purpose of this code?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2014 at 5:55 am
SQLRNNR (2/3/2014)
WayneS (2/3/2014)
SQLRNNR (2/3/2014)
rodjkidd (1/29/2014)
Talking of Grant, did anyone see the picture of him on the SQLCruise yesterday- almost as red as the livery of that company he works for!Rodders...
Why...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 3, 2014 at 4:11 pm
Viewing 15 posts - 8,971 through 8,985 (of 22,226 total)