Viewing 15 posts - 5,821 through 5,835 (of 22,219 total)
Try it with explicit transactions, separating the ALTER command from the 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
July 30, 2015 at 3:59 am
Just use Powershell. Here's an example script that will do what you need.
"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
July 30, 2015 at 3:58 am
You might be facing a bit of an issue here. I'm assuming you're planning to do log shipping after a restore to get the 2000 database to 2014? The problem...
"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
July 30, 2015 at 3:56 am
There's a service that gets installed with SQL Server called SQL Agent. You can use that to schedule your backups. Here's the documentation on the service. It's very straight forward...
"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
July 29, 2015 at 4:01 am
owen_zeng (7/29/2015)
hi,we have two way to upgrade sql server.
1.sql server upgrade guide
2.instal a new instance with higher version.backp&restore to the new instance.
which way is better?and what is the difference.
thanks.
Situationally,...
"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
July 29, 2015 at 3:59 am
Table variables also don't have statistics. Sometimes, this is a great thing. Sometimes it's a horrible thing. But it's one of the biggest differences between table variables and temporary tables.
"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
July 28, 2015 at 3:51 pm
And remember, the order of the keys on the indexes matters quite a bit, especially for the first column since that determines what is in the histogram of the statistics....
"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
July 28, 2015 at 10:43 am
If the disk has gone bad, that should have shown up in the wait statistics. You didn't see any changes tehre at all?
"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
July 28, 2015 at 10:40 am
I really don't sweat what happens after I spit the data out. That's the work of developers, UI experts and report writers. But yeah, those people need presentations too. Go...
"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
July 28, 2015 at 4:27 am
I'd say yes, but test it to be sure.
If you really want to improve performance though, you probably need to get rid of the WHILE loop. That's just a cursor...
"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
July 28, 2015 at 4:25 am
It's only more time consuming when you're writing it. I'm with Gail though, be sure you're using table variables for the right reasons.
"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
July 28, 2015 at 4:23 am
Eric M Russell (7/27/2015)
Based on what you've described above, I see no reason not to simply create a SubItem table.
Absolutely agreed. Based on what we're seeing, maintaining this in anything...
"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
July 28, 2015 at 3:57 am
Eric M Russell (7/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
July 28, 2015 at 3:52 am
We're talking pretty hypothetical here, but sure, there are situations where normalized storage isn't the most efficient way to manage information. That's actually part of why all the NoSQL 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
July 27, 2015 at 12:22 pm
SQL Server resolves your query into an execution plan. That shows how it chooses to retrieve the information. It tries to filter the information as it retrieves it, rather 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
July 27, 2015 at 11:19 am
Viewing 15 posts - 5,821 through 5,835 (of 22,219 total)