Pre - Requisites of Log Shipping

The following are the prerequisites to configure Log Shipping SQL 2008

1. SQL Server 2008 Enterprise Edition, SQL Server 2008 Workgroup Edition, or SQL Server 2008 Standard Edition must be installed on all server instances involved in log shipping.

2. The servers involved in log shipping should have the same case sensitivity settings.

3. Enable Remote connections to the server in SQL Server surface are configuration, by navigating to start menu--->All Program--->Microsoft SQL 2008--->Configuration tools--->Surface Area Configuration tool--->Select Surface Area configuration for Services and Connections option--->Select Remote Connections--->Select Local and Remote connections by using TCP and Named Pipes option or else you can also use local and remote connections using TCP\IP only and click OK.

4. The SQL Services in both the primary and secondary server should be the same with same password. Preferably --a domain account.

5. The DB to be log Shipped should be in Full Recovery or Bulk logged recovery model, so that T-logs can be applied, else you cannot configure log shipping. Use the below command to change the recovery model or else you can change in the SSMS by right clicking the DB properties.

6. Shared folder should be created in Primary server to hold the T-Log backups.

Comments

Self Introduction and Responsibilities of a SQL Server DBA.

Hi, Self Introduction: I am Vang chew bigger , currently I am working with Citronics , Here my role is SQL Server Database Administrator , I am having 3+ yrs Exp in SQL SERVER DBA with T-SQL, I have experience on SQL Server 2000, 2005 and 2008, I have a great experience on installation and configuration of SQL SERVER versions, and also applying the patches, hot fix, services packs and RTM’s accordingly, involved in upgrading on in place and side by side as per client requirement, and also Migrating the database on SQL SERVER 2000 to 2005 and 2008, Solid experience on configuring and maintenance of High availability SQL Server solutions, including Log shipping, Database Mirroring, Replication(Transactional and Merge) and SQL Server Clustering., having experience on performance tuning on server level, database level and query level, Responsible for working with application developers in identifying, resolving and proactively working to prevent performance or oth

SQL Server 2016 Windows Server 2016 Firewall Rule Step-By-Step.

SQL Server 2016 Windows Server 2016 Firewall Rule Step-By-Step. Opening Firewall in SQL Server 2016. Once the SQL Server is installed on the machine. We must enable the incoming traffic i.e., from the application to the SQL Server Database. For this purpose, we must create rule for SQL Server ports so that the application can connect to database & perform the CRUD operations on the tables. Now Let’s start Step-by-Step to enable it. 1. Start System and Login (As Administrator); 2. Open Control Panel. Click on Windows Firewall; 3. Now click on Advanced Settings; 4. Windows Firewall console open. If you click on Properties (right side) – you can disable firewall for all networks. We going to Inbound Rules (left side) for our rule creation; After Clicking on the Inbound rules. We will see the below screen. Click on New

Shrinking a SQL Server Log File with Database in Always ON Availability.

Shrinking a SQL Server Log File with Database in Always ON Availability. Once we had a situation in our production server that the database which is in Always ON Availability group has been grown to the maximum size. Many of them say that we can't shrink the log file as the database is in Always ON and we should take the downtime to perform the operation. But we shrink-ed the database log file to 5 GB from 180 GB. Steps are as below: --To Check the Number of pages allocated by the LogFile. DBCC LOGINFO --To check the file sixe sp_helpdb [SQLPantry] --To check the Log file Size DBCC SQLPERF(LOGSPACE) The above statement will show the logspace of all db at present situation. --To check the Log_reuse_wait description of a log file. select log_reuse_wait_desc,* from sys.databases The above statement will show the status of the log whether it has to be backuped i.e., LogBackup, Nothing, Active Transaction. When ever there is status as Activ

MS SQL SERVER DBA

Search This Blog