learnSQLwithME

Hi there. This post will be a quick and easy fix. If you are not already aware, availability groups are the replacement for mirroring in SSMS (SQL Server Management Studio). We like to utilize availability groups so that there is minimal data loss. Also, in the event of some natural disaster or disk failure on a server that is participating in an availability group, the data will fail-over to a backup server (replica). I was adding a database to an availability group when I received the error: Database "database_name" database is not in full recovery mode on each of the server instances. The full recovery model is required for a database to participate in database mirroring or in an availability group. [SQLSTATE 42000] (Error 1465). The error is exactly as it sounds; The database is not in the full recovery model. To fix this: I. In SSMS, right click the database to see the properties. On the Options page, change the database recovery model to Full. II....

Hello again. This post is related to automating SQL server tasks with Task Scheduler. In this example I was tasked with exporting SQL server agent jobs twice a month. To achieve this, I setup a task scheduler task that ran a PowerShell script that: establishes a local connection to the SQL server. cleans the file before writing to the .sql file to avoid adding on (appending) results on subsequent runs of the task scheduler task. when a connection is established, export the SQL agent jobs on the server to a .sql file on a remote server. sends a confirmation email via the SQL server database mail profile that the SQL agent jobs were exported to the specified remote server path. That was a mouthful. Now that you know my task scheduler task is calling a PowerShell script, let's get back to why it is failing.  The good news is this error is not related to the script. The error launch failure means the task could not even run. This is most likely due to a permissi...

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...

This blog documents different SQL scenarios I have encountered on the job or assisting friends. This information is intended for those who are new to SQL. I hope that SQL beginners will find this information useful. Note: A SQL beginner would be someone that has just completed their first boot camp or is a new junior database administrator; someone that would be familiar with the various technologies and terms used. Thank you and Happy reading, -marshé hutchinson #learnSQLwithME