learnSQLwithME

Hi everyone! As a database administrator, you always need a copy of your data and data processes for: migrating servers disaster recovery backup procedures/best practices This post covers a simple Powershell script. The script is to take a backup of all the SQL agent jobs on your SQL server instance. If you ever needed to recreate all the jobs on another server, all you would have to do is execute the SQL script. I. In SSMS (SQL Server Management Studio), create an empty .SQL file and save it with this naming convention: I.e. SqlAgentJobs_PROD01.sql } This file will represent all the SQL agent jobs on the primary production SQL server. II. Copy the "SqlAgentJobs_PROD01.sql" file from above to a network share. III. Run the Powershell script below in  Powershell ISE as administrator: ##migrating jobs from one server to another with the replace command $SqlConnection = New-Object System.Data.SqlClient.SqlConnection $SqlConnection.ConnectionStrin...

Hi everyone! Today's post is about Postgres SQL. In my environment we are using Postgres SQL as one option for the backend of AWS (Amazon Web Services). That's right. We also have another option - MySQL. This post however will focus on the Postgres SQL error: "ERROR: must be owner of database databaseName" Scenario : I encountered this error when I was trying to drop a database from an AWS cluster. Amazon allows you to group databases inside of containers. These containers still have the same logic as SQL schemas which hold our database in SQL server. You can read more about AWS clusters here . Solution : This is very easy. It's in the error. All I have to do is make myself the owner of the database so I can delete the database. I. If your user account does not already have read/write privileges, then you will need to sign in to the Postgres cluster with an admin account so you can grant read/write access to your user account. II. If your ...

Hi guys! Today's post is on exporting a deadlock graph with Idera Diagnostic Manager . Idera Diagnostic Manager is a great tool to track performance issues in your SQL environment.  Let's get started. Open the application: Select the server: S elect the Sessions tab: Select the Blocking option on the Sessions tab: Select the History Browser : Look for the culprit with a critical status of the Historical snapshots area in the bottom right: a) b) c) View session details for the culprit (session) that is causing all the issues: a) b) You can gather all the details to email to effected teams. Go back to the session blocking view: Under Deadlock Reports , double click the most...

Hi guys! As you know, in my environment I use Redgate SQL Clone . You can check out an older post I have here on what you can do with the SQL Clone application. Today's post is on how to remove SQL Clone agents from a server. Let's get started. I. Remove a clone agent from a server that is still online Removing a clone agent from a server that is already online is relatively easy. Just remote desktop into your server > under services, stop the "SQL Clone Agent version#" service. Then under control panel, uninstall "SQL Clone Version#". II. Remove a clone agent from a server that is offline. Here's how to remove SQL Clone from a server that has already been shut down. Note : This method will also work on servers that are still online. Log on to the server and open a powershell window/prompt as administrator. Use the script below. Inside your powershell prompt enter:  Connect-SqlClone -ServerUrl ...

Hi guys! Today's post is on how to delete an AWS cluster. If you are brand new to Amazon Web Services, here is some quick vocabulary for you: instance (database) cluster snapshot Let's jump right in. Part 1 - How to Stop an Instance or Cluster in AWS: Sign on to the AWS console. Enter your MFA (multi-factor authentication code) Under "RDS Services", choose databases. Search for your database or cluster name Select the radial button to the left of the instance or cluster name you would like to stop. Note: In this example, stopping the instance is the same as stopping the entire cluster because there is only 1 instance in this cluster. If this cluster had more than 1 instance, you would need to stop all of the instances for the entire cluster to be stopped. Otherwise, the cluster would still be operational. Part 2 - How to Delete an Instance or Cluster in AWS: If we are picking up from the last step of Part 1 where we would like to no...

Hi guys! Today's post is a very common request. What do you do if you have to add a SQL user to an instance, but don't know what the password is? It's actually an easy fix. First, you need to find the SID for the SQL user so you can map the user irregardless of the instance you are on. --Step 0 SELECT SUSER_SID(' yourSqlUser ');   GO    Note: You need to copy the result from the results pane in SSMS. I.E.: 0x6FE56AD1A3AA6C40A1336814621ED733 Then you have to run 3 T-SQL scripts that will generate the permissions you need. You will need to put the results from the results pane together. --Step 1 SELECT 'IF (SUSER_ID('+QUOTENAME(SP.name,'''')+') IS NULL) BEGIN CREATE LOGIN ' +QUOTENAME(SP.name)+ CASE  WHEN SP.type_desc = 'SQL_LOGIN' THEN ' WITH PASSWORD = ' +CONVERT(NVARCHAR(MAX),SL.password_hash,1)+ ' HASHED, CHECK_EXPIRATION = '  + CASE WHEN SL.is_expiration_checked = 1 THEN 'ON' EL...