Not even a good guess. Now, frankly, I'm curious. I'm with Steve. Set this one fire and move on... after you capture the wait stats.

I just remember, I wrote an article on just this topic[/url].

yeah, if you want to explore multi-server management, you certainly can schedule them to run across multiple servers.

Weird.

I tried to replicate it. Standard worked just as fast as Enterprise on the VM I created.

Have you tried capturing wait stats before and after running the create database command?

Yeah. It'll generate a script, or you can generate a report of the differences, or both. All from the command line. I forget the syntax, but it's in the documentation.

OK. I'm back.

I spun up an Enterprise server taking all the defaults and then created a database. It only took about 3 seconds (if that). Maybe this is on Standard?...

And because you're selecting everything, that's all stored with the clustered index, hence the scan.

How many rows is it returning out of how many rows in the database?

Check the wait stats before and after the query runs on the slow machine to understand what is causing it to slow down. Also, compare the execution plans between the...

I know I work for Red Gate now, but, prior to working for Red Gate, I had SQL Compare open on my desk pretty much every day. Plus, you can...

Instead of using a linked server, what about using OPENQUERY?

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.

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...

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...

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...

ScottPletcher (12/2/2014)

---

Robert Frasca (12/2/2014)

---

ScottPletcher (12/2/2014)

---

Robert Frasca (12/2/2014)

---

ScottPletcher (12/1/2014)

---

I guess the SourceFactTimeCard table is fairly wide?

I suggest creating a covering index on:

SourceFactTimeCard ( TimecardIndex, EmployeeID )

If SQL...