Viewing 15 posts - 21,886 through 21,900 (of 22,219 total)
Cool. What would you use in 2005? ![]()
"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 1, 2007 at 8:58 am
Are you running this against a 2000 server or against a 2005 server in 8.0 compatibility mode? Either of those will be the problem.
"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 1, 2007 at 8:57 am
One likely issue is the USING word you've got in the very first join. Also, you can't use variables $x. Instead you should use @x. What are those other two...
"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 1, 2007 at 8:56 am
No, you and the article are correct. Seeks are better than scans. Eliminating, as much as you can, bookmark lookups is the way to go. The issue isn't whether or not...
"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 1, 2007 at 5:17 am
The differences in the data are most likely going to cause different query plans. I suspect that's the most likely issue.
One thing you said that concerns me a bit. You've created...
"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 30, 2007 at 12:19 pm
Is the amount of data and it's distribution the same between dev & production. Do you have the latest statistics in both environments? Do you have an index maintenance plan in 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 30, 2007 at 8:51 am
There are some tools that offer a solution to this problem too. You can try Red-Gate's SQL Refactor which will rename an object and all it's references. Another one is...
"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 30, 2007 at 7:58 am
I've only spent five minutes looking at this, but the first two things I'd check would be the parallelism threshold on your server and the cluster on the Subscriber table.
I'd...
"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, 2007 at 1:05 pm
sp_addextendedproperty is for putting descriptions, etc., on to your SQL server objects. It doesn't do any kind of formatting of any kind. It's for creating meta-data about your database objects....
"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, 2007 at 12:30 pm
And get a copy of Inside SQL Server 2005: The Storage Engine by Kalen Delaney
"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, 2007 at 12:16 pm
Have you runa a DBCC CHECKDB against the database as it suggests?
Other than that, I'd want to see the code to try to figure out where the error lies.
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
April 27, 2007 at 12:14 pm
Not at all. If I thought I had something really cool & wonderful I'd be crushed. Instead, what I've got is a bit of a hack based on other people'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 26, 2007 at 2:36 pm
It's not a terribly well written script. We had a specific need and wrote it to meet that need and then stopped. We're extremely dilligent about keeping reserved words &...
"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, 2007 at 2:01 pm
I'm fairly certain you can only get the columns available from the inserted table within a trigger and not any parameters within a stored procedure. You either have to simply...
"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, 2007 at 5:41 am
This should do it:
SELECT
p.name,m.name
FROM
sys.server_principals p
JOIN
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood" Author of:
- Theodore Roosevelt
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 26, 2007 at 5:31 am
Viewing 15 posts - 21,886 through 21,900 (of 22,219 total)