Viewing 15 posts - 20,116 through 20,130 (of 22,219 total)
You mean something like this?
CREATE PROCEDURE UpdateEmail
(@OldEmail nvarchar(275)
,@NewEmail nvarchar(275)
AS
BEGIN TRY
UPDATE MyEmail
SET Email = @NewEmail
WHERE Email = @OldEmail
END
BEGIN CATCH
RETURN ERROR_NUMBER();
END
"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 19, 2008 at 11:34 am
So much for contacting people.
I'm still baffled. I'm not sure why this is happening like it is. Odd stuff.
"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 19, 2008 at 11:10 am
No, it's not the same at all. 2005 really is better.
"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 19, 2008 at 7:00 am
Pull up the execution plan. That will help you find out where to look.
I suspect it's this:
(D.Did in (select max(Did) from D group by Aid) ...
"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 19, 2008 at 6:51 am
I can't find the documentation. Here's a support article, but it's not what I meant:
http://support.microsoft.com/kb/281671
And Kalen
http://www.sqlmag.com/Article/ArticleID/16078/sql_server_16078.html
"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 19, 2008 at 6:47 am
Mike Levan (6/18/2008)
Exactly.Can you pls update my proc with your best performance ideas.
Actually, quite a few of us get paid to rewrite 500 line stored procedures. We'll help, but you...
"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 19, 2008 at 6:35 am
First, I'd try posting in the SQL Server 2000 forums, not the 2005 forum.
Second, there isn't an immediate method to do this. There are some options. If you're running a...
"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 19, 2008 at 6:21 am
I agree with Matt. There are some fantastic articles right here that will move you along. As for books, Wrox has a decent one called Professional SSIS. The one our...
"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 19, 2008 at 6:09 am
It really does sound like recompiles either from causes within the code or due to changes in the data. Especially since it seemed to happen over time and somewhat randomly,...
"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 19, 2008 at 6:02 am
I wish I had a contact or three at MS. I'd love to see this moved up the chain... I'm going to try contacting a couple of people.
"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 19, 2008 at 5:52 am
It's still Visual Studio.
"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 18, 2008 at 1:17 pm
While GUID's can be a unique value, you didn't put a unique constraint on the key, so when combined with the other part of your where clause, you're probably getting...
"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 18, 2008 at 10:06 am
It sounds like Steve nailed it in one.
We had a similar issue, waits for compiles, which lead to other waits for compiles, etc.
Our code was actually compiling due to changes...
"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 18, 2008 at 10:03 am
Ummmm. That was strange. Where the heck did the execution plan go?
If I run this query, I can see it.
SELECT
p.*,
q.*,
...
"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 18, 2008 at 9:33 am
A log file is a mechanism I'd only use from the application side. If you're capturing error information inside SQL Server, just write it out to a table.
"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 18, 2008 at 9:21 am
Viewing 15 posts - 20,116 through 20,130 (of 22,219 total)