自动生成SQL Server表的INSERT语句,最佳方法是什么?

755
我们正在编写一个新的应用程序,在测试时需要一大堆虚拟数据。我使用 MS Access 将 Excel 文件转储到相关表中,以添加这些数据。
偶尔,我们想要“刷新”相关表,这意味着删除它们所有内容、重新创建它们,并运行已保存的 MS Access 追加查询。
第一部分(删除并重新创建)是一个简单的 SQL 脚本,但最后一部分让我感到不安。我想要一个单一的设置脚本,其中包含大量的 INSERT 语句来重新生成虚拟数据。
现在我已经将数据存储在表中,有什么最好的方法可以从该数据集自动生成大量的 INSERT 语句?
我能想到的唯一方法是将表保存到 Excel 工作表中,然后编写 Excel 公式,为每一行创建一个 INSERT 语句,但这肯定不是最好的方法。
我使用 2008 管理工具连接到 SQL Server 2005 数据库。

6
哇,我刚刚检查了我的安装情况,你说得对,“脚本表格为”→“插入”只会给你一个插入模板,而不是一张包含实际数据插入的页面!我希望你的问题能够得到解答,因为我也想找一个简单的方法来做你所要求的事情。 - JoeCool
2
@JosephStyons 我稍微更新了一下问题,试图大幅简化和澄清它,并使其保持相关性。这已经成为StackOverflow上的一个重要问题,希望能减轻那些来这里寻求解决方案的人的工作量。 =)看看你是否认为已删除的信息中有任何重要的内容。如果您对编辑有任何异议,请随时回滚。 - Evan Carroll
1
@EvanCarroll 谢谢你,Evan。我已经回滚了;我尊重地建议一些背景信息不仅有助于理解上下文,还有助于帮助提问者想出真实世界的搜索词。我保留了你的一个更改;我删掉了关于Toad for Oracle的段落。那可能没有太大帮助。 - JosephStyons
3
我使用SSMSBoost。https://www.ssmsboost.com - Darren Griffith
24个回答

1288

微软应该宣传SSMS 2008的这种功能。您需要查找的功能内置于生成脚本实用程序中,但默认情况下该功能被关闭,必须在脚本表时启用。

以下是使用SQL Management Studio 2008生成表中所有数据的INSERT语句的快速过程,无需使用脚本或插件:

  1. 右键单击数据库并转到任务 > 生成脚本
  2. 选择要生成脚本的表(或对象)。
  3. 转到设置脚本选项选项卡,然后单击高级按钮。
  4. 常规类别中,转到要脚本化的数据类型
  5. 有3个选项:仅架构仅数据架构和数据。选择适当的选项,然后单击确定SqlDataOptions

然后,您将获得来自SSMS的CREATE TABLE语句以及所有INSERT语句中的数据。


12
请务必阅读下面的Noonand评论--复选框不在SCRIPT DATA = TRUE下,而是在常规部分下,选择适当的'Types of data to script'选项。 - Richard West
12
如果你只想生成一个插入语句,可以像这样操作:从现有表中选择*,并将其插入到新表中,其中包括您的where子句,然后在新表上执行上述操作。 - tony
29
高级按钮的位置真的很蠢。难怪没有人能够自己找到它。它似乎与“保存到文件”选项相关联。此外,我想知道为什么它不会生成更有效的插入语句而是多个插入语句。 - Joe Phillips
8
这在更新的版本中也同样适用。我在 SSMS 2014 中进行了确认。 - Alan Fluka
3
如果您选择“仅数据”并遇到“找到循环依赖关系”错误,请切换到“架构和数据”以避免错误。这在Management Studio v17中发生。 - Endy Tjahjono
显示剩余6条评论

110

我们使用这个存储过程 - 它允许你针对特定的表,并使用where子句。你可以在这里找到文本。

例如,它可以让你做到这一点:

EXEC sp_generate_inserts 'titles'

从链接复制的源代码:

SET NOCOUNT ON
GO

PRINT 'Using Master database'
USE master
GO

PRINT 'Checking for the existence of this procedure'
IF (SELECT OBJECT_ID('sp_generate_inserts','P')) IS NOT NULL --means, the procedure already exists
    BEGIN
        PRINT 'Procedure already exists. So, dropping it'
        DROP PROC sp_generate_inserts
    END
GO

--Turn system object marking on
EXEC master.dbo.sp_MS_upd_sysobj_category 1
GO

