Viewing 15 posts - 7,171 through 7,185 (of 22,232 total)
Instead of using a linked server, what about using OPENQUERY?
"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
December 4, 2014 at 4:06 am
That's a weird one. And it's Enterprise that's causing the problem?
I haven't seen it, but I'll go spin up a VM and see what happens.
"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
December 4, 2014 at 4:02 am
I prefer using OPENQUERY to linked servers so that I can pass parameters to the linked machine in order for it to do as much filtering of data as possible...
"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
December 4, 2014 at 4:00 am
But, if it's a data warehouse, does it need to have point in time recovery? If not, maybe Simple would work for you.
You'll still need to set the transaction...
"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
December 4, 2014 at 3:57 am
Nope. Backups are just databases. If you want to move only a table you need to set up some kind of ETL process. The common tool is SQL Server Integration...
"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
December 2, 2014 at 3:38 pm
ScottPletcher (12/2/2014)
Robert Frasca (12/2/2014)
ScottPletcher (12/2/2014)
Robert Frasca (12/2/2014)
ScottPletcher (12/1/2014)
I suggest creating a covering index on:
SourceFactTimeCard ( TimecardIndex, EmployeeID )
If SQL...
"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
December 2, 2014 at 10:39 am
GilaMonster (12/2/2014)
Grant Fritchey (12/2/2014)
GilaMonster (12/2/2014)
Grant Fritchey (12/2/2014)
You may need to re-schedule them so they run less frequently, but you may just need to get more hardware.
Or restore the backups 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
December 2, 2014 at 7:22 am
npranj (12/2/2014)
As for the Identity Column CI - we will not be using this column in any query.
So what should...
"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
December 2, 2014 at 6:52 am
GilaMonster (12/2/2014)
Grant Fritchey (12/2/2014)
You may need to re-schedule them so they run less frequently, but you may just need to get more hardware.
Or restore the backups to another server 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
December 2, 2014 at 6:48 am
It sounds like your server is seriously underpowered. I've seen DBCC impact performance in some ways, but it doesn't take the database offline, at all, by design. So if your...
"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
December 2, 2014 at 6:32 am
Have you looked at the documentation available from Microsoft. Here's the command line install documentation and the configuration file install documentation. Both of those have examples available that you can...
"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
December 2, 2014 at 6:28 am
npranj (12/1/2014)
The 42% cost is Clustered Index insert cost. There is one CI and 4 NCI on this table.
All the other costs are from Index Seeks.
Also, this PK...
"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
December 2, 2014 at 6:04 am
Jeff Moden (12/1/2014)
Grant Fritchey (12/1/2014)
Just because it's not an incrementing number doesn't mean that it's not a good choice for the clustered index.
I have to admit that I'm taken aback...
"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
December 2, 2014 at 5:59 am
kevaburg (12/2/2014)
Grant Fritchey (12/1/2014)
"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
December 2, 2014 at 5:51 am
Nah, the other plan knew that it was only returning a single row from the seek too.
Pretty sure Scott's onto something. Indexes sure won't hurt and if you can...
"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
December 1, 2014 at 5:51 pm
Viewing 15 posts - 7,171 through 7,185 (of 22,232 total)