Viewing 15 posts - 20,236 through 20,250 (of 22,219 total)
Does this script really run? It defines the primary key twice. Once as a clustered index and once as a non-clustered index. If you're able to run this, you might...
"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
June 5, 2008 at 5:29 am
You can call the agent from the command line. Put that behind an icon on their desktop.
"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
June 4, 2008 at 12:19 pm
When it comes to triggers... Absolutely!
"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
June 4, 2008 at 11:48 am
If you used a trigger wouldn't it have to be an "instead of" trigger?
"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
June 4, 2008 at 10:46 am
I'm pretty sure you 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
June 4, 2008 at 10:26 am
You don't want my help. Here's a short[/url] account of all the problems we ran into attempting to virtualize some of our servers.
"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
June 4, 2008 at 9:21 am
BTW, running the functions against the columns means you're only going to get table scans. The indexes will not be 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
June 4, 2008 at 8:21 am
Get an estimated execution plan for the query. It won't be terribly accurate, but it should give you some information as to why you're seeing things run so incredibly slow.
"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
June 4, 2008 at 8:20 am
Seems like overkill.
Generally we approach it this way:
"Here are the top 10 poor performing procedures for database x"
"We have evaluated these procedures and identified possible fixes"
"Performance before the fix looked...
"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
June 4, 2008 at 8:18 am
It sounds like you're not exactly working from a good set of SOA standards. By and large, in most cases, you should have one system defined as the absolute authority...
"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
June 4, 2008 at 7:39 am
In 2005 use ordered GUID's. They make a huge difference in performance, especially if you have clustered indexes on the GUID. In 2000, you'll have to just deal with 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
June 4, 2008 at 6:55 am
Any time you're asked to tune a performance problem but told you can't touch the code (unless it's a third party app), you need to push back. More often than...
"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
June 4, 2008 at 6:50 am
How many rows are in the table? I ran into a similar issue and posted it on Microsoft Connect because I thought I had a bug. It has to do...
"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
June 4, 2008 at 6:48 am
We have similar problems. We've used two steps to resolve it. First, identify absolute owners of all the data you possibly can. The primary keys generated by those owning systems...
"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
June 4, 2008 at 6:43 am
One way that comes to mind is to have a tinyint column that you increment manually as you insert data. Put two constraints on the column, one to make it...
"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
June 4, 2008 at 6:36 am
Viewing 15 posts - 20,236 through 20,250 (of 22,219 total)