SQL Server Always On – Monitor The Redo_Queue_Size

Cause sometimes you need to check why replication is slow or halted. For example, like during an IO storm - no hurricane pun intended. Say you have transnational replication over an Always On (SQL Server Availability Groups) environment that's a publisher. To see in the Dashboard just add the column, this is what it looks… Continue reading SQL Server Always On – Monitor The Redo_Queue_Size

I’ll be presenting Saturday 6/9/2018 @NovaSE – 1:30pm Room 3046

Keeping a good thing going. Register here (FREE): https://www.sqlsaturday.com/755/registernow.aspx You can extend the invite to your friends and colleges if you think they’ll be interested in the topics. I'll be presenting at Nova South Eastern this Saturday afternoon at 1:30pm in Room 3046 of the Carl DeSantis Building (3301 College Avenue, Carl DeSantis Building, Davie, FL 33314). Here's my… Continue reading I’ll be presenting Saturday 6/9/2018 @NovaSE – 1:30pm Room 3046

SQL Sync Logins – Domain Accounts

Hypothetically, say you can't grant dbo permissions. Instead you just need read, write and execute for stored procedures. Common Database-Level Roles are: db_datareader, db_datawriter, and my personal favorite db_executor. Ideally, you would use a domain security group (making the accounts members of the group) and grant the group access to the SQL Server instead of… Continue reading SQL Sync Logins – Domain Accounts

SQL Server Error – Incorrect time syntax in time string used with WAITFOR.

This is a simple one but it doesn't stick until you write/read about it.  Note, I use WAITFOR DELAY to pause/sleep the session between batches or T-SQL commands. For logic reasons, sometimes, I just gotta buy myself a few seconds for one thing to finish, before I start the next one. Ref: Control-of-Flow (lots of goodies… Continue reading SQL Server Error – Incorrect time syntax in time string used with WAITFOR.

Select and Start a SQL Job without knowing the full job name or history

So I was trying to figure out how to get the TLog backup job's name based on Back History because in this case, the job name happens to vary between SQL Server Instances. Sounds simple enough (well...not quite), then I realized for new SQL Server instances this job might not have even ever ran...so there went… Continue reading Select and Start a SQL Job without knowing the full job name or history