Sometime while connecting MSSQL 2005 Remotely OR locally using MSSQL Management Studio (using user as SA) it throw following Error

Login failed for user 'sa'. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18452&LinkId=20476

This Error occurs when SQL Server doesn’t support SQL Server Authentication Mode (Mixed Mode for MSSQL 2000). This issue can be fixed using following Steps:

1) Connect the MSSQL server using Windows Authentication of the server.

2) Right Click on the server name in the tree on the left and go to properties.

3) Click the Security Option. Now under Server authentication Select “SQL Server and Windows Authentication Mode” and press OK.

Now try to connect MSSQL using SA user. Please refer Microsoft KB Article 840219 for more information

Sometime due to some technical problems or uncleaned shutdown master database of MSSQL gets corrupted and while starting MSSQL service it throws following Error

Application Log in Event Viewer shows following Error

Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it.

The above error shows that the System Database like Master has been corrupted. To fix this issue we need to rebuild the MSSQL system databases from Installation Disk.

1) Insert MSSQL Installation Disk in Optical Disk Drive

2) Go to Command Prompt (Start >> run >> cmd >> Enter)

3) Execute Following Command:

Here, [Instance Name] will be the name of the MSSQL instance you want to set like MSSQLSERVER and [Password] will be the sa password for MSSQL.

Now try to start MSSQL service.

Sometime while connecting to MSSQL Server Configuration Manager it throws following Error

Cannot Connect to WMI Provider. You do not have permissions of the server is unreachable. Note that you can only manage SQL Server 2005 servers with the SQL Server Configuration Manager.
Invalid namespace[0x8004100e]

I have searched on Google and found that it happens when 32bit MSSSQL application is installed on 64bit Server and they suggested to execute the following command to fix the issue.

mofcomp "%programfiles%\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof"

MOF files are appropriate for static management data or dynamic management data. Static data includes details such as the computer user’s phone number, office number, and name. Dynamic data includes details such as Microsoft SQL Server(tm) database sizes and applications installed with Windows Installer.

Few days ago while working on MS SQL 2008 Transactional Replication I have faced following two issue
1) To find out the total number of tables to verify that Primary Server and Secondary server have same table count.
2) Tables without Primary key: After replication setup I have found that some tables were not replication. When I checked the logs it showed following error

“This table cannot be published because it does not have a primary key column. Primary key columns are required for all tables in transactional publications.”

1) Find Number of Tables:

a) Open MSSQL management studio and login using SA password or Administrator access.
b) Click on “New Query” and select the database using following command

c) now execute following Query to count the total number of tables in the database.

You will get result like:

2) Tables without primary key:

a) Open MSSQL management studio and login using SA password or Administrator access.
b) Click on “New Query” and select the database using following command

c) now execute following Query to find the Tables without Primary Key.

Output tab will show result like:

After you configure the Distributor Server (Guide to MS SQL 2008 Transactional Replication (Configure Distributor) Part-II) now I will explain how you can create & configure the Publisher.

Create & Configure Publisher

1) Select the Transactional Databases: Login to MSSQL Management Studio and go to  Server >> Replication (right Click) >> Publisher Properties >> Publication Databases >> Select the database you want as Transactional Database and press OK.

2) Now under Replication Right click on Local Publication and select “New Publication…”

3) New Publication Wizard window will open; Press Next.

4) Publication Database: Select the database you want to publish and click on Next.

5) Publication type: You have to select the publication type you want to create. Select “Transactional Publication” and click on Next.

6) Articles: You have to select the objects which will be published. If you have stored procedures and views in your table you can either publish along with views or stored procedure.

7) Filter Table Rows: If you want to filter rows or don’t want to publish any row you can add filter here or you can just press Next without adding filter.

8) Snapshot Agent: You can manage when Snapshot agent should run. You can configure it to run immediatly or you can schedule it. Press Next.

9) Wizard Actions: Select the operations and action wizard will do. Select both the options and click Next.

 10) Script File Properties: Mention the path where publication file will be created and press Next.

11) Summary will be provided; press Finish to complete it and you will get following screen once New Publication has been created successfully.

The publication that you have created will appears under the Replication folder in SQL Server Management Studio.

