Viewing 15 posts - 12,646 through 12,660 (of 22,219 total)
Just saying you have a 300gb database with many users is not nearly enough to begin to make suggestions for what to do with that database. It's not even remotely...
"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 27, 2011 at 7:24 am
Brandie Tarvin (4/27/2011)
SQLRNNR (4/26/2011)
When did Brandie crack the top 25?Wait. What?
I'm in the top 25?
WHOO HOO! Steve, I'm glad my bribe worked! @=)
Well done. That's a serious milestone, especially considering...
"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 27, 2011 at 5:47 am
For that one query, yeah, it sounds like it needs more up to date statistics.
"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 26, 2011 at 3:49 pm
Take a look at "SQL Server Team-based Dvelopment." [/url]It's not going to tell you how to move large amounts of data. That's a different issue entirely.
"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 26, 2011 at 3:46 pm
ChrisM@home (4/26/2011)
Is it me, or are the posted questions from developers working on medical systems a little worrying?
I used to work for a medical software company. it was a nightmare...
"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 26, 2011 at 3:16 pm
Ninja's_RGR'us (4/26/2011)
So plan B would be? Collect a trace and sum up to reads / writes columns?
I think I'd call it step 2 of Plan A, but yeah.
"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 26, 2011 at 6:51 am
Ninja's_RGR'us (4/26/2011)
Grant Fritchey (4/26/2011)
Ninja's_RGR'us (4/26/2011)
Grant Fritchey (4/26/2011)
You need a fundamental assessment of the 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
April 26, 2011 at 6:26 am
Ninja's_RGR'us (4/26/2011)
Grant Fritchey (4/26/2011)
You need a fundamental assessment of the system done. It sounds...
"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 26, 2011 at 6:17 am
I would look first at the SQL Server error log. You can see that in the Management folder in SSMS. I would also look at the Event Viewer on 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
April 26, 2011 at 6:03 am
Referential integrity is also a speed issue. It speeds things up. Here's a blog post outlining why[/url].
You need a fundamental assessment of the system done. It sounds like you don'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 26, 2011 at 6:00 am
Absolutely possible. Pretty common task really. It's an easy way to get a database from one system to another. When you run the restore operation you'll probably have to use...
"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 26, 2011 at 5:56 am
Without knowing lots more about your system, there's no way to know why it's running longer. It could be parameter sniffing. It could be blocking. It could be a hundred...
"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 26, 2011 at 5:54 am
nico van niekerk (4/26/2011)
"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 26, 2011 at 5:45 am
I have to say, after almost 3 months of working from home, I'm still not used to it. However, I love it. I'm getting tons of work done. I get...
"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 26, 2011 at 5:39 am
David Burrows (4/25/2011)
Grant Fritchey (4/25/2011)
... I usually bump mine up to 35 or so on OLTP systems.Is that a general rule of thumb?
Are there any consequences to that setting?
Not really....
"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 25, 2011 at 8:35 am
Viewing 15 posts - 12,646 through 12,660 (of 22,219 total)