Thursday, 17 April 2014

SQL SERVER 2008 & 2008 R2 - Create Script to Copy Database Schema and All The Objects - Data, Schema, Stored Procedure, Functions, Triggers, Tables, Views, Constraints and All Other Database Objects

Quite Often we get request regarding how to copy all the objects - including schema and data from any database and re-create it on another instance.

SQL Server 2008 & SQL Server 2008 R2 has script generator wizard which does it for us.









Pay attention to the option Types of data to script - select option "Schema and data"










After the script is generated, the next challenge often users face is how to execute this large script as SSMS does not open the file. One can use SQLCMD for the same as shown in the following image

As the file with data will be very large, use SQLCMD to execute the larger script which will create with schema & data.





Failover and Failback in LogShipping - SQL Server 2008 R2

Database State & Jobs on Primary & Secondary Server

Database state on primary server (bhamare3)

Database state on secondary server (bhamare3\named)

Log Shipping jobs on Primary & Secondary Server

Log Shipping jobs on primary server (bhamare3)


Log Shipping job on secondary server (bhamare3\Named)


Check the log shipping is in sync by executing the following query on secondary server (bhamare\named)

select secondary_database,last_copied_file,last_restored_file from msdb..log_shipping_monitor_secondary


you can generate the log shipping sync report on secondary server (bhamare\Named) by

Right click on Instance Name > Reports > Standard Reports > Transaction Log Shipping Status


Backup Logins

If you simply want to make a backup of your SQL Sever Logins for disaster recovery purposes, just follow these easy steps:

On the primary server (bhamare3) launch SSMS & connect to the instance of SQL Server


USE master
GO
IF OBJECT_ID ('sp_hexadecimal') IS NOT NULL
  DROP PROCEDURE sp_hexadecimal
GO
CREATE PROCEDURE sp_hexadecimal
    @binvalue varbinary(256),
    @hexvalue varchar (514) OUTPUT
AS
DECLARE @charvalue varchar (514)
DECLARE @i int
DECLARE @length int
DECLARE @hexstring char(16)
SELECT @charvalue = '0x'
SELECT @i = 1
SELECT @length = DATALENGTH (@binvalue)
SELECT @hexstring = '0123456789ABCDEF'
WHILE (@i <= @length)
BEGIN
  DECLARE @tempint int
  DECLARE @firstint int
  DECLARE @secondint int
  SELECT @tempint = CONVERT(int, SUBSTRING(@binvalue,@i,1))
  SELECT @firstint = FLOOR(@tempint/16)
  SELECT @secondint = @tempint - (@firstint*16)
  SELECT @charvalue = @charvalue +
    SUBSTRING(@hexstring, @firstint+1, 1) +
    SUBSTRING(@hexstring, @secondint+1, 1)
  SELECT @i = @i + 1
END

SELECT @hexvalue = @charvalue
GO

IF OBJECT_ID ('sp_help_revlogin') IS NOT NULL
  DROP PROCEDURE sp_help_revlogin
GO
CREATE PROCEDURE sp_help_revlogin @login_name sysname = NULL AS
DECLARE @name sysname
DECLARE @type varchar (1)
DECLARE @hasaccess int
DECLARE @denylogin int
DECLARE @is_disabled int
DECLARE @PWD_varbinary  varbinary (256)
DECLARE @PWD_string  varchar (514)
DECLARE @SID_varbinary varbinary (85)
DECLARE @SID_string varchar (514)
DECLARE @tmpstr  varchar (1024)
DECLARE @is_policy_checked varchar (3)
DECLARE @is_expiration_checked varchar (3)

DECLARE @defaultdb sysname

IF (@login_name IS NULL)
  DECLARE login_curs CURSOR FOR

      SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name,l.hasaccess, l.denylogin FROM
sys.server_principals p LEFT JOIN sys.syslogins l
      ON ( l.name = p.name ) WHERE p.type IN ( 'S', 'G', 'U' ) AND p.name <> 'sa'
ELSE
  DECLARE login_curs CURSOR FOR


      SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name,l.hasaccess, l.denylogin FROM
