Viewing 15 posts - 9,406 through 9,420 (of 22,224 total)
Yeah, if you create a temporary table as a local temp table, using #temptablename, it's only for the connection using it. You can create a global temporary table using ##temptablename...
"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
October 25, 2013 at 5:44 am
Check out my sig for a book on reading execution plans. You can even download it for free.
"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
October 24, 2013 at 12:33 pm
I'm pretty sure the differences are in how the query is dealing with the DISTINCT statement. Look at the execution plan to see how that is resolving itself.
Since DISTINCT is...
"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
October 24, 2013 at 12:29 pm
I'm with Gail. I can't think of anything that would lead me to regularly restart the instance because of something within TEMPDB.
"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
October 24, 2013 at 8:10 am
From a core behavior stand point, there's no real difference between the two. Both are basically just deallocating the resource. But, you then have to go back and recreate 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
October 24, 2013 at 8:09 am
For just learning PowerShell, I'd suggest Don Jones book, PowerShell in a Month of Lunches. It'll give you most of what you need to learn 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
October 24, 2013 at 8:05 am
The EPM does all the work for you. But the other stuff is documented on Microsoft. It's very easy. Yes, for more complete direct control you'll do PowerShell scripting, but...
"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
October 24, 2013 at 7:40 am
Just don't ever forget that all these types of tables from table variables, multi-statement UDF and table parameters, all of them lack statistics which can seriously, negatively, impact performance.
"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
October 24, 2013 at 6:13 am
Sure. It's a part of PBM. You can make calls from Agent. Keep reading in the documentation. PBM is great.
"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
October 24, 2013 at 6:08 am
All databases must have a transaction log, even on SQL Server 2000. Are you trying to remove a log file you are no longer using, but there will still be...
"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
October 24, 2013 at 5:50 am
If you look at Policy Based Management, it has backup monitoring built in. But there are examples online. Here's one from MSSQLTips[/url]. As far as reports goes, I'd suggest taking...
"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
October 24, 2013 at 4:45 am
A) It's difficult to get a job without experience, despite any training you have. So that's going to be a hurdle. I wouldn't mess around with SSIS because that is...
"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
October 23, 2013 at 12:10 pm
According to the documentation, you have to use a table variable. That means defining the columns.
"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
October 23, 2013 at 12:06 pm
If you have a mechanism to test the backup, meaning restore it, then you could do a physical only check on the live database which is much faster. Then, 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
October 23, 2013 at 10:33 am
Koen Verbeeck (10/23/2013)
Beatrix Kiddo (10/23/2013)
Grant Fritchey (10/23/2013)
"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
October 23, 2013 at 7:15 am
Viewing 15 posts - 9,406 through 9,420 (of 22,224 total)