Yep. Without the rest of the error message, I can't even hazard a guess. Jeff is probably right (says Grant all the time).

Ha! Clearly I type slowly and/or too much. Agreement with @Ant-Green. +1

You're in a bit of a tough spot, not having a network. However, probably, your best bet would be to use Azure SQL Database (or AWS RDS SQL Server,...

All the votes for Johan's solution with Extended Events. #TeamXE

Also, I unspammed TangoVictor's first post, not noticing the second. Not sure why that happened. I put it back to spam...

For the restore operation, according to the documentation, you can go as far back as a 2005 backup and restore it to 2019. As to the in-place server upgrades,...

The only negative to any approach is when it's either destructive of your data, or doesn't work well. If, in your testing, dropping and recreating the indexes works better, then...

You could encrypt it with a password. You can use the Data Protection API (DPAPI). Here's an article on it. Another showing how to create a password protected...

Auto close is a pain. Happy you fixed it.

Hey all!

Thanks for the feedback. I have no arguments to make against any of it. As I said in the editorial, all I have are questions here.

One point I will...

Yep.

There are trends. More often than not, I see having a clustered...

Compression means more rows stored on a page, reducing I/O by reducing the number of pages needed to retrieve a value and the number of pages needed in memory.

Columnstore is...

There's no obvious issues with the code, so it's really a question of the right indexes to support it. That assumes that the value in the WHERE clause provides actual...

Testing is your buddy. Lots and lots of testing. There is no true one-size-fits-all approach to doing things in SQL Server.

Since the clustered index itself redefines data storage, the choice...

I'd just jump in and start using XE. First, there is no way of completely avoiding the XML. It's fundamental to the process. However, I recently wrote a blog...

The failover will cause disconnects on the application side. That's unavoidable. However, the overall down time will be very small. In flight transactions will be lost. All committed transactions will...