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

GilaMonster (12/2/2014)

---

Grant Fritchey (12/2/2014)

---

GilaMonster (12/2/2014)

---

Or restore the backups to...

npranj (12/2/2014)

---

Hi Grant - There are intent exclusive locks (LCK_M_IX)

As for the Identity Column CI - we will not be using this column in any query.

So what should...

GilaMonster (12/2/2014)

---

Or restore the backups to another server and...

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

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

npranj (12/1/2014)

---

Thanks Grant.

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

Jeff Moden (12/1/2014)

---

I have to admit that I'm taken aback...

kevaburg (12/2/2014)

---

Grant Fritchey (12/1/2014)

---

On most systems, most of the time, the vast majority of tables should have, at minimum, a clustered index. I'll bet if you put it on the...

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

Robert Frasca (12/1/2014)

---

Grant Fritchey (12/1/2014)

---

The pain point on the WithMAX plan is the fact that it's doing a Loops join against 1.9 million rows. That's effectively a cursor. But, it...

The pain point on the WithMAX plan is the fact that it's doing a Loops join against 1.9 million rows. That's effectively a cursor. But, it looks like your full...

On most systems, most of the time, the vast majority of tables should have, at minimum, a clustered index. I'll bet if you put it on the right place, in...

Just because it's not an incrementing number doesn't mean that it's not a good choice for the clustered index. Also, the cost of an insert is usually quite high for...