sys.server_principals p LEFT JOIN sys.syslogins l
      ON ( l.name = p.name ) WHERE p.type IN ( 'S', 'G', 'U' ) AND p.name =@login_name
OPEN login_curs

FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type,@is_disabled, @defaultdb, @hasaccess, @denylogin
IF (@@fetch_status = -1)
BEGIN
  PRINT 'No login(s) found.'
  CLOSE login_curs
  DEALLOCATE login_curs
  RETURN -1
END
SET @tmpstr = '/* sp_help_revlogin script '
PRINT @tmpstr
SET @tmpstr = '** Generated ' + CONVERT (varchar, GETDATE()) + ' on ' +@@SERVERNAME + ' */'
PRINT @tmpstr
PRINT ''
WHILE (@@fetch_status <> -1)
BEGIN
  IF (@@fetch_status <> -2)
  BEGIN
    PRINT ''
    SET @tmpstr = '-- Login: ' + @name
    PRINT @tmpstr
    IF (@type IN ( 'G', 'U'))
    BEGIN -- NT authenticated account/group

      SET @tmpstr = 'CREATE LOGIN ' + QUOTENAME( @name ) + ' FROM WINDOWS WITH DEFAULT_DATABASE = [' + @defaultdb + ']'
    END
    ELSE BEGIN -- SQL Server authentication
        -- obtain password and sid
            SET @PWD_varbinary = CAST( LOGINPROPERTY( @name, 'PasswordHash') AS varbinary (256) )
        EXEC sp_hexadecimal @PWD_varbinary, @PWD_string OUT
        EXEC sp_hexadecimal @SID_varbinary,@SID_string OUT

        -- obtain password policy state
        SELECT @is_policy_checked = CASE is_policy_checked WHEN 1 THEN 'ON'WHEN 0 THEN 'OFF' ELSE NULL END FROM sys.sql_logins WHERE name = @name
        SELECT @is_expiration_checked = CASE is_expiration_checked WHEN 1THEN 'ON' WHEN 0 THEN 'OFF' ELSE NULL END FROM sys.sql_logins WHERE name= @name

            SET @tmpstr = 'CREATE LOGIN ' + QUOTENAME( @name ) + ' WITH PASSWORD = ' + @PWD_string + ' HASHED, SID = ' + @SID_string + ', DEFAULT_DATABASE = [' + @defaultdb + ']'

        IF ( @is_policy_checked IS NOT NULL )
        BEGIN
          SET @tmpstr = @tmpstr + ', CHECK_POLICY = ' + @is_policy_checked
        END
        IF ( @is_expiration_checked IS NOT NULL )
        BEGIN
          SET @tmpstr = @tmpstr + ', CHECK_EXPIRATION = ' +@is_expiration_checked
        END
    END
    IF (@denylogin = 1)
    BEGIN -- login is denied access
      SET @tmpstr = @tmpstr + '; DENY CONNECT SQL TO ' + QUOTENAME(@name )
    END
    ELSE IF (@hasaccess = 0)
    BEGIN -- login exists but does not have access
      SET @tmpstr = @tmpstr + '; REVOKE CONNECT SQL TO ' + QUOTENAME(@name )
    END
    IF (@is_disabled = 1)
    BEGIN -- login is disabled
      SET @tmpstr = @tmpstr + '; ALTER LOGIN ' + QUOTENAME( @name ) + ' DISABLE'
    END
    PRINT @tmpstr
  END

  FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type,@is_disabled, @defaultdb, @hasaccess, @denylogin
   END
CLOSE login_curs
DEALLOCATE login_curs
RETURN 0
GO


Note This script creates two stored procedures in the master database. The two stored procedures are named the sp_hexadecimal stored procedure and the sp_help_revlogin stored procedure.

Run the following statement
EXEC sp_help_revlogin
The output script that is generated by the sp_help_revlogin stored procedure is the login script. This login script creates the logins that have the original security identifier (SID) and the original password.

Failover

Before disabling log shipping jobs please copy any uncopied backup files from the shared folder on primary server  to the shared destination folder on secondary server by using copy job.

