As others have said, the log backup is the easiest one to explain. Any completed transactions that are currently in the log are what get backed up. Those completed transactions...

The big value will get added to the last page, and then everything else will be inserted behind it. Without testing I couldn't see just to what degree having one...

Is it just the one row? Or are you regularly going to be inserting rows at the end of the chain along with rows at the start? If the former,...

+1 For Denny Cherry. My other preferred resource on Virtualization is David Klee. You can pick up a lot of his stuff here[/url]. While this is a major undertaking, it's...

Just remember that whatever memory you give to SQL Server, it's going to use all of it. It will load everything into cache and keep it there as long as...

There are security patches that it's probably a good idea to get on the servers for all the reasons Gianluca lists. However, I've managed servers that stayed up regularly for...

Has the database that is failing its backups passed DBCC?

Brandie Tarvin (3/1/2016)

---

As part of some classes I've been taking lately, I had to do record some video presentations. I'd love some feedback on my latest, if none of you...

Before you repair with the data loss (which could be severe), identify that object by the object ID. If it's a non-clustered index, you can just drop it and recreate...

The basics will work. Mainly T-SQL is going to be fine. But I'd just get the 2014 SSMS out to people. The backward compatibility works, so it's safe.

There is no right answer. It's a set of trade-offs. Sacrifice some CPU and I/O to update the statistics and rebuild any execution plans versus have execution plans be out...

No. Full backups and log backups can be mixed and matched as long as you have the log backups in order. Taking a full backup, in and of itself, never...

If the process is, record some data and close the connection, open another connection later and read that data, then I'd say you just need a regular table. Don't try...

No. That's not about accessing the server. It's an internal, SQL Server to SQL Server communication mechanism. Read about it here. It's deprecated and Microsoft doesn't recommend its use.

Global temporary tables are removed after the last process that is referencing them closes. Because you're closing the process, and no other process is referencing the table, it gets closed....