Something broke with that link...

http://www.buzzfeed.com/daves4/jokes-only-nerds-will-understand

Not true. Publisher can be in any recovery model

Subscriber database must be in...

No.

What exactly happened and why is it a concern?

Ignoring my mail, so hadn't noticed. No notifications today.

No.

You can create a procedure that refers to tables that don't exist, but if the tables do exist, the columns referenced must all be there.

DELETE FROM @TableVariableName

Yes, it will take some memory, just for its threadstack which is 2MB (I think) on x64.

If you drop the DB then the first thing SQL has to do is recreate the files, including zeroing them out.

Try taking the DB offline with rollback immediate.

Virtually nothing.

All that tells you is the number of reads (pages read from memory) that the connection did from the time it connected...

It will use the first then the second then the first again then the second again, etc. The log files will only grow if both are full.

IT researcher (7/8/2013)

---

I am not using differential backup in my environment. i use full backup and transaction log backup.So in this case taking full backup and copy only...

Yes, they are a SQL Server connection and they hold a small amount of memory (2MB each I think) for the thread stack

You don't need the TempDB files. Master...

He's talking about the system databases, not user databases...

Joie Andrew (7/8/2013)

---

Copy-only full backups are the same concept as copy-only log backups. It does not write an archive bit so the log chain is not interrupted with the backup....