由于目前还广泛使用着SQLServer2000,很多公司又想使用新的SQLServer,从而直接【分离/附加】或者【备份/还原】数据库,在不同版本之间存放。往往就会遇到版本不兼容的问题。前几天遇到了从我本机2008R2上备份的一个数据库还原到2008上面时报错: 从运行版本
由于目前还广泛使用着SQLServer2000,很多公司又想使用新的SQLServer,从而直接【分离/附加】或者【备份/还原】数据库,在不同版本之间存放。往往就会遇到版本不兼容的问题。前几天遇到了从我本机2008R2上备份的一个数据库还原到2008上面时报错:
从运行版本10.50.2500(2008R2是10.50)和10.00.1600(2008是10.00)中可以看出这个版本不兼容问题,大部分情况下,从低版本升级到高版本,只要不是跨度太大,如2000升级到2012,都不会怎么报错。除非使用了一些新版本不兼容的特性如*=来实现left join的语句。但是就像上图那样,从高版本还原到低版本的时候,问题就出现了,而且几乎一定会报错。
下面给出几个小建议,例子是从2008 降级到2005:
方法一:使用图形化操作(GUI),打开SSMS(SQL Server Management Studio)
步骤1:右键你要降级的数据库,按下图选择:
步骤2:在对话框中选择:
步骤3:在【高级】中选择下图:
步骤4:把脚本保存起来,然后在SQLServer2005中运行脚本。
详细步骤可以看:http://bbs.csdn.net/topics/390438560?page=1#post-394316973 中的13楼的回复,有截图
步骤5:通过【任务】→【导入数据】,把数据从2008导入到使用脚本创建的库上如下图,就完成了:
方法二:使用系统自带的存储过程实现:sp_dbcmptlevel ——将某些数据库行为设置为与指定的 SQL Server 版本兼容
下面是其内部实现代码:
SET QUOTED_IDENTIFIER ON SET ANSI_NULLS ON GO create procedure sys.sp_dbcmptlevel -- 1997/04/15 @dbname sysname = NULL, -- database name to change @new_cmptlevel tinyint = NULL OUTPUT -- the new compatibility level to change to as set nocount on declare @exec_stmt nvarchar(max) declare @returncode int declare @comptlevel float(8) declare @dbid int -- dbid of the database declare @dbsid varbinary(85) -- id of the owner of the database declare @orig_cmptlevel tinyint -- original compatibility level declare @input_cmptlevel tinyint -- compatibility level passed in by user ,@cmptlvl80 tinyint -- compatibility to SQL Server Version 8.0 ,@cmptlvl90 tinyint -- compatibility to SQL Server Version 9.0 ,@cmptlvl100 tinyint -- compatibility to SQL Server Version 10.0 select @cmptlvl80 = 80, @cmptlvl90 = 90, @cmptlvl100 = 100 -- SP MUST BE CALLED AT ADHOC LEVEL -- if (@@nestlevel > 1) begin raiserror(15432,-1,-1,'sys.sp_dbcmptlevel') return (1) end -- If no @dbname given, just list the valid compatibility level values. if @dbname is null begin raiserror (15048, -1, -1, @cmptlvl80, @cmptlvl90, @cmptlvl100) return (0) end -- Verify the database name and get info select @dbid = dbid, @dbsid = sid ,@orig_cmptlevel = cmptlevel from master.dbo.sysdatabases where name = @dbname -- If @dbname not found, say so and list the databases. if @dbid is null begin raiserror(15010,-1,-1,@dbname) print ' ' select name as 'Available databases:' from master.dbo.sysdatabases return (1) end -- Now save the input compatibility level and initialize the return clevel -- to be the current clevel select @input_cmptlevel = @new_cmptlevel select @new_cmptlevel = @orig_cmptlevel -- If no clevel was supplied, display and output current level. if @input_cmptlevel is null begin raiserror(15054, -1, -1, @orig_cmptlevel) return(0) end -- If invalid clevel given, print usage and return error code -- 'usage: sp_dbcmptlevel [dbname [, compatibilitylevel]]' if @input_cmptlevel not in (@cmptlvl80, @cmptlvl90, @cmptlvl100) begin raiserror(15416, -1, -1) print ' ' raiserror (15048, -1, -1, @cmptlvl80, @cmptlvl90, @cmptlvl100) return (1) end -- Only the SA or the dbo of @dbname can execute the update part -- of this procedure sys.so check. if (not (is_srvrolemember('sysadmin') = 1)) and suser_sid() @dbsid -- ALSO ALLOW db_owner ONLY IF DB REQUESTED IS CURRENT DB and (@dbid db_id() or is_member('db_owner') 1) begin raiserror(15418,-1,-1) return (1) end -- If we're in a transaction, disallow this since it might make recovery impossible. set implicit_transactions off if @@trancount > 0 begin raiserror(15002,-1,-1,'sys.sp_dbcmptlevel') return (1) end set @exec_stmt = 'ALTER DATABASE ' + quotename(@dbname, '[') + ' SET COMPATIBILITY_LEVEL = ' + cast(@input_cmptlevel as nvarchar(128)) -- Note: database @dbname may not exist anymore exec(@exec_stmt) select @new_cmptlevel = @input_cmptlevel return (0) -- sp_dbcmptlevel GO
语法
sp_dbcmptlevel [ [ @dbname = ] name ] [ , [ @new_cmptlevel = ] version ]
参数
- [ @dbname = ] name
要为其更改兼容级别的数据库的名称。数据库名称必须符合标识符的规则。name 的数据类型为 sysname,默认值为 NULL。
- [ @new_cmptlevel = ] version
-
数据库要与之兼容的 SQL Server 的版本。version 的数据类型为 tinyint,默认值为 NULL。该值必须为下列值之一:
80 = SQL Server 2000
90 = SQL Server 2005
100 = SQL Server 2008
返回代码值
0(成功)或 1(失败)
注意事项:
后续版本的 Microsoft SQL Server 将删除该功能。请不要在新的开发工作中使用该功能,并尽快修改当前还在使用该功能的应用程序。 改为使用 ALTER DATABASE 兼容级别。
关于备份,可以看我的另外一篇文章:第一篇——第一文 SQL Server 备份基础

MySQLoffersvariousstorageengines,eachsuitedfordifferentusecases:1)InnoDBisidealforapplicationsneedingACIDcomplianceandhighconcurrency,supportingtransactionsandforeignkeys.2)MyISAMisbestforread-heavyworkloads,lackingtransactionsupport.3)Memoryengineis

