Viewing 15 posts - 8,776 through 8,790 (of 22,232 total)
I really don't care what naming standards we have. Let's just make them clear and let's enforce them. After that, it's all good.
I have a presentation where I spend about...
"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
March 6, 2014 at 4:05 pm
SQL Guy 1 (3/6/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
March 6, 2014 at 3:51 pm
If it's an update statement, you could be seeing contention from other resources doing reads at the same time as you're trying to modify the data. That's a pretty classic...
"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
March 6, 2014 at 12:18 pm
Abu Dina (3/6/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
March 6, 2014 at 11:09 am
Abu Dina (3/6/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
March 6, 2014 at 9:14 am
Just backing up what's been said. You can get extremely granular on the security, and I'd get as granular as possible. If you can, limit all access to the data...
"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
March 6, 2014 at 7:58 am
Usually, but not always, ASYNC_IO_COMPLETION is caused by client side slow downs. The secondary cause is from network processes. But, in this case, it sounds like an issue with the...
"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
March 6, 2014 at 7:55 am
Ed Wagner (3/6/2014)
MysteryJimbo (3/6/2014)
Ed Wagner (3/6/2014)If you've ever driven in the Great Smokey Mountains or especially the Rocky Mountains, it is absolutely beautiful, but it is anything but straight and...
"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
March 6, 2014 at 6:55 am
Deadlocks are fundamentally a performance problem. So, yes, indexing may help. It's hard to say without all the specifics of your code and structures, but it's pretty likely. You'll also...
"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
March 6, 2014 at 4:47 am
We had a situation where we needed to provide a database for testing and development that matched production, but, didn't have sensitive data (trust me, you want to clean up...
"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
March 6, 2014 at 4:45 am
It's not about what the 'sa' account has access to. It's about what the account that SQL Server is running under has access to. That account determines what can be...
"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
March 6, 2014 at 4:36 am
MysteryJimbo (3/6/2014)
Koen Verbeeck (3/6/2014)
MysteryJimbo (3/6/2014)
Koen Verbeeck (3/5/2014)
Pfff, than you have never been in Belgium before 😀
If we wouldn't be having the most traffic jam congested cities in the world, you...
"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
March 6, 2014 at 4:31 am
Ran into this again, 6 years later. Glad I asked this question online so I could find the answer again.
"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
March 5, 2014 at 12:21 pm
Jacob Pressures (3/5/2014)
So you guys suggest I should avoid that syntax? OkI got it from doing debug on the following statement:
EXEC sp_help;
GO
Ha! Awesome. That would explain why it's not...
"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
March 5, 2014 at 12:05 pm
It's a non-standard use though. I don't know that I'd actively rewrite everything I found that way, but I'd certainly discourage any new code being written like 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
March 5, 2014 at 10:23 am
Viewing 15 posts - 8,776 through 8,790 (of 22,232 total)