Viewing 15 posts - 8,371 through 8,385 (of 22,219 total)
The thing I'd look to are the wait statistics. What's causing the system to slow down? That will tell you if you are stuck on I/O or if it's something...
"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, 2014 at 4:12 am
I'm pretty sure there's no way to trace by JobId. But, you can trace by application name, so that will make it so you only ever get calls from SQL...
"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, 2014 at 4:21 pm
You can get a bunch of information from the backup files themselves, all through T-SQL. I've got an article on it over at Simple-Talk[/url].
"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, 2014 at 4:14 pm
Steve has largely nailed it. Be cautious using extended events to capture all statements though. That can be a ton of information.
Now, if you're running SQL Server 2014, you can...
"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, 2014 at 10:29 am
Probably a double hop on Kerberos and I was going to link to the same article. That's the place to go.
"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, 2014 at 10:23 am
Again, for PDW, I strongly advise you track down information from PragmaticWorks. They're the experts. Here's their web site.[/url]
"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 18, 2014 at 3:34 pm
Yeah, I've applied to Maine, but no word on if I got picked. I'm doing a pre-con at Albany, so I'm pretty sure I'm picked there. See you at both!
"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 18, 2014 at 3:32 pm
In general, I would consider this a very dangerous position. You may have dirty data in your systems and you won't know it.
Now, you may be in one of...
"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 18, 2014 at 12:37 pm
PDW might be a little different. I'm not sure. I've never worked with it. You might be better off tracking down someone from Pragmaticworks. They're the real PDW experts.
"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 18, 2014 at 12:13 pm
ramana3327 (4/18/2014)
So depends on the user seeks count, we can get idea about the dropping of the Index.
Suppose if you have index1 with one key column and index2 with...
"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 18, 2014 at 11:27 am
Yeah, Brandie has a good point. Reports can usually afford to wait a bit. Active OLTP systems can't.
"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 18, 2014 at 6:39 am
I'm not crazy about either approach. I prefer what you've done in the first approach. An employee has one or more salaries, so the Employee table (Not sure I'd call...
"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 18, 2014 at 5:09 am
Since you're working for a non-profit, I'd probably concentrate on keeping licensing costs down, so, as few servers as possible. While you can split your databases across multiple instances, 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
April 18, 2014 at 5:03 am
Oh, I don't know. I don't use SQL Server to send emails except for alerts. If I had to do that, I'd probably go to Powershell for it anyway. There'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
April 18, 2014 at 4:39 am
The only way to know indexes with a partial match are good or not is to evaluate those indexes with your code. There's no way to say for sure based...
"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, 2014 at 8:26 pm
Viewing 15 posts - 8,371 through 8,385 (of 22,219 total)