This guide walks through migrating a SQL Server database from a source server to a destination server, covering schema scripting, database creation, and data transfer using both Generate Scripts and the Import/Export Wizard.vThis guide walks through migrating a SQL Server database from a source server to a destination server, covering schema scripting, database creation, and data transfer using both Generate Scripts and the Import/Export Wizard.v

How to Migrate an SQL Server Database: A Complete Step-by-Step Guide

2025/12/08 22:06
4 min read
For feedback or concerns regarding this content, please contact us at crypto.news@mexc.com

Database migration is a common task when moving to a new server, creating backups, or setting up development/staging environments. In this guide, we’ll walk through the complete process of migrating a database from a source server to a destination server, including both the database structure and data.

Use Case

We have:

  • Source Server: Contains database TestDB with a cities table
  • Destination Server: Empty server where we need to create a clone of TestDB
  • Goal: Migrate database schema and copy all data to the destination

Prerequisites

  • SQL Server Management Studio (SSMS) installed
  • Access credentials for both source and destination servers
  • Appropriate permissions (CREATE DATABASE, db_owner)

Part 1: Setting Up Sample Data (Source Server)

First, let’s create our sample database on the source server:

-- Connect to Source Server in SSMS -- Create TestDB database CREATE DATABASE TestDB; GO USE TestDB; GO -- Create cities table CREATE TABLE cities ( city_id INT IDENTITY(1,1) PRIMARY KEY, city_name NVARCHAR(100) NOT NULL, country NVARCHAR(100) NOT NULL, population INT, established_year INT ); GO -- Insert sample data (5 cities) INSERT INTO cities (city_name, country, population, established_year) VALUES ('New York', 'United States', 8336817, 1624), ('London', 'United Kingdom', 9002488, 43), ('Tokyo', 'Japan', 13960000, 1603), ('Dubai', 'United Arab Emirates', 3331420, 1833), ('Sydney', 'Australia', 5312163, 1788); GO -- Verify data SELECT * FROM cities;


Part 2: Generate Database Migration Script

Now let’s create a script to migrate the database structure to the destination server.

Step 1: Open Generate Scripts Wizard

  1. In SSMS, connect to your Source Server

  2. In Object Explorer (left panel), locate your database

  3. Right-click on TestDB database

  4. Select Tasks → Generate Scripts…

Step 2: Choose Objects to Script

  1. Click Next on the Introduction screen
  2. Select “Select specific database objects”
  3. Expand Tables and check:
  • dbo.cities
  1. Click Next

Step 3: Set Scripting Options

  1. Click Next to reach “Set Scripting Options”
  2. Choose “Save to file”
  3. Click Browse and save as: C:\Temp\TestDB_Schema.sql
  4. Click the Advanced button
  5. Find “Types of data to script” and select “Schema only”
  6. Click OK
  7. Click NextFinish

The wizard will generate a SQL script file containing all CREATE statements for your database objects.


Part 3: Create Database on Destination Server

Option A: Create Database Manually (Recommended for Different Servers)

Connect to your Destination Server in SSMS and run:

-- Create the database on destination server CREATE DATABASE TestDB; GO USE TestDB; GO

Option B: Include Database Creation in Script

If you want the script to create the database automatically:

  1. Follow the same Generate Scripts steps
  2. But in Step 2, select “Script entire database and all database objects”
  3. The script will include CREATE DATABASE statements

Part 4: Execute Migration Script on Destination

  1. Connect to Destination Server in SSMS
  2. Open the generated script:
  • File → Open → File
  • Select C:\Temp\TestDB_Schema.sql
  1. Select the database from the dropdown at the top:
  • Type: TestDB (if dropdown is empty)
  1. Execute the script by pressing F5

Your database structure is now created on the destination server!

Verify Structure Creation

-- Run on Destination Server USE TestDB; GO -- Check if table exists SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'cities'; -- Check table structure SELECT COLUMN_NAME, DATA_TYPE, CHARACTER_MAXIMUM_LENGTH FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME = 'cities';


Part 5: Copy Data from Source to Destination

Now that we have the database structure in place, let’s copy the data.

Method 1: Using Generate Scripts (Recommended for Small Datasets)

