Viewing 15 posts - 8,956 through 8,970 (of 22,219 total)
Thanks. That was a fun discussion. Greg is a great guy.
"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 7, 2014 at 4:16 am
EXACTLY!
It's going to be a hybridized world, partially hosted locally, partially externally, and partially through various services. It's happening right now and shows every sign of accelerating. I am all...
"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 6, 2014 at 5:08 am
TheSQLGuru (2/5/2014)
Grant Fritchey (2/5/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 5, 2014 at 9:30 am
Assuming I understand the question, yes, that's not only possible, it's the right way to get the job done.
"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 8:37 am
But the FAST (50) hint is also going to impact what gets delivered by the optimizer. It's likely to see what you're seeing, a seek where a scan would serve...
"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 6:10 am
The update statement you have is modifying the row where the ID = 9. If you want to move the value from 27 to 9, try writing an UPDATE FROM...
"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 6:05 am
If you know you have a query that is causing performance problems, I'd start by looking at the code to see any of the common issues and then I'd look...
"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 6:03 am
I have used, as a DBA, Idera, Spotlight, Foglight, Operations Manager and SQL Monitor. Currently, I work for Red Gate, so my view might be a little biased. All these...
"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:58 am
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
Viewing 15 posts - 8,956 through 8,970 (of 22,219 total)