heb1014 (5/19/2011)

---

Great point about not seeing anything yet that won't produce a scan. I started hammering away and tried some indexes when it hit me that there isn't any...

Create a new linked server to test. Shut that server down.

Run the insert and log the error you get.

use try catch to control the error, then run the 2nd...

Any of them blanks?

Make sure the total space of the report doesn't exceed the size of the paper (including margins)

Make sure the image is in the page header (not report header).

Then in the page properties click repeat header.

You could do the same in the header / footer of a...

GSquared (5/19/2011)

---

Ninja's_RGR'us (5/19/2011)

---

GSquared (5/19/2011)

---

Ninja's_RGR'us (5/19/2011)

---

GSquared (5/19/2011)

---

I've gone from $7.50/hour in 2001 to, well HR says I can't say the number but it's more than 4X that. None of it...

The real solution is to tune those processes and if possible run them of hours to lighten the load.

http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/

http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-2/

I still don't see anything that won't run a scan of some sort... still waiting on table script and sample data.

GSquared (5/19/2011)

---

Ninja's_RGR'us (5/19/2011)

---

GSquared (5/19/2011)

---

I've gone from $7.50/hour in 2001 to, well HR says I can't say the number but it's more than 4X that. None of it has been...

GSquared (5/19/2011)

---

I've gone from $7.50/hour in 2001 to, well HR says I can't say the number but it's more than 4X that. None of it has been through percentage...

For better answers on performance questions, click on the following...

http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Delete in small loop. Switch db to simple recovery. Make sure you don't care about losing all your data and changes between backups tho.

I assume the column is of varchar datatypes here.

UPDATE Tbl SET Col = REPLACE(Col, '7', '82')

I has to be a reindex job. It's always that or a massive import of data.

When the backup is taken, the space is marked available for reuse. so the log doesn't need to grow.

You can schedule it more than once... maybe every 10...

Run the log backups every 10 minutes (maybe even less).