Viewing 15 posts - 21,241 through 21,255 (of 22,226 total)
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
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
Viewing 15 posts - 21,241 through 21,255 (of 22,226 total)