Viewing 15 posts - 19,486 through 19,500 (of 22,219 total)
If you're using table variables that are more than a few rows in size, switch them to temp tables. Except for a primary key, table variables have not statistics where...
"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
October 8, 2008 at 7:45 am
If you also get an execution plan, that will allow focus on the parts of the query that are causing the most problem.
First thing that jumped out at me was...
"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
October 8, 2008 at 7:42 am
Seriosly, this is way to big a topic to be answered in a post. Simply saying "customer feedback" is not nearly enough information to begin designing a database. You need...
"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
October 8, 2008 at 7:28 am
That really depends on the system. Most of our systems work just fine with the sampled statistics update, but we have a few tables on a few systems that need...
"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
October 8, 2008 at 7:10 am
Also, make sure you look up the right way to create a user, CREATE USER. A lot of our 2000 scripts were using sp_grantdbaccess, which will create a user, but...
"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
October 8, 2008 at 7:08 am
An index on Registrationno will help more if it's a clustered index. If it's a non-clustered index, the SELECT statement will force a key lookup either against whatever clustered index...
"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
October 7, 2008 at 11:18 am
I don't know. I got it from our server admin guys. They handle all the software versions, 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
October 7, 2008 at 10:51 am
That's wild, but as you say, at least you got a result. I'd be happy with a result, even a sub-standard one. Actually, I'd be happier with a sub-standard result....
"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
October 7, 2008 at 10:22 am
It's on Connect. If you want to confirm it or track it, go here.
"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
October 7, 2008 at 9:33 am
Nope. No recommendation from that query either. I haven't found a query yet that the silly thing will recommend and index for.
I'll post something on Connect now.
"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
October 7, 2008 at 9:17 am
Oh, since I violated the rules with the first post, let me show my query:
SELECT soh.Freight, soh.SalesOrderNumber
FROM Sales.SalesOrderHeader AS soh
WHERE soh.SalesOrderNumber LIKE 'SO' +...
"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
October 7, 2008 at 6:00 am
OK. A little more information. According to BOL, the DTA won't provide recommendations unless:
The table has been selected to tune (it is)
The table has more than 10 pages 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
October 7, 2008 at 5:53 am
Yeah, that might be the place to go.
I found a clean place on the wall. I'm going to do a few more bashes first.
"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
October 7, 2008 at 5:26 am
Similar.
I know a number of other ways to fix the queries myself. I need to see the bloody DTA do the work.
I tracked down a bit of sample code...
"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
October 7, 2008 at 4:04 am
I wouldn't say you need to replace VBS with PowerShell. Different critters really.
I'm just getting started learning Powershell. It's installed automatically with SQL Server 2008 (just run sqlps.exe) and Windows...
"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
October 6, 2008 at 9:35 am
Viewing 15 posts - 19,486 through 19,500 (of 22,219 total)