Viewing 15 posts - 21,226 through 21,240 (of 22,219 total)
"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 17, 2008 at 12:26 pm
Hey Sandy,
Can you simply use a WHILE loop?
WHILE [SomeCondition = TRUE]
BEGIN
EXEC sp_proc
[Change Condition]
END
Or do you need something more like:
exec sp_who
go 5
Putting the number next to the GO statement will make...
"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 17, 2008 at 7:01 am
Hey Sandy,
Sorry I'm late to the game, but everything Jeff said goes double for me. 😀
"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 17, 2008 at 6:56 am
The two things I saw that stood out was that there was a join without a predicate. That's usually not a good thing. Joins, for the most part, should have...
"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 1:13 pm
Looks good. Thanks.
"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 12:01 pm
I know I sound like a broken record sometimes, but have you looked at the execution plan to see which operations are specifically causing the most problem? That will lead...
"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 10:56 am
Embarcadero ERStudio, but I wouldn't be swallowing when you see the price on that one either.
Great tool. Decent company.
"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 10:28 am
Nothing to be sorry about. You'll just get quick responses because it's going to be seen by a wider audience.
"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 8:47 am
You should start a new topic for this question.
"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 8:36 am
Yeah, that is one the BIG weakness to the approach. You can't count on referential integrity. Basically we work from the model that there is an authoritative source for data....
"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 8:33 am
Unless you want to tie the development schedules together (which is a perfectly viable option, but one that needs to be taken eyes open) you should seperate the databases. Once...
"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 7:51 am
Oh, sorry, I am dense sometimes.
You have to open the Profiler trace file first. Then you can import the perfmon data.
"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 7:02 am
I'd use the 4th option and turn on cascading deletes from there (if you really want to use those things). However, what happens if an address is used more than...
"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:57 am
Just understand that you can't escape the 8060 limit by doing an insert and an update. If you exceed 8060 in a row, you've exceeded it.
Another option that 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
January 16, 2008 at 6:52 am
If you haven't rebuilt the indexes on the this system in recent memory, I'd start there (and establish a mechanism that does it on a regular basis. There are several...
"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:40 am
Viewing 15 posts - 21,226 through 21,240 (of 22,219 total)