I would say your Azure database is under powered (as is almost ALWAYS the case). But as someone else said, fastest will be to make a new table (with NO...

First and by FAR the most important let me say that this should be done OUTSIDE of SQL Server (unless you are going to be using the set in another...

Ross McMicken (4/1/2016)

---

Hugo Kornelis (3/31/2016)

---

Chitown (3/31/2016)

---

Hugo Kornelis (3/31/2016)

---

1200 logical files? That is a lot!

I recommend using this opportunity as a test case to check how long the restore will take....

See SET DEADLOCK_PRIORITY (https://msdn.microsoft.com/en-us/library/ms186736.aspx) and use that for your batch processes. Set them HIGH and you should be good. This could be easier than setting LOW for all of your...

If all columns are "important" for updating your who/when columns then you don't need to check for them. You simply update the fields joining to INSERTED without a WHERE clause....

Chitown (3/31/2016)

---

I will personally kick his/her butt :-). Since it's prod, no one...

CLR is by far the best way to do this, at least until SQL 2016 is released. You can use Delimited8KSplit found here on SSC.com to do this, although the...

Since bcp is a command-line tool and I'm old school, I would use DOS scripting for this. Works fine, lasts a long time. 🙂 If you have xp_cmdshell enabled on...

Just write a SELECT TOP 1 ... query and use that to drive bcp:

https://msdn.microsoft.com/en-us/library/ms162802.aspx

This is the third time I have mentioned this this week, but you must make sure your non-production environments have Instant File Initialization enabled. Otherwise your restore will zero out...

Your post doesn't make sense as written. Nothing you have explains any need to iterate. So, what, EXACTLY, are you doing with this output:

SELECT @user-id = UID, @RefID = RefID...

I would also check if you have enabled Instant File Initialization on the restore machine. Without it, your server will zero out every bit of every byte of the entire...

That is a false statement, as Grant has already said. A Failover Cluster requires shared storage.

I REALLY caution you...

Personally in such situations (and others, such as too many databases on the same server) I simply construct my own processes for backup file migration and processing.

Lets see real code please, not pseudo code.