Step 1: Generate Data Script

  1. Connect to Source Server in SSMS

  2. Right-click TestDBTasks → Generate Scripts

  3. Select the cities table

  4. Click NextAdvanced

  5. Change “Types of data to script” to “Data only”

  6. Save to file: C:\Temp\TestDB_Data.sql

  7. Click NextFinish

Step 2: Execute Data Script on Destination

  1. Connect to Destination Server
  2. Select database: TestDB
  3. Open the data script file
  4. Execute (F5)

-- The generated script will look something like this: INSERT INTO [dbo].[cities] (city_name, country, population, established_year) VALUES ('New York', 'United States', 8336817, 1624), ('London', 'United Kingdom', 9002488, 43), ('Tokyo', 'Japan', 13960000, 1603), ('Dubai', 'United Arab Emirates', 3331420, 1833), ('Sydney', 'Australia', 5312163, 1788);

Method 2: Using Import/Export Wizard (Good for Larger Datasets)

  1. Connect to Source Server in SSMS
  2. Right-click TestDBTasks → Export Data
  3. Choose Data Source:
  • Data Source: Microsoft OLE DB Driver for SQL Server
  • Server name: Your source server
  • Database: TestDB
  • Click Next
  1. Choose Destination:
  • Destination: Microsoft OLE DB Driver for SQL Server
  • Server name: Your destination server
  • Database: TestDB
  • Click Next
  1. Select Source Tables:
  • Select “Copy data from one or more tables or views”
  • Check: [dbo].[cities]
  • Click Next
  1. Run ImmediatelyFinish

The wizard will copy all data directly from source to destination.Summary of Steps

Database Migration:

  1. Generate schema script from source database
  2. Create database on destination server
  3. Execute schema script on destination

Data Migration:

  1. Generate data script from source tables
  2. Execute data script on destination

\

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact crypto.news@mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.

You May Also Like

NYSE parent ICE completes new $600M investment in Polymarket

NYSE parent ICE completes new $600M investment in Polymarket

ICE completed a new $600 million investment in Polymarket, advancing its $2 billion funding deal as prediction markets face growing scrutiny.
Share
Coin Telegraph2026/03/27 22:07
Why UK Private Healthcare Practices Keep Losing Time to the Wrong Software

Why UK Private Healthcare Practices Keep Losing Time to the Wrong Software

Running a private healthcare practice in the UK in 2026 means managing two things at once: patient care and an increasingly complex operational infrastructure.
Share
Techbullion2026/03/27 22:40
Why It Could Outperform Pepe Coin And Tron With Over $7m Already Raised

Why It Could Outperform Pepe Coin And Tron With Over $7m Already Raised

The post Why It Could Outperform Pepe Coin And Tron With Over $7m Already Raised appeared on BitcoinEthereumNews.com. Crypto News 17 September 2025 | 20:26 While meme tokens like Pepe Coin and established networks such as Tron attract headlines, many investors are now searching for projects that combine innovation, revenue-sharing and real-world utility. BlockchainFX ($BFX), currently in presale at $0.024 ahead of an expected $0.05 launch, is quickly becoming one of the best cryptos to buy today. With $7m already secured and a unique model spanning multiple asset classes, it is positioning itself as a decentralised super app and a contender to surpass older altcoins. Early Presale Pricing Creates A Rare Entry Point BlockchainFX’s presale pricing structure has been designed to reward early participants. At $0.024, buyers secure a lower entry price than later rounds, locking in a cost basis more than 50% below the projected $0.05 launch price. As sales continue to climb beyond $7m, each new stage automatically increases the token price. This built-in mechanism creates a clear advantage for early investors and explains why the project is increasingly cited in “best presales to buy now” discussions across the crypto space. High-Yield Staking Model Shares Platform Revenue Beyond its presale appeal, BlockchainFX is creating a high-yield staking model that gives holders a direct share of platform revenue. Every time a trade occurs on its platform, 70% of trading fees flow back into the $BFX ecosystem: 50% of collected fees are automatically distributed to stakers in both BFX and USDT. 20% is allocated to daily buybacks of $BFX, adding demand and price support. Half of the bought-back tokens are permanently burned, steadily reducing supply. Rewards are based on the size of each member’s BFX holdings and capped at $25,000 USDT per day to ensure sustainability. This structure transforms token ownership from a speculative bet into an income-generating position, a rare feature among today’s altcoins. A Multi-Asset Platform…
Share
BitcoinEthereumNews2025/09/18 03:35