Viewing 15 posts - 10,171 through 10,185 (of 22,219 total)
Not just zero pages. It should have a page limit so that the defrag is across an index that's greater than 1 extent or the defrag just won't work. I...
"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
January 11, 2013 at 8:16 am
GilaMonster (1/11/2013)
Grant Fritchey (1/11/2013)
I think Gail would spontaneously combust over a few of the statements I saw.
Almost, on a few occasions. I've had cases where people quote that site 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
January 11, 2013 at 8:14 am
The only way I know how to do this would be to modify the timeout for the connection. You could enable the query governor to limit long running queries 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
January 11, 2013 at 6:53 am
You can use what is called a derived table. This means your first select statement is treated like a table and then you can join that to your next table....
"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
January 11, 2013 at 5:50 am
Are the partitions on a single disk? If so, you've just added the overhead of having to filter your data but you're not benefitting from having multiple disks to offset...
"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
January 11, 2013 at 5:44 am
It could be fragmentation, but more likely is either slow disks or disk contention. Check your wait statistics to see what is causing the system to slow down. See if...
"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
January 11, 2013 at 5:27 am
It's probably because the SELECT criteria only converts the information returned, but the WHERE clause, since it's a function on a column which means a complete scan of the table...
"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
January 11, 2013 at 5:26 am
Since you're moving to 2012, you can use distributed replay to test the new server. That'll work better than using Profiler. And, it's a great new tool in your 2012...
"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
January 11, 2013 at 4:54 am
It really does depend on the indexes and statistics on the table, but most of the time, option 2 is the right way to go. And when it isn't 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
January 11, 2013 at 4:40 am
After seeing Lynn's comments about SQL Server Performance, I read through... well, attempted to read through a couple of articles over there. I have to ask, who is running 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
January 11, 2013 at 4:32 am
That is not behavior I've run into before. Is there something special about your domain setup? I use domain specific logins for all my installations and haven't seen this type...
"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
January 11, 2013 at 4:08 am
I'd go with 2012. I still haven't finished upgrading to it here, but it offers opportunities that don't exist in 2008R2. But, you do have to deal with the crap...
"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
January 10, 2013 at 7:13 am
I'm not comfortable with any of those answers. A is somewhat true, but so is B. I'd have to choose E if pushed, but I'd want to have a long...
"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
January 10, 2013 at 7:12 am
None of the above.
Use the source control system that has all the database objects in it to run an automated build for the new people. But not to create 10...
"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
January 10, 2013 at 7:08 am
You can also create extended events to capture all logins.
"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
January 10, 2013 at 7:05 am
Viewing 15 posts - 10,171 through 10,185 (of 22,219 total)