CREATE PROC sp_generate_inserts
(
    @table_name varchar(776),       -- The table/view for which the INSERT statements will be generated using the existing data
    @target_table varchar(776) = NULL,  -- Use this parameter to specify a different table name into which the data will be inserted
    @include_column_list bit = 1,       -- Use this parameter to include/ommit column list in the generated INSERT statement
    @from varchar(800) = NULL,      -- Use this parameter to filter the rows based on a filter condition (using WHERE)
    @include_timestamp bit = 0,         -- Specify 1 for this parameter, if you want to include the TIMESTAMP/ROWVERSION column's data in the INSERT statement
    @debug_mode bit = 0,            -- If @debug_mode is set to 1, the SQL statements constructed by this procedure will be printed for later examination
    @owner varchar(64) = NULL,      -- Use this parameter if you are not the owner of the table
    @ommit_images bit = 0,          -- Use this parameter to generate INSERT statements by omitting the 'image' columns
    @ommit_identity bit = 0,        -- Use this parameter to ommit the identity columns
    @top int = NULL,            -- Use this parameter to generate INSERT statements only for the TOP n rows
    @cols_to_include varchar(8000) = NULL,  -- List of columns to be included in the INSERT statement
    @cols_to_exclude varchar(8000) = NULL,  -- List of columns to be excluded from the INSERT statement
    @disable_constraints bit = 0,       -- When 1, disables foreign key constraints and enables them after the INSERT statements
    @ommit_computed_cols bit = 0        -- When 1, computed columns will not be included in the INSERT statement

)
AS
BEGIN

/***********************************************************************************************************
Procedure:  sp_generate_inserts  (Build 22) 
        (Copyright © 2002 Narayana Vyas Kondreddi. All rights reserved.)

Purpose:    To generate INSERT statements from existing data. 
        These INSERTS can be executed to regenerate the data at some other location.
        This procedure is also useful to create a database setup, where in you can 
        script your data along with your table definitions.

Written by: Narayana Vyas Kondreddi
            http://vyaskn.tripod.com
            http://vyaskn.tripod.com/code/generate_inserts.txt

Acknowledgements:
        Divya Kalra -- For beta testing
        Mark Charsley   -- For reporting a problem with scripting uniqueidentifier columns with NULL values
        Artur Zeygman   -- For helping me simplify a bit of code for handling non-dbo owned tables
        Joris Laperre   -- For reporting a regression bug in handling text/ntext columns

Tested on:  SQL Server 7.0 and SQL Server 2000

Date created:   January 17th 2001 21:52 GMT

Date modified:  May 1st 2002 19:50 GMT

Email:      vyaskn@hotmail.com

NOTE:       This procedure may not work with tables with too many columns.
        Results can be unpredictable with huge text columns or SQL Server 2000's sql_variant data types
        Whenever possible, Use @include_column_list parameter to ommit column list in the INSERT statement, for better results
        IMPORTANT: This procedure is not tested with internation data (Extended characters or Unicode). If needed
        you might want to convert the datatypes of character variables in this procedure to their respective unicode counterparts
        like nchar and nvarchar


Example 1:  To generate INSERT statements for table 'titles':

        EXEC sp_generate_inserts 'titles'

Example 2:  To ommit the column list in the INSERT statement: (Column list is included by default)
        IMPORTANT: If you have too many columns, you are advised to ommit column list, as shown below,
        to avoid erroneous results

        EXEC sp_generate_inserts 'titles', @include_column_list = 0

Example 3:  To generate INSERT statements for 'titlesCopy' table from 'titles' table:

        EXEC sp_generate_inserts 'titles', 'titlesCopy'

Example 4:  To generate INSERT statements for 'titles' table for only those titles 
        which contain the word 'Computer' in them:
        NOTE: Do not complicate the FROM or WHERE clause here. It's assumed that you are good with T-SQL if you are using this parameter

        EXEC sp_generate_inserts 'titles', @from = "from titles where title like '%Computer%'"

Example 5:  To specify that you want to include TIMESTAMP column's data as well in the INSERT statement:
        (By default TIMESTAMP column's data is not scripted)

        EXEC sp_generate_inserts 'titles', @include_timestamp = 1

Example 6:  To print the debug information:

        EXEC sp_generate_inserts 'titles', @debug_mode = 1

Example 7:  If you are not the owner of the table, use @owner parameter to specify the owner name
        To use this option, you must have SELECT permissions on that table

        EXEC sp_generate_inserts Nickstable, @owner = 'Nick'

Example 8:  To generate INSERT statements for the rest of the columns excluding images
        When using this otion, DO NOT set @include_column_list parameter to 0.

        EXEC sp_generate_inserts imgtable, @ommit_images = 1

Example 9:  To generate INSERT statements excluding (ommiting) IDENTITY columns:
        (By default IDENTITY columns are included in the INSERT statement)

        EXEC sp_generate_inserts mytable, @ommit_identity = 1

Example 10:     To generate INSERT statements for the TOP 10 rows in the table:

        EXEC sp_generate_inserts mytable, @top = 10

Example 11:     To generate INSERT statements with only those columns you want:

        EXEC sp_generate_inserts titles, @cols_to_include = "'title','title_id','au_id'"

Example 12:     To generate INSERT statements by omitting certain columns:

        EXEC sp_generate_inserts titles, @cols_to_exclude = "'title','title_id','au_id'"

Example 13: To avoid checking the foreign key constraints while loading data with INSERT statements:

        EXEC sp_generate_inserts titles, @disable_constraints = 1

Example 14:     To exclude computed columns from the INSERT statement:
        EXEC sp_generate_inserts MyTable, @ommit_computed_cols = 1
***********************************************************************************************************/

