Viewing 15 posts - 14,791 through 14,805 (of 22,221 total)
Ninja's_RGR'us (6/22/2010)
Grant Fritchey (6/22/2010)
In general, especially for the size of systems you're talking about, I'd seperate these installs to seperate machines.
2 or 3?
They're not even sure they need the technologies,...
"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
June 22, 2010 at 1:16 pm
In general, especially for the size of systems you're talking about, I'd seperate these installs to seperate machines.
"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
June 22, 2010 at 11:53 am
GilaMonster (6/22/2010)
Grant Fritchey (6/22/2010)
I'll see if I can't get others to comment on it as well.
What happens if the user goes for lunch leaving the screen open, then decides 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
June 22, 2010 at 9:33 am
Inserts or deletes are occurring on the system at the same time that you're trying to read it, but the information that was being scanned has been moved. One of...
"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
June 22, 2010 at 9:23 am
A little help over here would be appreciated
"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
June 22, 2010 at 9:19 am
mshah23 (6/22/2010)
What is the problem do you see on the above solution?
Just as a starting point, what happens if, within the transaction you're holding open, you need to read...
"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
June 22, 2010 at 9:17 am
mshah23 (6/22/2010)
That's why I want...
"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
June 22, 2010 at 8:36 am
By and large in SQL Server you don't want to try to control locking. In general it does row level locking by default, all on it's own.
Why are you...
"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
June 22, 2010 at 8:15 am
Greg Edwards-268690 (6/22/2010)
Paul White NZ (6/22/2010)
Schadenfreude-Mei (6/22/2010)
Seriously, how do these people get to a point where they are even alowed to look at a live server :crazy:
I guess it's because...
"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
June 22, 2010 at 6:30 am
Assuming that you're using SQL Server 2005 or above since you're posting in the 2005 forum, why not use TRY/CATCH syntax for the error handling? This eliminates messy GO 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
June 22, 2010 at 6:17 am
I'm a bit confused. A LEFT JOIN is an OUTER JOIN. The full syntax would be LEFT OUTER JOIN.
"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
June 22, 2010 at 6:10 am
Since you're copying the entire database, why not simply run a backup and restore?
"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
June 22, 2010 at 6:06 am
It sure looks like it's going through a de-dup process to 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
June 22, 2010 at 6:05 am
balasach82 (6/21/2010)
"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
June 21, 2010 at 6:35 am
Are you looking for something in particular? There are probably a hundred "how-to" articles on setting up a basic backup schedule just here on SSC alone, and most of them...
"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
June 21, 2010 at 6:22 am
Viewing 15 posts - 14,791 through 14,805 (of 22,221 total)