Viewing 15 posts - 6,271 through 6,285 (of 22,228 total)
The thing to do might be to hire a consultant to do the job description and the interviews for you. As Jeff says, you've split the difference between a BI...
"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
April 24, 2015 at 6:22 am
I've seen a 5 minute compile time on queries, so they can run for a very long time indeed. If you're looking at the plan, you can see the compile...
"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
April 24, 2015 at 6:15 am
Sounds great. Nicely 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
April 23, 2015 at 10:09 am
Nesting views is a really common code smell and should be avoided. It's best to write each query as a stand-alone entity and not attempt code reuse through views or...
"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
April 22, 2015 at 2:14 pm
aaron.reese (4/21/2015)
They also have a data compare so that you can script config and static data
Their tools also integrate very nicely into SSMS and SQL compare can handle...
"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
April 21, 2015 at 11:09 am
More reasons why system_health is better.
"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
April 21, 2015 at 9:00 am
Your best bet if you want to capture parameters is to use Extended Events[/url]. You can't capture parameter values querying the cache.
For lost more on query tuning, see the books...
"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
April 21, 2015 at 6:44 am
I would absolutely advocate for using the mathematical calculations supplied by Microsoft in the link above. But, for a ballpark guess when doing initial evaluations, 3-5 times the data is...
"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
April 20, 2015 at 9:18 am
SQLRNNR (4/19/2015)
Eirikur Eiriksson (4/19/2015)
Grant Fritchey (4/19/2015)
Eirikur Eiriksson (4/19/2015)
spaghettidba (4/19/2015)
"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
April 20, 2015 at 6:30 am
Eirikur Eiriksson (4/19/2015)
spaghettidba (4/19/2015)
Did I say...
"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
April 19, 2015 at 3:43 am
When querying the wait stats, the real key is going to be getting them before and after the backup to understand where and why things are running slow. Also, 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
April 17, 2015 at 9:59 am
I really dislike the native intellisense, so...
I haven't seen major slow downs, but, make sure you have the latest SP and maybe the latest CU installed on top of your...
"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
April 17, 2015 at 8:57 am
It actually might be easier to just use T-SQL rather than the GUI. It's much more straight forward to RESTORE:
RESTORE DATABASE 'ANewName'
FROM DISK = 'e:\backups\myotherdb.bak'
WITH MOVE 'logicaldataname' to 'd:\data\anewname.mdf',
MOVE 'logicallogname'...
"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
April 17, 2015 at 8:52 am
Favorite answer, it depends.
Check the execution plan. It might do TOP on its own. In which case, ignore me. But if it's doing aggregate functions there, modifying it could 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
April 17, 2015 at 7:23 am
Instead of MAX, try a TOP 1 with an ORDER BY.
"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
April 17, 2015 at 7:13 am
Viewing 15 posts - 6,271 through 6,285 (of 22,228 total)