Common security vulnerabilities in MySQL include SQL injection, weak passwords, improper permission configuration, and unupdated software. 1. SQL injection can be prevented by using preprocessing statements. 2. Weak passwords can be avoided by forcibly using strong password strategies. 3. Improper permission configuration can be resolved through regular review and adjustment of user permissions. 4. Unupdated software can be patched by regularly checking and updating the MySQL version.

Identifying slow queries in MySQL can be achieved by enabling slow query logs and setting thresholds. 1. Enable slow query logs and set thresholds. 2. View and analyze slow query log files, and use tools such as mysqldumpslow or pt-query-digest for in-depth analysis. 3. Optimizing slow queries can be achieved through index optimization, query rewriting and avoiding the use of SELECT*.

To monitor the health and performance of MySQL servers, you should pay attention to system health, performance metrics and query execution. 1) Monitor system health: Use top, htop or SHOWGLOBALSTATUS commands to view CPU, memory, disk I/O and network activities. 2) Track performance indicators: monitor key indicators such as query number per second, average query time and cache hit rate. 3) Ensure query execution optimization: Enable slow query logs, record and optimize queries whose execution time exceeds the set threshold.

The main difference between MySQL and MariaDB is performance, functionality and license: 1. MySQL is developed by Oracle, and MariaDB is its fork. 2. MariaDB may perform better in high load environments. 3.MariaDB provides more storage engines and functions. 4.MySQL adopts a dual license, and MariaDB is completely open source. The existing infrastructure, performance requirements, functional requirements and license costs should be taken into account when choosing.

MySQL uses a GPL license. 1) The GPL license allows the free use, modification and distribution of MySQL, but the modified distribution must comply with GPL. 2) Commercial licenses can avoid public modifications and are suitable for commercial applications that require confidentiality.

The situations when choosing InnoDB instead of MyISAM include: 1) transaction support, 2) high concurrency environment, 3) high data consistency; conversely, the situation when choosing MyISAM includes: 1) mainly read operations, 2) no transaction support is required. InnoDB is suitable for applications that require high data consistency and transaction processing, such as e-commerce platforms, while MyISAM is suitable for read-intensive and transaction-free applications such as blog systems.

In MySQL, the function of foreign keys is to establish the relationship between tables and ensure the consistency and integrity of the data. Foreign keys maintain the effectiveness of data through reference integrity checks and cascading operations. Pay attention to performance optimization and avoid common errors when using them.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

Dreamweaver Mac version
Visual web development tools