SET NOCOUNT ON

--Making sure user only uses either @cols_to_include or @cols_to_exclude
IF ((@cols_to_include IS NOT NULL) AND (@cols_to_exclude IS NOT NULL))
    BEGIN
        RAISERROR('Use either @cols_to_include or @cols_to_exclude. Do not use both the parameters at once',16,1)
        RETURN -1 --Failure. Reason: Both @cols_to_include and @cols_to_exclude parameters are specified
    END

--Making sure the @cols_to_include and @cols_to_exclude parameters are receiving values in proper format
IF ((@cols_to_include IS NOT NULL) AND (PATINDEX('''%''',@cols_to_include) = 0))
    BEGIN
        RAISERROR('Invalid use of @cols_to_include property',16,1)
        PRINT 'Specify column names surrounded by single quotes and separated by commas'
        PRINT 'Eg: EXEC sp_generate_inserts titles, @cols_to_include = "''title_id'',''title''"'
        RETURN -1 --Failure. Reason: Invalid use of @cols_to_include property
    END

IF ((@cols_to_exclude IS NOT NULL) AND (PATINDEX('''%''',@cols_to_exclude) = 0))
    BEGIN
        RAISERROR('Invalid use of @cols_to_exclude property',16,1)
        PRINT 'Specify column names surrounded by single quotes and separated by commas'
        PRINT 'Eg: EXEC sp_generate_inserts titles, @cols_to_exclude = "''title_id'',''title''"'
        RETURN -1 --Failure. Reason: Invalid use of @cols_to_exclude property
    END


--Checking to see if the database name is specified along wih the table name
--Your database context should be local to the table for which you want to generate INSERT statements
--specifying the database name is not allowed
IF (PARSENAME(@table_name,3)) IS NOT NULL
    BEGIN
        RAISERROR('Do not specify the database name. Be in the required database and just specify the table name.',16,1)
        RETURN -1 --Failure. Reason: Database name is specified along with the table name, which is not allowed
    END

--Checking for the existence of 'user table' or 'view'
--This procedure is not written to work on system tables
--To script the data in system tables, just create a view on the system tables and script the view instead

IF @owner IS NULL
    BEGIN
        IF ((OBJECT_ID(@table_name,'U') IS NULL) AND (OBJECT_ID(@table_name,'V') IS NULL)) 
            BEGIN
                RAISERROR('User table or view not found.',16,1)
                PRINT 'You may see this error, if you are not the owner of this table or view. In that case use @owner parameter to specify the owner name.'
                PRINT 'Make sure you have SELECT permission on that table or view.'
                RETURN -1 --Failure. Reason: There is no user table or view with this name
            END
    END
ELSE
    BEGIN
        IF NOT EXISTS (SELECT 1 FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = @table_name AND (TABLE_TYPE = 'BASE TABLE' OR TABLE_TYPE = 'VIEW') AND TABLE_SCHEMA = @owner)
            BEGIN
                RAISERROR('User table or view not found.',16,1)
                PRINT 'You may see this error, if you are not the owner of this table. In that case use @owner parameter to specify the owner name.'
                PRINT 'Make sure you have SELECT permission on that table or view.'
                RETURN -1 --Failure. Reason: There is no user table or view with this name      
            END
    END

--Variable declarations
DECLARE     @Column_ID int,         
        @Column_List varchar(8000), 
        @Column_Name varchar(128), 
        @Start_Insert varchar(786), 
        @Data_Type varchar(128), 
        @Actual_Values varchar(8000),   --This is the string that will be finally executed to generate INSERT statements
        @IDN varchar(128)       --Will contain the IDENTITY column's name in the table

--Variable Initialization
SET @IDN = ''
SET @Column_ID = 0
SET @Column_Name = ''
SET @Column_List = ''
SET @Actual_Values = ''

IF @owner IS NULL 
    BEGIN
        SET @Start_Insert = 'INSERT INTO ' + '[' + RTRIM(COALESCE(@target_table,@table_name)) + ']' 
    END
ELSE
    BEGIN
        SET @Start_Insert = 'INSERT ' + '[' + LTRIM(RTRIM(@owner)) + '].' + '[' + RTRIM(COALESCE(@target_table,@table_name)) + ']'      
    END


--To get the first column's ID

SELECT  @Column_ID = MIN(ORDINAL_POSITION)  
FROM    INFORMATION_SCHEMA.COLUMNS (NOLOCK) 
WHERE   TABLE_NAME = @table_name AND
(@owner IS NULL OR TABLE_SCHEMA = @owner)



