On the new T-SQL optimization I highly recomend Microsoft SQL Server...

jarid.lawson (11/26/2012)

---

Glad I posted this, because my brilliant idea caused the system to crash.

I tried the Tasks > Copy Database option. I made it most of the way through, but...

Backup/Restore is best.

You can also do a copy by: right-click your db >> Tasks >> Copy Database then go through the wizard.

The agent job will be running whereever the job is...

First, I concur with MyDoggieJessie - check for filters, check the agent job to see if it is running without error...

I don't know...

I going to assume we're not in Prod...

If the snapshot agent ran correctly your tables should...

You can accomplish this by re-running the snapshot agent for that subscription.

Based on the info provided:

-- This table has the name of every department

DECLARE @dept TABLE (

deptNbr int primary key,

department varchar(10) NOT NULL );

-- This is where department goals are...

-- place to test the insert

DECLARE @targetTable TABLE (val1 varchar(30), val2 varchar(30));

-- the value fed to your query

DECLARE @splitMe varchar(40) = '9279-1^Respiratory Rate^LOINC';

;WITH x(a,b) AS

(SELECTLEFT(@splitMe, CHARINDEX('^',@splitMe)-1),

RIGHT(@splitMe, LEN(@splitMe)-CHARINDEX('^',@splitMe))

)

INSERT...

If by "slows down the entire database" you mean that running these reports slows down other, non-reporting activity then my advise would be to do what Eugene was saying: consider...

Lokesh Vij (10/10/2012)

---

This query would give the best performance from all the queries posted above 🙂

SELECT dtStartDate,

(SELECT Max(dtRunDate)

...

haiao2000 (10/10/2012)

---

Alen,

I updated...

Homersdonut (10/10/2012)

---

A co-worker analyzed CTE performance in SQL Server 2005 and determined it begins to degrade after, if I recall, 100,000 records.

As we encounter performance related issues in production which...

SQL Guy 1 (10/10/2012)

---

Thanks for quick replies.

Alan: I cannot create a real table, because this db will be restored, and the table will be gone. About SSIS, frankly...

You should post the actual DDL.

From what I see you could make this faster using the Local Updateable Variable approach (e.g. the 'Quirky Update')... See http://www.sqlservercentral.com/articles/T-SQL/68467/