Level 0 Extended Properties

Using Tempdb

What's a Normal SQL Server?

Many of us have worked in environments that have a number of SQL Server instances. Different versions, editions, and mostly different hardware profiles. We deal with different applications and software that places different demands and requirements on our database systems. Some of us are even dealing with multiple datastores, trying to integrate SQL Server with […]

Database Extended Properties

Do You Think About CheckDB?

Running checkdb is part of ensuring your database health and data integrity. Steve notes that you might want to review that you have the best strategy for your organization.

Clearing Database Cache

Adding a Database with Polybase External Tables to Always On Availability Group

Learn how to ensure your PolyBase objects are accessible from all nodes in an Availability Group.

[Video] Free DBA Training Month: Configuring TempDB, Lock Pages in Memory, and the DAC

While you’re stuck inside wondering if you’ll ever be able to attend a user group meeting again, I’m giving you free access to training materials that your boss probably wouldn’t have been nice enough to buy you anyway. So far this week, we’ve covered DBCC CHECKDB, how to set up Ola Hallengren’s maintenance scripts, and restoring for oops deletes. Today, let’s talk about two common configuration issues. Don’t dilly-dally on these though: these blog posts will be online during May only, and they’ll disappear on June 1.

Tempdb Default Size

How to Attach a SQL Server Database without a Transaction Log and with Open Transactions

You want to attach a SQL Server database that does not have the transaction log files and get the following error: "The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to a hardware or environment failure." In this tip I will help you to successfully attach the transaction log to the problematic SQL Server database.