Figured out the answer -- you have to look at both the Max_size which will be -1 and the Growth which will be 0.

If by "fail over" you mean start using, then no, you can't. A failover on an asynch setup will cause recovery to happen. Once a database recovers, it...

One comment -- the syntax of the question only works on SQL 2008 and up. This line:

DECLARE @a VARCHAR ='xyz'

is not supported on earlier versions;...

What's really bad is understanding the question correctly and screwing up the loop counts because it is early in the morning. I counted the 5 loops but forgot to...

Dana Medley (8/13/2012)

---

+ 1 Amen to...

And Lowell, I am blaming Microsoft for creating an application that uses SQL Server as its data repository that doesn't use their own best practices in maintaining its own database....

So why bother making replication able to replicate schema then? There is only one schema change that replication cannot handle -- dropping tables that are part of a publication....

opc.three (8/2/2012)

---

This is exactly what Microsoft is up against. They have...

If someone wants to add a column to the middle of a table, they should get better SQL training. If order matters that much, make a view and change...

opc.three (8/1/2012)

---

It's a least common denominator approach. If SSMS were coded to account for every permutation possible to arrive at the most efficient way to add a column think about...

Lowell (7/31/2012)

---

the reason is to make is a beauty of a gui/user tool.

yes for a simple add column, it's a trivial one line wonder in TSQL.

But they put logic in...

Lokesh Vij (7/26/2012)

---

anthony.green (7/26/2012)

---

Damn, got 3 out of the 4, I thought mirroring wouldn't of been true as it is now a depreciated feature so, wouldn't of thought the two...

Also, you have to consider that SQL will stop a backup even if there are open transactions. I know because we have had a rogue developer who was given...

Steve Jones - SSC Editor (7/20/2012)

---

There was a slight typo in the original question, and I mistakenly added another in fixing it. It should have been:

12:10 AM - Transaction 1...

sestell1 (7/20/2012)

---

jeff.mason (7/20/2012)

---

sestell1 (7/20/2012)

---

Wow, interesting. I'd been under the false impression that the full backup used an internal snapshot to capture the state of the database at the time...