Viewing 15 posts - 21,241 through 21,255 (of 22,219 total)
Not to push my own stuff, but I busted my bottom for Tony Davis to write the darn thing, so, try this article [/url]over on Simple-Talk as a starting point....
"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
January 16, 2008 at 6:34 am
Which application are you referring 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
January 16, 2008 at 6:32 am
Just understand that, depending on the stored procedure in question, the performance increase will be miniscule or incredibly huge. The simplest of simple insert statements, for example, going to 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
January 16, 2008 at 6:30 am
Seperate the databases and provide a service (Service Oriented Architecture, SOA) that pulls the data from X in order to feed it to Y, through the applications, not through 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
January 16, 2008 at 6:24 am
I sure can't tell you. I white list your stuff about once or twice a month because it keeps getting flagged.
"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
January 16, 2008 at 5:36 am
When you say "somewhat changed" what exactly?
Have you updated statistics or, better still, rebuilt your indexes in recent memory?
"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
January 16, 2008 at 5:35 am
Congrats again then.
And a WOO HOO to go with it.
:w00t:
"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
January 16, 2008 at 5:33 am
Oh yes, Profiler and Perfmon. They can do more for you than almost any third party tool.
Set up Profiler to run by script (look up sp_trace_create & sp_trace_setevent among others)...
"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
January 15, 2008 at 1:28 pm
Another vote for Visual Studio. Hook it into source control and then you get versions of your scripts too. Very handy when one of them suddenly breaks for no apparent...
"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
January 15, 2008 at 12:34 pm
In addition to what Matt Miller is suggesting, you might verify that the data types of the parameters is the same as the data types of the columns. If you're...
"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
January 15, 2008 at 12:33 pm
You have to understand, BOL is my best friend because I'm too darned stupid to remember 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
January 15, 2008 at 8:28 am
Oh, that's likely to be a bit tougher then. I'm not sure how you'd do this in 7.0 (haven't touched it in years and years).
"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
January 15, 2008 at 7:12 am
Just note, it's 'sys.databases' not 'sysdatabases'. You need to get in the habit of looking at the catalog views, not the 2000 system tables.
"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
January 15, 2008 at 7:03 am
You can use parameters within sp_executesql. Those parameters can be output parameters. You can set those values within the ad hoc query and output them from there and then set...
"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
January 15, 2008 at 7:00 am
Probably a completely inadequate solution... but I wanted a little experiment this morning:
CREATE TABLE #DBList(DBName NVARCHAR(100))
DECLARE @Tablename NVARCHAR(100)
DECLARE @Tsql NVARCHAR(MAX)
DECLARE @DBName NVARCHAR(100)
DECLARE Cur CURSOR FOR
SELECT NAME
FROM [sys].databases;
SET @Tablename =...
"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
January 15, 2008 at 6:52 am
Viewing 15 posts - 21,241 through 21,255 (of 22,219 total)