Viewing 15 posts - 20,431 through 20,445 (of 22,219 total)
And you will need to show execution plans so that bottlenecks can be identified.
"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 12, 2008 at 6:39 am
The wizard should work. You can also select all your procedures in the Object Explorer Detail window by first clicking on the Procedures folder in the Object Explorer window. In...
"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 12, 2008 at 6:23 am
Can't you simply open another connection to the database and fire the procedure asynchronously? That way it won't be part of the main application's execution path.
"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 12, 2008 at 6:17 am
It's also worth pointing out that the ANSI 92 joins will cause problems in SQL Server 2005 and above when doing outer joins. From BOL: The outer join operators (*=...
"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 9, 2008 at 9:49 am
dfalso (5/9/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 9, 2008 at 9:40 am
Jane Matheson (5/9/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 9, 2008 at 7:31 am
22?
Oh lordy, I knew you were wet behind the ears, but I had no idea. I could be your father... Oh, yuck. No offense, just lamenting my lost youth.
Anyway,...
"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 9, 2008 at 5:56 am
Huh, I wonder why that's running slow. 😀
Sorry, that's not nice. Actually, except for the enormous set of columns in the GROUP BY, this isn't too bad a query based...
"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 9, 2008 at 5:43 am
Rollback the transaction before you insert into your audit table. Here's a sample using Adventureworks:
BEGIN TRY
BEGIN TRANSACTION
UPDATE [HumanResources].[Department]
SET [Name] = NULL
WHERE [Name] IS NOT NULL
END TRY
BEGIN CATCH
ROLLBACK TRANSACTION
INSERT INTO dbo.[AuditLog]...
"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 9, 2008 at 5:35 am
Just a quick follow-up. It looks like, based on the code you posted, that you're missing the concept of part of the UPDATE statement. You went inline on both your...
"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 9, 2008 at 5:30 am
Great article Yoda: "you'll never wrong go by creating a primary key on a table, temp or not"
Seriously though, I find the resistance to your thoughts that, with a VERY...
"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 9, 2008 at 5:21 am
Hey Sandy,
Are you getting lazy in your old age? 😉
Just go over to the MS web site and you'll get all the marketing stuff you need. Here's the page to...
"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 9, 2008 at 5:14 am
You should look into breaking down your process into smaller steps. Insteading of processing one million rows (or whatever it is) as a single transaction, run them hundred thousand row...
"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 9, 2008 at 5:10 am
I've always loved love writing. I hated English class in school because I thought, and still do, the teachers were, let's say, less than adequate to their jobs and more...
"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 9, 2008 at 5:06 am
@@ERROR is resolved individually for each statement. So a bit of your code:
CREATE TABLE test1(testint int, oooo)
GO
IF @@ERROR<>0 OR @@TRANCOUNT=0
BEGIN
As long as the GO...
"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 8, 2008 at 10:44 am
Viewing 15 posts - 20,431 through 20,445 (of 22,219 total)