Viewing 15 posts - 14,806 through 14,820 (of 22,227 total)
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
adnan8t2 (6/21/2010)
According to your experience what we should set the size of following fields while creating a new database.
MDF Initial Size = depends on system estimates
LDF Initial Size =...
"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:17 am
balasach82 (6/21/2010)
I need to determine the Number of Transactions a DB faces in a single day.
If you just need a transaction count, there are performance monitor counters that will give...
"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:10 am
Ah, different information. I would check the ANSI settings first, see if they're the same.
"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 18, 2010 at 12:01 pm
david.c.holley (6/18/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 18, 2010 at 11:50 am
GilaMonster (6/18/2010)
If you just want to view the proc, you can grant view definition rights on it.
Oh right, I was thinking about looking at the data... misread it. Good catch,...
"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 18, 2010 at 8:52 am
You can't. You'd need to have execute privs on the procedure in order to execute it and get the data back from it.
"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 18, 2010 at 8:34 am
A server side trace is the best method. Just limit the number of events and columns you're capturing and you won't even see the effects of it running, even on...
"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 18, 2010 at 8:02 am
Another option that we use pretty frequently is to create a role within the database. Grant all permissions through the role, and then add users or AD groups to 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
June 18, 2010 at 7:37 am
First off, you didn't state whether or not the hardware was different. Unless the memory, cpu and disks are identical, you'll see fundamental differences in behavior between machines.
Second, index fragementation,...
"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 18, 2010 at 7:35 am
Viewing 15 posts - 14,806 through 14,820 (of 22,227 total)