Viewing 15 posts - 10,861 through 10,875 (of 22,219 total)
Developer Edition for 2008 was not free. It cost money. Maybe you're thinking of Express 2008.
"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
May 23, 2012 at 5:43 am
Can you post the execution plan for the query? It's hard to suggest improvements not knowing the structure of your system, tables, indexes, constraints, etc.
"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
May 23, 2012 at 5:41 am
If your database was created using the defaults, then it's in Full Recovery. This means you need to backup the log on a regular basis, at least once an hour...
"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
May 23, 2012 at 5:40 am
Piling on at this point, but that's one ugly naming convention so...
No, I've never seen one like that and wouldn't recommend it. In fact, I'd fight against it, kicking, biting...
"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
May 23, 2012 at 5:35 am
Also remember, those costs are estimates. They're the only numbers you have, so you must use them, but they're estimates, not actual measures.
"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
May 23, 2012 at 5:11 am
After reading Gail's articles, read my book. Links are in the signature.
"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
May 23, 2012 at 5:09 am
That's very abnormal. Were you able to capture the execution plans for the queries so we can try to compare them to each other? This is not something I'm used...
"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
May 23, 2012 at 5:00 am
The necessary permissions are documented right here on the Red Gate web site.
"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
May 22, 2012 at 6:20 am
Ditto. Or, it might be accessed by looking at the default ANSI settings for the server.
"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
May 22, 2012 at 6:17 am
MadTester (5/22/2012)
Currently I'm thinking of changing the job to do a reorganise daily based on fragmentation and an...
"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
May 22, 2012 at 6:16 am
The ANSI settings change how the optimizer creates execution plans. So one connection with "concat null yields null" turned on can create a different execution plan from one that has...
"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
May 22, 2012 at 4:46 am
The only way to be 100% sure is to restore the database. I wrote this short article [/url]laying out the various things you can do and what they do for...
"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
May 22, 2012 at 4:18 am
In theory, the same stored proc called from any connection should run roughly the same speed, regardless of who called it. But... there are connection settings that will cause different...
"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
May 22, 2012 at 4:12 am
By the way, if you're getting RID lookups it means that you're dealing with hash tables, tables without a clustered index. Unless you have a very thorough set of tests...
"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
May 22, 2012 at 4:09 am
From the sounds of things, you could just leave stuff as is. It doesn't sound like the data is so volatile that your stats are getting updated.
I don't think doing...
"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
May 22, 2012 at 4:07 am
Viewing 15 posts - 10,861 through 10,875 (of 22,219 total)