Viewing 15 posts - 21,466 through 21,480 (of 22,224 total)
Once you identify the offending procedure using Gail's method, get execution plans to see what is occuring within the script.
"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
December 5, 2007 at 6:06 am
Do you foresee a need to use character sets from other languages, Kanji, Cyrilic, what have you? No, use VARCHAR. Yes, use NVARCHAR.
"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
December 4, 2007 at 5:41 am
99.999% TSQL.
The remaining bits I use C# or VB.NET through the SMO (SQL Management Object). Very little need for anything else.
I did go through a great book on using PERL...
"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
December 4, 2007 at 5:39 am
montgomery johnson (12/3/2007)
"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
December 4, 2007 at 5:32 am
Gail is 100% correct. To add to it a bit, if your statement uses an index to retrieve the data, it frequently comes back in index order. The only way...
"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
December 4, 2007 at 5:25 am
Or, I didn't think that through all the way and I'm wrong.
"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
December 3, 2007 at 10:23 am
If you have a primary key constraint defined as nonclustered, you already have an index on that column, so no worries there.
Yes, you don't have to include the clustered index...
"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
December 3, 2007 at 9:49 am
It simply gives you an indication whether the error is informational, really important, fatal to a connection or fatal to the server. See the reference linked above for details.
"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
December 3, 2007 at 7:05 am
I went and read the original message. It's whining, pure and simple. I then read as many of the comments as I could stomach. It's kind of freaky how attached...
"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
November 30, 2007 at 9:01 am
The real problem is, I am a jerk. So I have to try to reduce the damage as much as possible. Emails are dangerous because, even a well crafted message...
"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
November 30, 2007 at 6:57 am
Sorry, I wasn't trying to upset anyone. I'm serious. I screw up all the time. The checks I can put in place to prevent my own errors will help those...
"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
November 30, 2007 at 6:54 am
In order to select FROM something, it needs to be a table valued object (table, view, function, temp table, table variable, OPENXML, XQuery). You can run a query against 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
November 30, 2007 at 5:55 am
What about literally breaking the query up into smaller queries? You can call them all from a single wrapper query. You get more discrete, tuneable execution plans and you can...
"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
November 30, 2007 at 5:51 am
P Jones (11/30/2007)
There's considerable power in .NET datatables, datarelations, foreign keys,primary keys and constraints that can be all done programmatically.
Works like a charm too... until the first time a request...
"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
November 30, 2007 at 5:34 am
We're using this method and the same idea with whole databases in some of our datamarts. It works well to minimize down time. Best of all, if there is 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
November 30, 2007 at 5:24 am
Viewing 15 posts - 21,466 through 21,480 (of 22,224 total)