--Loop through all the columns of the table, to get the column names and their data types
WHILE @Column_ID IS NOT NULL
    BEGIN
        SELECT  @Column_Name = QUOTENAME(COLUMN_NAME), 
        @Data_Type = DATA_TYPE 
        FROM    INFORMATION_SCHEMA.COLUMNS (NOLOCK) 
        WHERE   ORDINAL_POSITION = @Column_ID AND 
        TABLE_NAME = @table_name AND
        (@owner IS NULL OR TABLE_SCHEMA = @owner)



        IF @cols_to_include IS NOT NULL --Selecting only user specified columns
        BEGIN
            IF CHARINDEX( '''' + SUBSTRING(@Column_Name,2,LEN(@Column_Name)-2) + '''',@cols_to_include) = 0 
            BEGIN
                GOTO SKIP_LOOP
            END
        END

        IF @cols_to_exclude IS NOT NULL --Selecting only user specified columns
        BEGIN
            IF CHARINDEX( '''' + SUBSTRING(@Column_Name,2,LEN(@Column_Name)-2) + '''',@cols_to_exclude) <> 0 
            BEGIN
                GOTO SKIP_LOOP
            END
        END

        --Making sure to output SET IDENTITY_INSERT ON/OFF in case the table has an IDENTITY column
        IF (SELECT COLUMNPROPERTY( OBJECT_ID(QUOTENAME(COALESCE(@owner,USER_NAME())) + '.' + @table_name),SUBSTRING(@Column_Name,2,LEN(@Column_Name) - 2),'IsIdentity')) = 1 
        BEGIN
            IF @ommit_identity = 0 --Determing whether to include or exclude the IDENTITY column
                SET @IDN = @Column_Name
            ELSE
                GOTO SKIP_LOOP          
        END

        --Making sure whether to output computed columns or not
        IF @ommit_computed_cols = 1
        BEGIN
            IF (SELECT COLUMNPROPERTY( OBJECT_ID(QUOTENAME(COALESCE(@owner,USER_NAME())) + '.' + @table_name),SUBSTRING(@Column_Name,2,LEN(@Column_Name) - 2),'IsComputed')) = 1 
            BEGIN
                GOTO SKIP_LOOP                  
            END
        END

        --Tables with columns of IMAGE data type are not supported for obvious reasons
        IF(@Data_Type in ('image'))
            BEGIN
                IF (@ommit_images = 0)
                    BEGIN
                        RAISERROR('Tables with image columns are not supported.',16,1)
                        PRINT 'Use @ommit_images = 1 parameter to generate INSERTs for the rest of the columns.'
                        PRINT 'DO NOT ommit Column List in the INSERT statements. If you ommit column list using @include_column_list=0, the generated INSERTs will fail.'
                        RETURN -1 --Failure. Reason: There is a column with image data type
                    END
                ELSE
                    BEGIN
                    GOTO SKIP_LOOP
                    END
            END

        --Determining the data type of the column and depending on the data type, the VALUES part of
        --the INSERT statement is generated. Care is taken to handle columns with NULL values. Also
        --making sure, not to lose any data from flot, real, money, smallmomey, datetime columns
        SET @Actual_Values = @Actual_Values  +
        CASE 
            WHEN @Data_Type IN ('char','varchar','nchar','nvarchar') 
                THEN 
                    'COALESCE('''''''' + REPLACE(RTRIM(' + @Column_Name + '),'''''''','''''''''''')+'''''''',''NULL'')'
            WHEN @Data_Type IN ('datetime','smalldatetime') 
                THEN 
                    'COALESCE('''''''' + RTRIM(CONVERT(char,' + @Column_Name + ',109))+'''''''',''NULL'')'
            WHEN @Data_Type IN ('uniqueidentifier') 
                THEN  
                    'COALESCE('''''''' + REPLACE(CONVERT(char(255),RTRIM(' + @Column_Name + ')),'''''''','''''''''''')+'''''''',''NULL'')'
            WHEN @Data_Type IN ('text','ntext') 
                THEN  
                    'COALESCE('''''''' + REPLACE(CONVERT(char(8000),' + @Column_Name + '),'''''''','''''''''''')+'''''''',''NULL'')'                    
            WHEN @Data_Type IN ('binary','varbinary') 
                THEN  
                    'COALESCE(RTRIM(CONVERT(char,' + 'CONVERT(int,' + @Column_Name + '))),''NULL'')'  
            WHEN @Data_Type IN ('timestamp','rowversion') 
                THEN  
                    CASE 
                        WHEN @include_timestamp = 0 
                            THEN 
                                '''DEFAULT''' 
                            ELSE 
                                'COALESCE(RTRIM(CONVERT(char,' + 'CONVERT(int,' + @Column_Name + '))),''NULL'')'  
                    END
            WHEN @Data_Type IN ('float','real','money','smallmoney')
                THEN
                    'COALESCE(LTRIM(RTRIM(' + 'CONVERT(char, ' +  @Column_Name  + ',2)' + ')),''NULL'')' 
            ELSE 
                'COALESCE(LTRIM(RTRIM(' + 'CONVERT(char, ' +  @Column_Name  + ')' + ')),''NULL'')' 
        END   + '+' +  ''',''' + ' + '

        --Generating the column list for the INSERT statement
        SET @Column_List = @Column_List +  @Column_Name + ','   

        SKIP_LOOP: --The label used in GOTO

        SELECT  @Column_ID = MIN(ORDINAL_POSITION) 
        FROM    INFORMATION_SCHEMA.COLUMNS (NOLOCK) 
        WHERE   TABLE_NAME = @table_name AND 
        ORDINAL_POSITION > @Column_ID AND
        (@owner IS NULL OR TABLE_SCHEMA = @owner)


    --Loop ends here!
    END

--To get rid of the extra characters that got concatenated during the last run through the loop
SET @Column_List = LEFT(@Column_List,len(@Column_List) - 1)
SET @Actual_Values = LEFT(@Actual_Values,len(@Actual_Values) - 6)

IF LTRIM(@Column_List) = '' 
    BEGIN
        RAISERROR('No columns to select. There should at least be one column to generate the output',16,1)
        RETURN -1 --Failure. Reason: Looks like all the columns are ommitted using the @cols_to_exclude parameter
    END

--Forming the final string that will be executed, to output the INSERT statements
IF (@include_column_list <> 0)
    BEGIN
        SET @Actual_Values = 
            'SELECT ' +  
            CASE WHEN @top IS NULL OR @top < 0 THEN '' ELSE ' TOP ' + LTRIM(STR(@top)) + ' ' END + 
            '''' + RTRIM(@Start_Insert) + 
            ' ''+' + '''(' + RTRIM(@Column_List) +  '''+' + ''')''' + 
            ' +''VALUES(''+ ' +  @Actual_Values  + '+'')''' + ' ' + 
            COALESCE(@from,' FROM ' + CASE WHEN @owner IS NULL THEN '' ELSE '[' + LTRIM(RTRIM(@owner)) + '].' END + '[' + rtrim(@table_name) + ']' + '(NOLOCK)')
    END
ELSE IF (@include_column_list = 0)
    BEGIN
        SET @Actual_Values = 
            'SELECT ' + 
            CASE WHEN @top IS NULL OR @top < 0 THEN '' ELSE ' TOP ' + LTRIM(STR(@top)) + ' ' END + 
            '''' + RTRIM(@Start_Insert) + 
            ' '' +''VALUES(''+ ' +  @Actual_Values + '+'')''' + ' ' + 
            COALESCE(@from,' FROM ' + CASE WHEN @owner IS NULL THEN '' ELSE '[' + LTRIM(RTRIM(@owner)) + '].' END + '[' + rtrim(@table_name) + ']' + '(NOLOCK)')
    END 

--Determining whether to ouput any debug information
IF @debug_mode =1
    BEGIN
        PRINT '/*****START OF DEBUG INFORMATION*****'
        PRINT 'Beginning of the INSERT statement:'
        PRINT @Start_Insert
        PRINT ''
        PRINT 'The column list:'
        PRINT @Column_List
        PRINT ''
        PRINT 'The SELECT statement executed to generate the INSERTs'
        PRINT @Actual_Values
        PRINT ''
        PRINT '*****END OF DEBUG INFORMATION*****/'
        PRINT ''
    END

PRINT '--INSERTs generated by ''sp_generate_inserts'' stored procedure written by Vyas'
PRINT '--Build number: 22'
PRINT '--Problems/Suggestions? Contact Vyas @ vyaskn@hotmail.com'
PRINT '--http://vyaskn.tripod.com'
PRINT ''
PRINT 'SET NOCOUNT ON'
PRINT ''


--Determining whether to print IDENTITY_INSERT or not
IF (@IDN <> '')
    BEGIN
        PRINT 'SET IDENTITY_INSERT ' + QUOTENAME(COALESCE(@owner,USER_NAME())) + '.' + QUOTENAME(@table_name) + ' ON'
        PRINT 'GO'
        PRINT ''
    END


IF @disable_constraints = 1 AND (OBJECT_ID(QUOTENAME(COALESCE(@owner,USER_NAME())) + '.' + @table_name, 'U') IS NOT NULL)
    BEGIN
        IF @owner IS NULL
            BEGIN
                SELECT  'ALTER TABLE ' + QUOTENAME(COALESCE(@target_table, @table_name)) + ' NOCHECK CONSTRAINT ALL' AS '--Code to disable constraints temporarily'
            END
        ELSE
            BEGIN
                SELECT  'ALTER TABLE ' + QUOTENAME(@owner) + '.' + QUOTENAME(COALESCE(@target_table, @table_name)) + ' NOCHECK CONSTRAINT ALL' AS '--Code to disable constraints temporarily'
            END

        PRINT 'GO'
    END

PRINT ''
PRINT 'PRINT ''Inserting values into ' + '[' + RTRIM(COALESCE(@target_table,@table_name)) + ']' + ''''


--All the hard work pays off here!!! You'll get your INSERT statements, when the next line executes!
EXEC (@Actual_Values)

PRINT 'PRINT ''Done'''
PRINT ''


IF @disable_constraints = 1 AND (OBJECT_ID(QUOTENAME(COALESCE(@owner,USER_NAME())) + '.' + @table_name, 'U') IS NOT NULL)
    BEGIN
        IF @owner IS NULL
            BEGIN
                SELECT  'ALTER TABLE ' + QUOTENAME(COALESCE(@target_table, @table_name)) + ' CHECK CONSTRAINT ALL'  AS '--Code to enable the previously disabled constraints'
            END
        ELSE
            BEGIN
                SELECT  'ALTER TABLE ' + QUOTENAME(@owner) + '.' + QUOTENAME(COALESCE(@target_table, @table_name)) + ' CHECK CONSTRAINT ALL' AS '--Code to enable the previously disabled constraints'
            END

        PRINT 'GO'
    END

PRINT ''
IF (@IDN <> '')
    BEGIN
        PRINT 'SET IDENTITY_INSERT ' + QUOTENAME(COALESCE(@owner,USER_NAME())) + '.' + QUOTENAME(@table_name) + ' OFF'
        PRINT 'GO'
    END

PRINT 'SET NOCOUNT OFF'


SET NOCOUNT OFF
RETURN 0 --Success. We are done!
END

GO

PRINT 'Created the procedure'
GO


--Turn system object marking off
EXEC master.dbo.sp_MS_upd_sysobj_category 2
GO

PRINT 'Granting EXECUTE permission on sp_generate_inserts to all users'
GRANT EXEC ON sp_generate_inserts TO public

SET NOCOUNT OFF
GO

PRINT 'Done'

3
@jcollum - 这实际上不是一个内置的存储过程。如果您按照链接操作,您可以获取该存储过程的文本。 - Shane Fulmer
7
我遇到了以下问题: 消息536,级别16,状态5,过程sp_generate_inserts,行331 在SUBSTRING函数中传递了无效的长度参数。 消息536,级别16,状态5,过程sp_generate_inserts,行332 在SUBSTRING函数中传递了无效的长度参数。 消息50000,级别16,状态1,过程sp_generate_inserts,行336 没有要选择的列。 至少应该有一列来生成输出。 为什么会出现这些问题? - Nimrod Shory
18
我也遇到了这个错误。为了解决它,用“EXEC sp_MS_marksystemobject sp_generate_inserts”替换“EXEC master.dbo.sp_MS_upd_sysobj_category 2”,并删除“EXEC master.dbo.sp_MS_upd_sysobj_category 1”这一行。 - Dan Nolan
7
@InfinitiesLoop,有时候你需要通过代码自动化来完成任务,而不是让用户手动通过图形界面执行。请问需要翻译什么内容? - CaffGeek
2
想要指出的是,应该避免使用 sp_ 作为用户定义存储过程的前缀,因为这是 Microsoft 用于内置存储过程的命名空间。如果他们发布了一个同名的存储过程,你的代码将会出现问题。此外,如果你使用不同的命名约定,你可以通过元表轻松区分用户和系统存储过程。 - 10762409
显示剩余12条评论

77

这也可以使用Visual Studio来完成(至少在2013版本之后)。

在VS 2013中,还可以筛选插入语句所基于的行列表,这是我所知道的SSMS无法实现的功能。

按照以下步骤执行:

  • 打开“SQL Server对象资源管理器”窗口(菜单:/视图/SQL Server对象资源管理器)
  • 展开数据库及其表
  • 右键单击该表,从上下文菜单中选择“查看数据”
  • 这将在主区域中显示数据
  • 可选步骤:单击筛选器图标“排序和筛选数据集”(结果上方第四个图标),并对一个或多个列应用某些筛选器
  • 单击“脚本”或“脚本到文件”图标(顶部行右侧的图标,它们看起来像小纸片)

这将为所选表创建(条件)插入语句到活动窗口或文件中。


“筛选”和“脚本”按钮Visual Studio 2013

enter image description here


4
这现在是我从一个数据库中提取记录并插入到另一个地方的首选方法 - 这似乎比通过SSMS向导更简单。 - Michael12345
2
我无法将二进制字段导出 :( - Mafu Josh
你的帖子是正确的,使用Visual Studio中的SQL Server数据工具是最简单的方法。这里有一篇类似的帖子,解释了如何为前1000行生成插入语句,希望对你有所帮助。 - Shaiju T
仍然可以在使用VS 2019(16.8预览版3)的SSDT中找到。但是仍然无法在查询结果中找到,只能在表或视图上使用“查看数据”。您可以进行筛选,但无法重新排序列,必须创建视图才能实现。奇怪的是,这对视图也适用。 - yzorg
非常感谢您。我已经寻找类似的东西有一段时间了。 - parysoid
我确认这个功能在Visual Studio 2022 (17.3.2)中可用。 - nbstrat

59

@Mike Ritacco所述,但已更新至SSMS 2008 R2

  1. 右键单击数据库名称。
  2. 选择“任务”>“生成脚本”。
  3. 根据您的设置,介绍页面可能会显示或不显示。
  4. 选择“选择特定数据库对象”,
  5. 展开树视图并选中相关的表。
  6. 点击下一步。
  7. 点击高级选项。
  8. 在常规部分下,选择“要编写脚本的数据类型”的适当选项。
  9. 完成向导。

随后,您将获得直接从SSMS获取的所有数据的插入语句。

编辑2016-10-25 SQL Server 2016/SSMS 13.0.15900.1

  1. 右键单击数据库名称

  2. 选择“任务”>“生成脚本”

  3. 根据您的设置,介绍页面可能会显示或不显示

  4. 选择“选择特定数据库对象”

  5. 展开树视图并选中相关的表

  6. 点击下一步

  7. 点击高级选项

  8. 在常规部分下,选择“要编写脚本的数据类型”的适当选项

  9. 点击确定

  10. 选择输出目标,可以是新查询、剪贴板或文件

  11. 点击两次下一步

  12. 您的脚本将按照上面选择的设置准备好

  13. 点击完成


嗯,我不知道我们是否在使用不同版本的SSMS 2008 R2,但是我这里根本没有“高级”选项。我所做的是在“选择脚本选项”步骤中选择“脚本数据”。(顺便说一句,这个选项在Express版中不存在) - Andy

28

1
唯一能够处理带有制表符和换行符的非常大的nvarchar(max)内容的工具。 - Matej
1
FYI,这是一款商业产品,目前单个开发者的价格为30欧元。有60天的试用许可证。 - DharmaTurtle

26

我正在使用版本号为10.0.5500.0的SSMS 2008。在这个版本中,生成脚本向导的高级选项已被替换为下面的屏幕。在这种情况下,我只需要插入数据而不是创建语句,因此我不得不更改两个圆圈中的属性Script Options


15

如果需要编程访问,则可以使用开源存储过程 `GenerateInsert`。

INSERT语句生成器

举个简单快捷的例子,要为表 AdventureWorks.Person.AddressType 生成INSERT语句,请执行以下语句:

USE [AdventureWorks];
GO
EXECUTE dbo.GenerateInsert @ObjectName = N'Person.AddressType';

这将生成以下脚本:

SET NOCOUNT ON
SET IDENTITY_INSERT Person.AddressType ON
INSERT INTO Person.AddressType
([AddressTypeID],[Name],[rowguid],[ModifiedDate])
VALUES
 (1,N'Billing','B84F78B1-4EFE-4A0E-8CB7-70E9F112F886',CONVERT(datetime,'2002-06-01 00:00:00.000',121))
,(2,N'Home','41BC2FF6-F0FC-475F-8EB9-CEC0805AA0F2',CONVERT(datetime,'2002-06-01 00:00:00.000',121))
,(3,N'Main Office','8EEEC28C-07A2-4FB9-AD0A-42D4A0BBC575',CONVERT(datetime,'2002-06-01 00:00:00.000',121))
,(4,N'Primary','24CB3088-4345-47C4-86C5-17B535133D1E',CONVERT(datetime,'2002-06-01 00:00:00.000',121))
,(5,N'Shipping','B29DA3F8-19A3-47DA-9DAA-15C84F4A83A5',CONVERT(datetime,'2002-06-01 00:00:00.000',121))
,(6,N'Archive','A67F238A-5BA2-444B-966C-0467ED9C427F',CONVERT(datetime,'2002-06-01 00:00:00.000',121))
SET IDENTITY_INSERT Person.AddressType OFF

1
干得好!简单且实现了它的预定功能。希望能长期使用这个 :) - anar khalilov
在发现代码中的一个错误后,我在 GitHub 上提交了一个拉取请求。感谢分享。 - anar khalilov
2
这个比起“EXEC sp_generate_inserts 'titles'”更有效。 - user11156893
@drumsta,如果需要的话,你能否添加一个包含列和排除列列表参数?现在我只需要从我的表中选择几列。谢谢。 - user11156893

15

第一个链接是关于 sp_generate_inserts 的,非常棒,这里有一个非常简单的版本:

DECLARE @Fields VARCHAR(max); SET @Fields = '[QueueName], [iSort]' -- your fields, keep []
DECLARE @Table  VARCHAR(max); SET @Table  = 'Queues'               -- your table

DECLARE @SQL    VARCHAR(max)
SET @SQL = 'DECLARE @S VARCHAR(MAX)
SELECT @S = ISNULL(@S + '' UNION '', ''INSERT INTO ' + @Table + '(' + @Fields + ')'') + CHAR(13) + CHAR(10) + 
 ''SELECT '' + ' + REPLACE(REPLACE(REPLACE(@Fields, ',', ' + '', '' + '), '[', ''''''''' + CAST('),']',' AS VARCHAR(max)) + ''''''''') +' FROM ' + @Table + '
PRINT @S'

EXEC (@SQL)

在我的系统上,我得到了这个结果:

INSERT INTO Queues([QueueName], [iSort])
SELECT 'WD: Auto Capture', '10' UNION 
SELECT 'Car/Lar', '11' UNION 
SELECT 'Scan Line', '21' UNION 
SELECT 'OCR', '22' UNION 
SELECT 'Dynamic Template', '23' UNION 
SELECT 'Fix MICR', '41' UNION 
SELECT 'Fix MICR (Supervisor)', '42' UNION 
SELECT 'Foreign MICR', '43' UNION 
...

9
我的贡献是一个PowerShell插入脚本生成器,可让您在不使用笨重的SSMS GUI的情况下脚本化多个表。非常适合将“种子”数据快速持久化到源代码控制中。
  1. 将以下脚本保存为“filename.ps1”。
  2. 在“CUSTOMIZE ME”下面进行自己的修改。
  3. 您可以按任何顺序添加要脚本化的表列表。
  4. 您可以在PowerShell ISE中打开脚本并点击播放按钮,或者只需在PowerShell命令提示符中执行脚本即可。
默认情况下,生成的插入脚本将位于与脚本相同的文件夹下的“SeedData.sql”。
您需要安装SQL Server Management Objects程序集,如果已安装SSMS,则应该已经存在。
Add-Type -AssemblyName ("Microsoft.SqlServer.Smo, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91")
Add-Type -AssemblyName ("Microsoft.SqlServer.ConnectionInfo, Version=12.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91")



#CUSTOMIZE ME
$outputFile = ".\SeedData.sql"
$connectionString = "Data Source=.;Initial Catalog=mydb;Integrated Security=True;"



$sqlConnection = new-object System.Data.SqlClient.SqlConnection($connectionString)
$conn = new-object Microsoft.SqlServer.Management.Common.ServerConnection($sqlConnection)
$srv = new-object Microsoft.SqlServer.Management.Smo.Server($conn)
$db = $srv.Databases[$srv.ConnectionContext.DatabaseName]
$scr = New-Object Microsoft.SqlServer.Management.Smo.Scripter $srv
$scr.Options.FileName = $outputFile
$scr.Options.AppendToFile = $false
$scr.Options.ScriptSchema = $false
$scr.Options.ScriptData = $true
$scr.Options.NoCommandTerminator = $true

$tables = New-Object Microsoft.SqlServer.Management.Smo.UrnCollection



#CUSTOMIZE ME
$tables.Add($db.Tables["Category"].Urn)
$tables.Add($db.Tables["Product"].Urn)
$tables.Add($db.Tables["Vendor"].Urn)



[void]$scr.EnumScript($tables)

$sqlConnection.Close()

6

GenerateData 是一个很棒的工具,特别是在编程方面。你可以轻松地对其进行调整,因为源代码是公开的。一些不错的功能:

  • 人名和地名生成器
  • 能够保存生成配置文件(在下载并在本地设置之后)
  • 通过脚本自定义和操作生成过程
  • 多种不同的输出格式(CSV、Javascript、JSON等)可用于数据(如果需要在不同环境中测试数据集并跳过数据库访问)
  • 免费。但如果您觉得软件有用,请考虑捐赠 :)

GUI


我从未遇到过任何问题,而且我已经多次使用它。也许你没有使用该应用程序所制作的相同版本。在最坏的情况下,您可以使用其“使用自定义HTML格式”创建自定义输出。我认为这是一个非常好的工具。 - Klik
1
它没有正确映射类型,样本数据和插入语句也创建了错误的引号,我不得不费劲地清理脚本。但最终我认为dbschema更好。 - Transformer
有趣,我没有发现那个,不知道你是怎么使用它的。无论如何,各有所好。 - Klik
是的,它适用于非常基本的东西,我去年已经告诉了网站所有者,但我所指的输出是创建Sql Server脚本的DB选项。这很不幸,因为该脚本确实可以解决很多问题...但在插入1000个表记录时可能会很烦人...尽管如此,对于快速处理一些事情仍然是一个不错的工具。 - Transformer
1
https://github.com/benkeen/generatedata - yzorg
此工具不会读取现有生成的数据来生成INSERT/UPDATE/MERGE。它只能生成新数据,与其他答案不同。我认为这个答案并没有明确说明这个工具生成哪种类型的数据(从数据文件还是新数据)。 - yzorg

网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接