learnSQLwithME

Hi guys! Today we will be chatting about taking a database offline. Taking a database offline is the best practice versus deleting a database in production straight away. This way if there are any users that still need to access the database, you can turn the database back online. In Sql Server Management Studio (SSMS) (If your database is participating in an availability group) Remove the database from the Availability Group. Under AlwaysOn High Availability > Availability Groups > (your Availability Group) > Availability Databases > right click the database you want to remove > Remove Database from Availability Group. Now you can refresh your databases and see that your database is no longer being synchronized. Right click your database > Tasks > Take Offline. Now just verify that the database is offline: That's it! If you have any questions related to this post, please put them below. Thank you and Happy reading, -...

Hi everyone! This post will be a quick and easy fix. Scenario: You have a SQL agent job that will not execute. The specific error says: Could not obtain information about Windows NT group/user ' domain\username ', error code 0x5. [SQLSTATE 42000] (Error 15404)). Here's how to fix this: Double click the SQL agent job to open the job properties. On the 'General' page change the Owner of the job to 'sa' by clicking the box to the right of the field and then checking the username 'sa exists. Hit 'Ok' . Your job will now run successfully. I told you this was a short post :). If you have any further questions, please post below. Thank you and Happy reading, -marshé hutchinson #learnSQLwithme

Hi everyone. Welcome to my first post. In my environment, we still utilize replication. What in the world is replication? Replication is a way to copy data from your source to destination server continuously. Imagine if I am adding records to a database on your source server throughout the day and I would like the data updated to the target server. That's what is possible with replication. Here's a great article for further reading: https://www.sqlshack.com/sql-server-replication-overview-of-components-and-topography/ Back to the issue at hand. 1. After reinitializing replication on the QA server, I received this message under the replication monitor > Distributor To Subscriber History: The concurrent snapshot for publication is not available because it has not been fully generated or the Log reader agent is not running to activate it. This was the other error message I was receiving under the replication monitor > Publisher To Distr...