Check all the transaction log has been successfully applied on the secondary server, if not please run the restore job to apply unapplied transaction log backups on secondary server.

Disable Log Shipping Jobs

Disable Log Shipping jobs on primary server (bhamare3)



Disable Log shipping jobs on secondary server (bhamare3\Named)



T-Log Backup 

  • Kill the session open for the DB on which you have to take tail log backup.
  • Manually perform a tail log backup of the transaction log on the primary database specifying leave database in restoring state. This log backup captures any log records that have not been backed up yet and takes the database in Restoring state. The following example creates a tail log backup of the "AdventureWorks2008" database on the primary server.
  • We recommend that you use a distinct file naming convention to differentiate the manually created backup file from the backup files created by the log shipping backup job.




DB on primary server (bhamare3) will go in restoring state.

Restore T-Log Backup

Now restore the tlog backup on secondary server (bhamare3\Named)



The database on the secondary server (bhamare3\Named) will come in online state.


Check all the transactions are happening correctly.

Log Shipping Configuration

Now configure log shipping on secondary server (bhamare3\Named) DB.






Fallback

Run Log Shipping Jobs

Run the log shipping jobs on the primary server (bhamare3\Named)



Run the log shipping jobs on the secondary server (bhamare3)

 


Log Shipping Sync

Check the log shipping is in sync by executing following query on secondary server (bhamare3)

select secondary_database,last_copied_file,last_restored_file from msdb..log_shipping_monitor_secondary


You can generate the log shipping sync report on secondary server (bhamare3) by

Right Clicking on Instance Name > Reports > Standard Reports > Transaction Log Shipping Status



Enabling Log Shipping in SQL Server 2008 R2

Introduction

SQL Server Log Shipping allow to transfer data from one database to a lot of databases. So in Log Shipping we have 3 servers
  1. Primary
  2. Secondary
  3. Monitor (Optional)
*The secondary database can be more than one database.

Log Shipping involves copying a database backup and subsequent transaction log backups from the primary server and restoring the database and transaction log backups on one or more secondary servers

Steps

Create a folder in primary server (LogShipping_Primary) and also in secondary server (LogShipping_Secondary).This two folders must be sharing.

Take full and transaction log backup from the database in the primary Server

Restore this database on secondary server with stand by option.logShippingDB after Restore

On primary server right click >> properties >> Transaction Log Shipping >> Enable Log Shipping
Enable Log Shipping

Configure the backup setting for the transactional log backups
PrimaryServer backup path

  • Network backup path folder: the folder name LogShipping_Primary in primary server put the network path for this folder \\Servername\Foldername
  • Local path: the local path for the folder in primary server like C:\users\DBA\Desktop\LogShipping_Primary
Configure Scheduled job to backup database

4

Add Secondary Server

Add Secondry Server

Connect to select your secondary server

6

Select Secondry Server


Initialize Secondary Database
  • If you want to take full backup and restore it to the secondary server.
  • If you want to restore the existing backup from primary server to secondary server.
  • if you have manually restored the database on secondary server.
Copy Files
In this table you will put the path if the folder in the secondary server \\Servername\\Foldername

Copy Files

Configure the schedule to take the backup files copy from the primary server  to secondary server

10- Configure the Sehedule to take the backup

Restore transactional log : we will select Standby option and Disconnect all user in restore option

Restore transaction log

Configure the schedule to restore the backup taken from the primary server

12
Click OK

Optional (Check on monitor sever instance to monitor the backup status and the job status for the jobs in primary server and secondary server)

Configure the Sehedule to restore the backup

14

Last step in Log Shipping Configuration

Finish

After you finish from the Log Shipping go to the Primary Server to Check the new jobs

16

Return to the secondary server to check the new jobs

17

Note: Check the functionality of Log Shipping by executing all the SQL Jobs which have been scheduled during log shipping. All the jobs should execute successfully.

SQL Server Query Execution Plans for beginners – Clustered Index Operators

In this article we will continue discussing the various execution plan operators related to clustered indexes and what they do, when do the...