Viewing 15 posts - 8,536 through 8,550 (of 22,226 total)
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
I think Igor largely nails it. I'd concentrate the aggregations into the view. That's the stuff that is going to be the most costly in your queries, so doing 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 27, 2014 at 4:33 am
I don't that Profiler is the best tool. In fact, Profiler, the GUI, is a somewhat dangerous tool to point at a production server. It can actually cause performance problems.
My...
"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 4:30 am
Assuming you're trying to replicate the production environment, I'd have whatever type of fragmentation management you have in production in place on the test machine. Same with statistics maintenance 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 27, 2014 at 4:22 am
Ola and Michelle. Anything else is a waste of time.
"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 26, 2014 at 4:46 pm
Cost alone? Nah, surely not. Not that SQL Server is cheap any more, it isn't, but DB2 is hardly the low cost alternative. It's either politics, or some other piece...
"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 26, 2014 at 4:44 pm
Oops. Instead of server there at the end, I should have said instance. That's more accurate.
"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 26, 2014 at 4:43 pm
Viewing 15 posts - 8,536 through 8,550 (of 22,226 total)