learnSQLwithME

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

Hi guys! Today's post is on how to install SQL Server. In this demonstration I will be installing the Developer edition of SQL Server onto a DEV server. Let's get started. I have already copied my install file to the DEV server. I also went ahead and created my install directories on the different drives: I.e. D:\Data5, L:\Log5, T:\Temp5 and V:\Backup5. Note: My directory ends with the number 5 because I already have other instances installed on this server. When installing a new stand alone instance on a server with existing instances, you need to create a new directory for each instance AND make sure that your directories are on different drives as well. Go back to your installation file > rt click the file > Mount Run the setup file as administrator. Perform a New Stand Alone Installation. Skip auto updates. Perform a new installation. Enter the product Key and Accept the License Terms. SQL Server Feature Installation Add SQL Server Replication (under

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