Verify the status of Replication Agent

If you configured the “Snapshot Agent to start immediately” (on step Number 8) as recommended, you can now verify the progress of the Snapshot Agent by using Replication Monitor.

1) Login to MSSQL Management Studio and go to  Server >> Replication >> Local Publication (right Click) >> Launch Replication Monitor

2) The Publisher is now listed under the My Publishers node of Replication Monitor. Right side panel of the Replication Monitor will show the subscriptions (as we have not yet added any subcriptions it doesn’t show any).

Now go to Agents tab and make sure Snapshot agent and LogReader Agents are running

In Part IV (on Monday) I will explain how to configure Subscriber on which data from Publisher will be pushed.

In Previous three parts I have explained about

1. Transactional Replication
2. How to configure Distribution Server
3. How to create Publisher

 Today in last part of this series I am going to explain how you can create the Subcriber to the Publisher which will complete the replication setup. Before we start the configuration please make sure that the hostname of both the servers are configured properly and include proper enteries in hosts file (Please refer Part-I for more information).

Creating a Subscription

1) Go to Management studio (On Publisher Server) and right click on the Publication you have created >> New subcriptions…

2) New Subscription Wizard will open. Press Next

 3) Publication: Select the Publication Server from the Drop-down list and then select the Database and publication. Press Next after selection.

 4) Distribution Agent Location:  There are two type of Subscription i.e. Push Subscription and Pull Subscription using which we can setup replication. In Push Subscription publisher server pushes any changes made on database to the subscriber where as in case of Pull Subscription subscriber pull the data from publisher on a specified time. Push method is useful when the changes in database need to be replicated as soon as they occur.

So, select Push Subscription and press Next.

5) Subscribers: Here you have to select the subscriber i.e. Slave-DB, from the drop down “Add Subscriber” select “Add New SQL Subscriber…“

You will now get a MSSQL Login prompt which is similar to MSSQL Management Studio. Login to the Subscriber server using the “Hostname” of the server and “SA” Login Details.

Select the Subscriber name and in “Subscription Database” column client on drop-down which will show all the databases on subscriber server. If you have created the database on subscriber just select it or click “New database“. Press Next.

6) Distribution Agent Security: This Page allows you to configure Agent security for each Subscriber that you have added, to ensure that the Distribution Agents have the correct permissions.

I have configured this using “SQL Server Agent” User as it already in Publisher Access List (PAL). The Windows user that you select must meet the following conditions:

1. The user is included in the PAL.
2. The user should be a member of the db_owner fixed database role in the subscription database.
3. The user has read permissions on the snapshot share.

Enter MSSQL SA Login Details and press OK. On the Distribution Agent Security window, click Next.

7) Synchronization Schedule: By default Distributor Agent runs synchronization continuously, keep it as it is and press Next.

 8) Initialize Subscriptions: Select Immediately in the Initialize When and press Next.

9) Wizard Actions: Select both the options and press Next.

10) Script File Properties: Mention the path where Subscription file will be created and press Next.

11) Complete The Wizard: Summary of configuration will be shown. Press “Finish” to complete the subscription wizard.

12) Allow sometime to get it configured and you will able to see following screen when everything is properly configured.

Close the window and go to MSSQL Management Studio and open Replication Monitor for the Replication you have configured. You will able to see the Subscriber name and status now.

Now you can test the replication by adding or inserting in any table on publisher and it will get replicated in subscriber database as well.

Replication is can be defined as a process of copying or reproducing information between two or more resources to improve reliability, fault-tolerance or accessibility. Replication can be configured on LAN, WAN or on Internet for database where same data is copied and stored on multiple database servers or for web services where website data is distributed on various locations to increase the availability of website/database in case of any failure at one location.

Database is a very important constraint of any website or origination as it stores all the data. Any problem or failure in database server can lead many problems like work stoppage, unwanted downtime, loss in terms of money and time etc. to over come such problems most of the organization opt for the database replication solution. Most of the database servers like MySQL, Oracle, MSSQL supports database replications and provide various tools for the it.

