Viewing 15 posts - 6,226 through 6,240 (of 22,226 total)
It's an emergency traceflag for restarting the server when you've got a failed install going on. It's not something used regularly.
"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
April 29, 2015 at 8:16 am
No. MSDN has one key word in it. Developer. Your SQL Server licenses and your development licenses are different. You can set up Enterprise instances for testing and development and...
"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
April 29, 2015 at 8:13 am
The real question though is, why are you going for a certification. They're only helpful as study guides and possibly when working for a company that wants to maintain Microsoft...
"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
April 29, 2015 at 8:10 am
The trace is going to run on the server, not on your local machine. The output can be from the server to your local machine if you've set up 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
April 29, 2015 at 8:07 am
Sorry. Hope it's not production.
"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
April 28, 2015 at 6:37 pm
Steve Jones - SSC Editor (4/28/2015)
"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
April 28, 2015 at 6:37 pm
Lynn Pettis (4/28/2015)
SQLRNNR (4/28/2015)
Lynn Pettis (4/28/2015)
Lynn Pettis (4/28/2015)
Wow, what some people expect us volunteers.
The OP just PMed me with all the info that had been posted on the forum thread....
"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
April 28, 2015 at 6:35 pm
Yes.
You can't remove that from the database.
"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
April 28, 2015 at 10:39 am
Yes. SQL Server hasn't fundamentally changed.
"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
April 28, 2015 at 8:38 am
Check the data and your code again. If you're getting a primary key violation, especially while doing identity insert, you're attempting to add a value that already exists.
"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
April 28, 2015 at 5:30 am
Doing a statistics update after an index rebuild will, in some situations, result in worse statistics. This is more of an issue in transactional systems, but you could hit similar...
"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
April 28, 2015 at 5:28 am
Just know that installing them side-by-side on the same server, for a time, while both are running, they're likely to be competing for resources.
"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
April 28, 2015 at 5:24 am
Backing up the log won't decrease the file size of the log itself. It frees space within the log of committed transactions. If your log is continuing to grow, I...
"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
April 28, 2015 at 4:03 am
TomThomson (4/27/2015)
Grant Fritchey (4/27/2015)
"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
April 27, 2015 at 7:35 pm
TheSQLGuru (4/27/2015)
Igor Micev (4/27/2015)
You can use the NOLOCK hint for srno without worries because u're reading an identity value.Can you please explain that statement Igor??
Yeah. I'm unclear on it too.
"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
April 27, 2015 at 4:03 pm
Viewing 15 posts - 6,226 through 6,240 (of 22,226 total)