Viewing 15 posts - 8,536 through 8,550 (of 22,232 total)
It really is down to a unique setting for each alert, sometimes a unique setting for each server for each alert. There's no single answer to any of these. As...
"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 28, 2014 at 6:06 am
You can use ORDER BY along with TOP 1 to get the row that has the highest value.
"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 28, 2014 at 6:04 am
ShowPlan and StmtComplete are extremely resource intensive events to capture. Be very cautious doing this on a production system.
"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 28, 2014 at 6:03 am
Just remember that a clustered index is the table, so it may look very large, but that's because it's storing all 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 28, 2014 at 5:57 am
You're posting in the 2008 forum.
Not sure what you mean by batch delete. SET ROWCOUNT just limits the rows returned, but the query plan and the access of 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 28, 2014 at 5:39 am
The key is to make your queries run as fast as possible and keep the transactions as short as possible. So, if you're running an UPDATE statement, make sure it's...
"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 28, 2014 at 4:37 am
Instead of using SET ROWCOUNT, actually filter the data using some other criteria. SET ROWCOUNT is deprecated anyway and removed from the product in SQL Server 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 28, 2014 at 4:33 am
You've restarted the server, which rebuilds tempdb, and you're still seeing this? I strongly suspect hardware issues then.
"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 28, 2014 at 4:31 am
Cody K (3/27/2014)
Grant Fritchey (3/27/2014)
It can actually cause performance problems.
From what I've seen where people actually tested this out, it's no more than 10%. I guess there are environments where...
"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 28, 2014 at 4:06 am
jcrawf02 (3/27/2014)
We have a written test we use to weed out people who don't know the first thing about SQL (report writing position, not DBA stuff), it's pretty basic, but...
"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 27, 2014 at 3:52 pm
Came over here to answer your question and I find that Barry has already covered it better than I can. I'm out!
"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 27, 2014 at 12:46 pm
robin.pryor (3/27/2014)
Oh I understand that part. I liken a schema to a namespace or interface in OOP. My question is implementation-related
Sorry, I'm missing something then. I don't see a question...
"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 27, 2014 at 11:15 am
robin.pryor (3/27/2014)
I'm a SQL DBA and I've never given a crap about schemas. I know what they...
"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 27, 2014 at 11:08 am
robin.pryor (3/27/2014)
Sean Lange (3/27/2014)
robin.pryor (3/27/2014)
MarkusB (1/7/2009)
SQL DBA (1/7/2009)
I need differences between Roles, Schemas, Users and Logins. Can anyone help me. Thanks in advance
You call yourself SQL DBA and ask such...
"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 27, 2014 at 10:17 am
If you're going to use sys.dm_exec_requests to monitor, you'll have to capture it over and over again then write a query that shows the changes over time. As far as...
"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 27, 2014 at 6:20 am
Viewing 15 posts - 8,536 through 8,550 (of 22,232 total)