Posts

Showing posts from June, 2021

SYNTAXES FOR HOW TO MAKE YOUR DATABASES FULL TO SIMPLE AND SIMPLE TO FULL RECOVERY MODELS

  To make your database in the Full recovery model: 1 2 3 4 USE [ master ] GO ALTER DATABASE [ publisher ] SET RECOVERY FULL WITH NO_WAIT GO To make your database in the Bulk Logged recovery model: 1 2 3 4 USE [ master ] GO ALTER DATABASE [ publisher ] SET RECOVERY BULK_LOGGED WITH NO_WAIT GO

SQL SERVER –Different Ways to Find Recovery Model for Database

Image
  This is a very easy method and it gives all the database information in one script. SELECT  name  AS  [Database Name] , recovery_model_desc  AS  [Recovery Model]  FROM  sys.databases GO Method 4 This method provides only one database at a time. SELECT  'ADVENTUREWORKS'  AS  [Database Name] , DATABASEPROPERTYEX ( 'ADVENTUREWORKS' ,  'RECOVERY' ) AS  [Recovery Model] GO My recommendation

Transfer logins and passwords between instances of SQL Server

  Transfer logins and passwords between instances of SQL Server This article describes how to transfer the logins and the passwords between different instances of SQL Server running on Windows. Original product version:    SQL Server Original KB number:    918992 Introduction This article describes how to transfer the logins and passwords between different instances of Microsoft SQL Server.  Note The instances may be on the same server or on different servers, and their versions may differ. More information In this article, server A and server B are different servers. After you move a database from the instance of SQL Server on server A to the instance of SQL Server on server B, users may be unable to log in to the database on server B. Additionally, users may receive the following error message: Login failed for user ' MyUser '. (Microsoft SQL Server, Error: 18456) This problem occurs because you did not transfer the logins and the passwords from the instance of SQL Server on