In this series I am going to explain how you can configure MSSQL 2008 Transactional Replication between two servers which are located in countries on two different continents i.e. America and India. Transactional Replication is a automatic process of distributing changes between master and slave. In this process data is copied in real-time from the master server which is termed as publisher to the slave server which plays the role of subscriber. On its first run Transactional Replication makes complete copy of the Publisher data, and then all subsequent copies transfer modified data to the Subscriber only. Microsoft SQL Server replication uses a publish, distributor and subscribe relation.

Publisher : Publisher is the Primary or Master server which host the original data or database where actual or real-time changes/updates are made.
Subscriber : The Secondary or slave server which gets or fetch data from Primary (Publisher) Database.
Distributor : This is a system or server which manage the data flow in complete replication setup. We can configure Distributor and publisher on single server.

The Snapshot Agent prepares snapshot files of tables and database objects and records synchronization jobs on distributor. Log Reader Agent monitors the transaction log of each database configured in replication and copies the transaction recorded by the Snapshot Agent. The Distribution Agent moves the initial snapshot jobs and the transactions held in the distribution database tables to Subscribers.

Transactional replication is helpful when:

• You want the changes made on primary server get reflected on secondary server as soon as they occur.
• You want database to follow ACID properties.
• Availability or connectivity of subscriber to the publisher is frequent.

Scenario:
User X have a website hosted in a US based Datacenter and the website is expected to have heavy traffic which is going to put lots of stress on database. Data of the website including user data, their profiles and other information is stored in the MSSQL 2008 Database. Now the owner want to configure a replication of database (in a remote) to increase the availability and fault-tolerance for the database, so he contacts a datacenter in India to Host his secondary database server in their facility.

In next post (Guide to MS SQL 2008 Transactional Replication (Configure Distributor) Part – II) I have explained how to configure the servers to host replication and steps to configure distribution server.

Scenario

Your Company/Organization/Institute maintains certain data in MSSQL 2000 but now on suggestion of System Analyst or database administrator you want to move the data to MySQL 5.x.

Questions?
1) How to migrate the data?
2) Do we need to recreate the complete database schema?
3) Can we use any third Party Application to convert it and how feasible it will be?
etc.

Solution

Using following steps you can easily move/convert the data from MSSQL to MySql (Only data will be moved).

Downloads Required Tools

1) MySql ODBC connector: MySQL ODBC Connector will help Windows OS to configure MySQL as Database Source Name (DSN). It can be downloaded from http://dev.mysql.com/downloads/connector/odbc/5.1.htm

Install MySql ODBC connector on the Server.

Installation of MySql ODBC connector is pretty easy. You will just have to run setup file and follow the instructions.

Configure MySQL Database Source Name (DSN)

Database Source Name or DSN specifies a data structure that contains the information about a specific data source or database that an Open Database Connectivity (ODBC) driver needs in order to connect to that data source or database. To add new DSN follow the instructions given below

1) Go to “Control Panel -> Administrative Tools -> Data Source” which will open following windows.

Click on “Add…” to add new DSN

2) Select “MySQL ODBC 5.1 Driver” from the list and press “Finish”

3) Once you press Finish “MySQL Connector/ODBC Data Source Configuration” window will open.

Here, provide the information about DSN, database, password etc. I have used Localhost as TCP/IP Server as I have the MySQL server installed locally and migrating it locally. Once the data is filled you can test the DSN connectivity with database. Then Press Ok to configure the DSN.

4) Now ODBC Data Source Administrator will show the Datasource which you have created.

Export/Migrate Data from MSSQL to MySQL using DSN

1) Go to “MSSQL Enterprise Manager >> Databases >> Right Click the database you want to migrate or export >> All Tasks >> Export Data …“

2) You will get “Data Transformation Services Import/Export Wizard” Window. Press next.

3) Choose Source: You have to select the Data Source from where the data will be migrated. As we are going to migrated data from MSSQL to MySQL select “Microsoft OLE DB Provider for SQL Server” and the name of database which you want to migrate.

4) Select Destination: Select “MySQL ODBC 5.1 Driver” from dropdown list which will show the list of DSN in drop-down under “User/System DSN“. Select the DSN you have created and enter the login details.

Press Next to Continue.

