I would be very careful with the materialized view.

There is a lot of potential for blocking or deadlocks, so you may find it just makes things worse.

I suggest not using such a simple name for a global temp table, because someone else could use the same name, and debugging the conflict would be a nightmare.

I recomend...

guerillaunit (8/31/2012)

---

The rollback has been going on for a day now so I assume it is stuck. Any watchouts that need to be done when restarting the server? ...

Lowell (8/30/2012)

---

Eric i see just a couple of things i'd change.

the IF UPDATE(Canc) is misleading...it doesn't test if the column changed...it tests if the column was referenced in the...

ahthomas (8/29/2012)

---

Ok so starting at the date and time of the full backup file, every trn in the sequence. Got it. So the same stopat time should be used after...

I haven’t seen anything where Microsoft promises that the discussed behavior will be always observed, now or in the future.

I haven’t seen anything that proves that the discussed behavior will...

You need to restore each tran log file in sequence. You don't need the STOPAT on each log restore, but it doesn't hurt. Restore each log with NORECOVERY,...

It would be simpler to just create a maintenance plan and let it create a new backup file each time and delete files older than a week.

Backup devices are really...

Make sure you have the latest SQL 2005 service pack installed.

There was a problem with deleting files in maintanance plans in the early versions of SQL 2005.

What do you want when the letter is z?

select NextLetter = char(ascii('z')+1)

Results:

NextLetter

----------

{

(1 row(s) affected)

At a former job I managed backups for over 300 SQL Servers, and all of them were backed up to UNC locations on file servers dedicated to SQL Server backups....

Miles Neale (8/24/2012)

---

Michael Valentine Jones (8/24/2012)

---

Miles Neale (8/24/2012)

---

Michael Valentine Jones (8/24/2012)

---

Keep in mind the normal project life-cycle:

1. Set the delivery date

2. Throw some crap together.

3. Test

4. If testing is successful,...

Miles Neale (8/24/2012)

---

Michael Valentine Jones (8/24/2012)

---

Keep in mind the normal project life-cycle:

1. Set the delivery date

2. Throw some crap together.

3. Test

4. If testing is successful, then go live, otherwise go...

Ankur Bajaj (8/23/2012)

---

Heres the explanation given by my technical lead to the client for using views for reporting purposes while justifying no performance impact to App users accessing the base...

Keep in mind the normal project life-cycle:

1. Set the delivery date

2. Throw some crap together.

3. Test

4. If testing is successful, then go live, otherwise go live.

5. Define requirements.

6. Go back...