5) On “Specify Table Copy or Query” select “Copy table(s) and view(s) from the source database” and press next.

6) Select Source tables(s) and view(s): Select the tables which you want to migrate. I have pressed “Select All” for complete database migration.

Press “Next“

7) Select “Run immediately“; press Next and on next screen press Finish to start Migration.

Now its time to have a cup of coffee and depending upon size of database it will take 20-30 minutes to complete.

Microsoft SQL Server is a relational model database server produced by Microsoft and it’s Installation is quite Easy using GUI where a user has to selects the options which he/she needs with the database server and install it. We can automate the installation procedure and make it so simple that MSSQL can be installed using a single command.

Automating SQL server installation is made easier in MSSQL 2005 version and we can define the components which need to be installed with setup.exe via command prompt OR we can create an ini file which will contain all the information about the installation. In this post I will explain the steps to install MSSQL 2005 using command prompt with the help of single command.

Install MSSQL using Command Prompt (By Defining all modules in command)

1) Insert the MSSQL installation media into the disk drive.

2) Open Command Prompt (Start >> Run >> cmd >> Enter)

3) Execute following command

Here, ADDLOCAL is set to “All” which will install all the components and modules bundled with the MSSQL. If you want customized modules then you can declare the modules instead of “All“.

Install MSSQL using .ini file

1) Open Notepad (Start >> Run >> Notepad >> Enter)

2) Insert all the “Installation Parameters” in that file. Following is the sample file which I have used to install MSSQL on my System

Here, PIDKEY will be the Product Key of the product shipped with MSSQL.

3) Save this file with extension .ini (like sqlsetup.ini)

4) Execute following command to run the setup

Points to Note:

1) While specifying the accounts like SQLACCOUNT, AGTACCOUNT and SQLBROWSERACCOUNT make sure you define proper users. Users can be

2) Microsoft provides a template.ini file in the installation media but I would strongly recommend to remove the options that you don’t want.

You can refer to Microsoft tutorial for more information and component help at http://msdn.microsoft.com/en-us/library/ms144259.aspx

Sometime while setting up MSSQL Replication you will receive following error at the time of connecting Slave or Secondary Database Server.

Detailed Error:
TITLE: Connect to Server
——————————

Cannot connect to failover-db.

——————————
ADDITIONAL INFORMATION:

SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, ‘WIN-PNHS6NVSKPI’. (Replication.Utilities)

——————————
BUTTONS:

OK

Cause:

The problem mainly occurs when you change the computer name of the server after installation of MSSQL Server but even after reboot MSSQL uses the OLD Computer name as network name and the SQL Server instance name

Here,
OLD NAME of the Server was: WIN-PNHS6NVSKPI
Changed or New Name of the Server is: FAILOVER-DB

Solution.

1) Find Current Network Name and SQL Server Instance Name
First we need to check the Network name and the SQL Server instance name stored in the database. We can find it execute following commands in MSSQL Management Studio.

sp_helpserver
select @@servername

sp_helpserver: This Query or command shows the information of a particular or a replication server. This shows the server name, network name, identication number and collation name of the server.
select @@servername: This Query will return the server name on which the query is executed.

Following were the results which I recived clearly shows that the MSSQL didn’t accepted the new computer name which I have set i.e. FAILOVER-DB.

Output of sp_helpserver

Output of select @@servername

2) Change Server Instance Name and Network Name

Now to fix this issue we need change the Server Instance Name and Network Name. This can be done using Following Query

sp_dropserver ‘old_name’
go
sp_addserver ‘new_name’,'local’
go

In my case I have executed following query

sp_dropserver ‘WIN-PNHS6NVSKPI’
go
sp_addserver ‘FAILOVER-DB’,local
go

3) Restart MSSQL Server

Once the above commands get executed successfully; close the MSSQL Management Studio and restart MSSQL server using following commands in command prompt.

net stop mssqlserver
net start mssqlserver

4) Verify the Changes

To verify if the name has been changed or not execute the queries mentioned in Step 1. I have recived following outputs

Output of sp_helpserver

Output of select @@servername

Thats it; now try to setup Replication of MSSQL and it won’t give that error again.