主页 / server / 问题

问题[sql-server-2012](server)

Martin Hope
Harrison
Asked: 2021-02-26 19:46:30 +0800 CST
  • 2

我们的一台服务器上的“SQL Server 2012 Service Pack 4 CU (KB4583465) 安全更新”更新出现了一个奇怪的问题。它将显示为安装成功，但在重新启动后它再次显示为挂起。它还会在更新历史记录中显示每次安装它的时间。

我们还尝试卸载更新并从更新目录手动安装它，但我们最终得到了相同的结果。

任何想法将不胜感激！

windows-update windows-server-2012-r2 sql-server-2012
Martin Hope
Kyaw Zin Thant
Asked: 2018-05-22 23:20:35 +0800 CST
  • -1

我的一位朋友目前正在安装 Sql server 2012，她在“共享功能”步骤中遇到了。在“共享功能”步骤，正常安装会让用户选择

  • 管理工具-基本
  • Sql Client Connectivity SDK 等取决于服务器版本，对吧？她可以看到这些功能，但问题是这些功能被禁用（她无法选择它们）。

我确实从谷歌搜索了很多，但我能找到的只是安装指南。很抱歉没有提供屏幕截图。我相信你们能帮上忙。感谢您的帮助。

sql-server-2012
Martin Hope
whybull
Asked: 2018-03-09 07:44:57 +0800 CST
  • 1

我正在尝试使用 SQL Server Management Studio for Server2012 中的以下内容将数据库还原到新位置：

RESTORE [newdb-name] FROM DISK = '..\backupfile.bak'
WITH MOVE 'olddb-name.mdf' to '...\newdb-name.mdf',
MOVE 'olddb-name_log.ldf' to '..\newdb-name_log.ldf';
GO

我在第 1 行收到错误“'newdb-name' 附近的语法错误”。管理工作室在运行之前没有将其标记为语法错误，并且由于名称有连字符，我需要将其括起来。任何帮助，将不胜感激。

sql-server-2012
Martin Hope
Henrik H
Asked: 2016-11-22 01:01:13 +0800 CST
  • 1

将修补程序KB3194725应用到我们的 SQL 服务器后，SSRS 服务器在尝试生成报告时抛出以下异常：

异常类型：InvalidReportServerDatabaseException

异常消息：报表服务器数据库的版本格式无效或无法读取。找到的版本是“164”。预期版本是“163”。

ssrs sql-server-2012 ssrs-2012
Martin Hope
user2629636
Asked: 2016-11-08 10:37:49 +0800 CST
  • 1

我是数据库管理的初学者，所以请耐心等待。我有一个 500MB 的小型 DB 和一个非常大的事务日志 (19GB)。我想把它保持在“完全恢复”模式，所以请不要建议“简单”恢复模式。

我一直在研究如何减少事务日志的大小，我正在尝试实施这些建议，但日志大小没有改变。

首先，我的工作是：我有一个每日备份任务，在维护计划中备份所有数据库。这是一种“完整”备份类型，并且似乎运行良好。我看到每天备份一个文件，类似于数据库本身的大小。

现在我有了完整备份，我继续进行手动“事务日志”类型的备份，其中包含“截断事务日志”选项。

备份在几秒钟内完成，创建一个大小为几兆字节的文件，但事务日志的大小保持不变。

我究竟做错了什么？

sql-server database-backup sql-server-2012
Martin Hope
htm11h
Asked: 2016-11-05 12:07:53 +0800 CST
  • 1

我在 Server 2012 R2 上运行 SQL SERVER Express 2008 已经有一段时间了。我最近开始研究迁移到 SQL SERVER EPXRESS 2016 的迁移过程。因为原始数据库是从 Express 2005 迁移的，所以兼容性级别是 90，我需要在 110 停止才能迁移到 130。110 提供了新的对象类型和查询IIF 条款等进展。数据迁移工具确定了这些必要的更新。

在升级 SQL 的过程中，我现在收到以下错误：

TITLE: SQL Server Setup failure.
------------------------------

SQL Server Setup has encountered the following error:

Version string portion was too short or too long..

For help, click: http://go.microsoft.com/fwlinkLinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&EvtType=0x6343E456%25400x294A9FD9

该链接无用，因为 MS 重新发布了它。

在 SQL SERVER 安装中心窗口顶部选择“新 SQL Server 独立安装或向现有安装添加功能”后出现错误。就像测试一样，我也尝试了 SQL 2016 Express。同样的错误。

我发现了一些关于更改注册表的帖子，删除以下键中引用的旧版本的 .Net：

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform

这没有用。

我尝试了许多 .Net Framework 测试工具来验证每个版本。未发现错误，但这些工具似乎尚未针对 Server 2012 R2 进行更新。

目前我的服务器已经下沉，没有工作数据库。

我已经确认 .Net Framework 3.5 和 4.5 功能实际上是通过服务器管理器安装的。

我还尝试了 REPAIR 选项以及 SQL Server 安装中心中几乎所有其他可用功能。它产生相同的错误。

任何有见地的帮助都会很高兴审查。

更新：通过控制面板删除了所有 SQL 安装，并且通过 Aaron Burtrand 描述的方法不成功的地方被用来清理注册表......他的博客同样的错误仍在继续。

windows-server-2012-r2 sql-server-2016 sql-server-2012 sql-server-2008-r2
Martin Hope
SysAdminUK
Asked: 2016-09-13 23:59:28 +0800 CST
  • 0

情况 - 我们有一个 Live_db 数据库和一个 Test_db 数据库。我正在尝试获取 Live 的副本以用作测试。

进行了 Live 备份。现有的测试数据库被删除（关闭现有的连接），因为我们不需要它的数据。我正在尝试使用名称 Test_db 恢复 Live_db 并选择更改文件路径，使其指向 test_db_data.MDF 和 test_db_log.LDF，但恢复仍然失败。

    TITLE: Microsoft SQL Server Management Studio
------------------------------

Restore of database 'TEST_DB' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)

------------------------------
ADDITIONAL INFORMATION:

System.Data.SqlClient.SqlError: Exclusive access could not be obtained because the database is in use. (Microsoft.SqlServer.SmoExtended)

当数据库甚至不存在时，它怎么能被使用呢？有很多关于此错误的信息，但都没有帮助。

我尝试根据网络上其他线程的建议修复它：

  1. 创建一个空白数据库并尝试覆盖它。- 没有不同
  2. 重新启动 SQL 服务器 - 没有区别
  3. 尝试恢复为不同的名称 - 没有区别
  4. 尝试恢复到不同的文件路径 - 没有区别
  5. 确保它不是默认数据库 - 它不是
  6. 在单用户模式下恢复 - 没有区别
  7. 确保数据库没有查询窗口 - 没有
  8. 确保没有任何表被浏览到 - DB 已删除，没有表

我完全不知所措。我要做的就是获取 LIVE_DB 的副本并将其创建为 TEST_DB。有人可以帮忙吗？如果这有所作为，我正在使用 GUI。

sql-server-2012 database-restore
Martin Hope
barbecue
Asked: 2016-08-22 10:07:31 +0800 CST
  • 0

我正在尝试在我的 SQL Server 代理作业中使用令牌，如此处所述，但某些令牌没有按我预期的那样工作。

运行代理作业时，应该扩展以提供数据库名称、服务器名称等信息的令牌没有扩展。令牌扩展的结果是一个空字符串，而不是所需的值。

下面是一个简单的例子来演示这个问题。

一个名为“备份”的简单作业有一个名为“创建备份”的 T-SQL 步骤，它使用数据库 MyDatabaseName

BACKUP 
DATABASE 
 MyDatabaseName
TO  
DISK = N'D:\Backup\"$(ESCAPE_NONE(A-DBN))".bak'

令牌 $(ESCAPE_NONE(A-DBN)) 应该扩展为当前数据库的名称，因此我希望此作业生成与数据库同名的备份文件，如下所示：

D:\Backup\MyDatabaseName.bak

实际结果是创建一个没有名称的备份，如下所示：

D:\备份.bak

如果在名称周围使用方括号，则结果是一个错误，基本上是说名称不能为空。所以令牌的值被视为一个空字符串。

如果我在此步骤中将令牌更改为 (DATE)，那么它会按预期工作，并且会创建一个名称为当前日期的备份。

D:\备份\20160821.bak

选中替换所有作业对警报的响应的令牌框。

我花了几个小时寻找这种特定行为的解释，但找不到任何相关的东西。

操作系统是服务器 2008R2。SQL Server 版本为 11.0.3128.0

agent token sql-server-2012
Martin Hope
SysAdminUK
Asked: 2016-06-07 04:22:08 +0800 CST
  • 0

我正在尝试将数据库从我们的实时系统复制到测试系统。（相同的服务器，不同的数据库）

测试数据库已在准备过程中被删除，因此我们有一个干净的状态。我试过备份数据库，然后恢复它，但它没有说它没有对数据库的独占访问权限。（我不明白这一点，因为备份文件只是一个 .bak 文件，wby 它没有访问权限吗？如果它意味着目标数据库。它已被删除，所以甚至不应该在那里干预吗？）

我用谷歌搜索了这个问题，没有打开查询窗口。我是唯一连接到sql server的，默认db设置为master。这些都是我可以检查但没有帮助的简单事情。

有人建议使用复制数据库...而不是...

所以我通过向导，选择要复制的数据库，选择测试名称（相同的服务器），然后它运行并失败。

这是日志：

#Fields: event,computer,operator,source,sourceid,executionid,starttime,endtime,datacode,databytes,message
OnPreValidate,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0F384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,
OnPreValidate,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,
OnPostValidate,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,
OnPostValidate,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,
PackageStart,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,Beginning of package execution.

Diagnostic,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,Maximum concurrent executables are set to 1.

DiagnosticEx,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,<?xml version="1.0"?><DTS:ParameterValues xmlns:DTS="www.microsoft.com/SqlServer/Dts"/>
OnPreExecute,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,
OnPreExecute,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,
OnPreValidate,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,
OnPostValidate,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,
OnProgress,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,Task just started the execution.
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,Connecting to server SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:52,06/06/2016 12:31:52,0,0x,Connecting to server SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Connected to server SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Connected to server SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Connecting to server SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Connecting to server SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Connected to server SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Connected to server SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Transferring server objects to server SQLSERVER from SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Transferring server objects to server SQLSERVER from SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Transferring server objects to server SQLSERVER from SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Transferring server objects to server SQLSERVER from SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Transferred server objects to SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Transferred server objects to SQLSERVER
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Transferring database LIVE_DB from SQLSERVER server as TEST_DB to SQLSERVER server
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Added data file LIVE_DB in path E:\Microsoft SQL Server\MSSQL11.SQLSERVER\MSSQL\DATA\TEST_DB.mdf to file group [PRIMARY]
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Added data file LIVE_DB in path E:\Microsoft SQL Server\MSSQL11.SQLSERVER\MSSQL\DATA\TEST_DB.mdf to file group [PRIMARY]
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Added log file LIVE_DB_Log in path E:\Microsoft SQL Server\MSSQL11.SQLSERVER\MSSQL\DATA\TEST_DB_log.ldf
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Added log file LIVE_DB_Log in path E:\Microsoft SQL Server\MSSQL11.SQLSERVER\MSSQL\DATA\TEST_DB_log.ldf
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Transferring data to database TEST_DB from LIVE_DB
OnInformation,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:31:53,06/06/2016 12:31:53,0,0x,Transferring data to database TEST_DB from LIVE_DB
OnError,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:32:35,06/06/2016 12:32:35,0,0x,An error occurred while transferring data. See the inner exception for details.
StackTrace:    at Microsoft.SqlServer.Management.Smo.Transfer.TransferData()
   at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.TransferDatabasesUsingSMOTransfer()
InnerException-->Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
StackTrace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.SqlServer.Management.Smo.Transfer.ExecuteStatements(SqlConnection destinationConnection, IEnumerable`1 statements, SqlTransaction transaction)
   at Microsoft.SqlServer.Management.Smo.Transfer.TransferData()
OnError,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:32:35,06/06/2016 12:32:35,0,0x,An error occurred while transferring data. See the inner exception for details.
StackTrace:    at Microsoft.SqlServer.Management.Smo.Transfer.TransferData()
   at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.TransferDatabasesUsingSMOTransfer()
InnerException-->Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
StackTrace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.SqlServer.Management.Smo.Transfer.ExecuteStatements(SqlConnection destinationConnection, IEnumerable`1 statements, SqlTransaction transaction)
   at Microsoft.SqlServer.Management.Smo.Transfer.TransferData()
OnProgress,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:32:35,06/06/2016 12:32:35,0,0x,Database transfer failed for 1 database(s).
OnProgress,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:32:35,06/06/2016 12:32:35,100,0x,Transfer objects finished execution.
OnTaskFailed,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:32:35,06/06/2016 12:32:35,0,0x,
OnPostExecute,SQLSERVER,NT Service\SQLSERVERAGENT,SQLSERVER_SQLSERVER_Transfer Objects Task,{6B0681DE-D895-4E61-82B0-57682BB61E50},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:32:35,06/06/2016 12:32:35,0,0x,
OnWarning,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:32:35,06/06/2016 12:32:35,-2147381246,0x,SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

OnPostExecute,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:32:35,06/06/2016 12:32:35,0,0x,
DiagnosticEx,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:32:35,06/06/2016 12:32:35,0,0x,<?xml version="1.0"?><DTS:ProcessMemoryUsage xmlns:DTS="www.microsoft.com/SqlServer/Dts"><DTS:PeakWorkingSetSize>105385984</DTS:PeakWorkingSetSize></DTS:ProcessMemoryUsage>
   PackageEnd,SQLSERVER,NT Service\SQLSERVERAGENT,CDW_SQLSERVER_SQLSERVER_1,{A77E694E-5A0D-4244-A8E7-07B0DF384B94},{47E1B488-1421-49AE-A0D0-9F95D44B8EFB},06/06/2016 12:32:35,06/06/2016 12:32:35,1,0x,End of package execution.

我是一名 SQL 新手，如果有什么我需要做的，请您一步一步地提供。

名称已更改以保护无辜者：

服务器名称：SQLSERVER。原始数据库名称：LIVE_DB。目标数据库名称：TEST_DB。这一切都在 SA 帐户下运行。

如果您需要更多信息，请告诉我

sql-server-2012
Martin Hope
David
Asked: 2016-04-23 13:56:06 +0800 CST
  • 0

我已经尝试在 Ubuntu 中运行“Microsoft ODBC Driver 13 for SQL Server”两天了，但我没有想法/已经筋疲力尽了谷歌。

我的测试机器是一个 vagrant 虚拟机，这些是 bash 脚本的相关部分，它充当配置器：

sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get install -y python-software-properties vim curl libgss3 libstdc++6 git-core libpcre3-dev make
sudo apt-get upgrade -y
sudo apt-get dist-upgrade -y

和

cd /home/vagrant

wget https://download.microsoft.com/download/2/E/5/2E58F097-805C-4AB8-9FC6-71288AB4409D/msodbcsql-13.0.0.0.tar.gz
tar xvzf msodbcsql-13.0.0.0.tar.gz

sudo chmod +x msodbcsql-13.0.0.0/build_dm.sh
sudo chmod +x msodbcsql-13.0.0.0/install.sh

./msodbcsql-13.0.0.0/build_dm.sh --accept-warning

directory=$(ls /tmp | grep 'unixODBC')
path="/tmp/$directory/unixODBC-2.3.1"
cd $(echo $path)
sudo make install

cd /home/vagrant/msodbcsql-13.0.0.0/
sudo ./install.sh install --accept-license

sudo ln -s /usr/lib64/libodbcinst.so.2 /lib/x86_64-linux-gnu/libodbcinst.so.2

cat << EOF | sudo tee -a /home/vagrant/.odbc.ini
[MSSQL]
Description=Microsoft ODBC Driver 13 for SQL Server
Driver=/opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.0.so.0.0
Server=<my_server>\<my_sqlserver_instance_name>,1433
Database=PDS
Threading=1
UsageCount=1
EOF

sudo chown vagrant:vagrant /home/vagrant/.odbc.ini

这是安装日志的相关位：

[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on libmsodbcsql-13.0.so.0.0
[Fri Apr 22 20:16:59 UTC 2016] Copying install.sh to /opt/microsoft/msodbcsql/13.0.0.0
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on install.sh
[Fri Apr 22 20:16:59 UTC 2016] Copying build_dm.sh to /opt/microsoft/msodbcsql/13.0.0.0
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on build_dm.sh
[Fri Apr 22 20:16:59 UTC 2016] Copying README to /opt/microsoft/msodbcsql/13.0.0.0
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on README
[Fri Apr 22 20:16:59 UTC 2016] Copying LICENSE to /opt/microsoft/msodbcsql/13.0.0.0
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on LICENSE
[Fri Apr 22 20:16:59 UTC 2016] Copying WARNING to /opt/microsoft/msodbcsql/13.0.0.0
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on WARNING
[Fri Apr 22 20:16:59 UTC 2016] Copying INSTALL to /opt/microsoft/msodbcsql/13.0.0.0
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on INSTALL
[Fri Apr 22 20:16:59 UTC 2016] Copying bin/bcp.rll to /opt/microsoft/msodbcsql/13.0.0.0/en_US
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on bcp.rll
[Fri Apr 22 20:16:59 UTC 2016] Copying bin/SQLCMD.rll to /opt/microsoft/msodbcsql/13.0.0.0/en_US
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on SQLCMD.rll
[Fri Apr 22 20:16:59 UTC 2016] Copying bin/BatchParserGrammar.dfa to /opt/microsoft/msodbcsql/13.0.0.0/en_US
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on BatchParserGrammar.dfa
[Fri Apr 22 20:16:59 UTC 2016] Copying bin/BatchParserGrammar.llr to /opt/microsoft/msodbcsql/13.0.0.0/en_US
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on BatchParserGrammar.llr
[Fri Apr 22 20:16:59 UTC 2016] Copying lib64/msodbcsqlr13.rll to /opt/microsoft/msodbcsql/13.0.0.0/en_US
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on msodbcsqlr13.rll
[Fri Apr 22 20:16:59 UTC 2016] Copying docs/en_US.tar.gz to /opt/microsoft/msodbcsql/13.0.0.0/docs/en_US
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on en_US.tar.gz
[Fri Apr 22 20:16:59 UTC 2016] Copying include/msodbcsql.h to /opt/microsoft/msodbcsql/13.0.0.0/include
[Fri Apr 22 20:16:59 UTC 2016] Setting permissions on msodbcsql.h
[Fri Apr 22 20:16:59 UTC 2016] Extracting documentation from /opt/microsoft/msodbcsql/13.0.0.0/docs/en_US/en_US.tar.gz
...
[Fri Apr 22 20:16:59 UTC 2016] Creating symbolic links
[Fri Apr 22 20:16:59 UTC 2016] Linking bcp to bcp-13.0.0.0
[Fri Apr 22 20:16:59 UTC 2016] Linking sqlcmd to sqlcmd-13.0.0.0
[Fri Apr 22 20:16:59 UTC 2016] Registering the Microsoft ODBC Driver 13 for SQL Server driver
odbcinst: Driver installed. Usage count increased to 1.
    Target directory is /etc

ldd 显示满足所有依赖项：

vagrant@vagrant-ubuntu-trusty-64:~$ ldd /opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.0.so.0.0
    linux-vdso.so.1 =>  (0x00007ffd109e8000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fde5d698000)
    libodbcinst.so.2 => /lib/x86_64-linux-gnu/libodbcinst.so.2 (0x00007fde5d486000)
    libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fde5d280000)
    libgss.so.3 => /usr/lib/libgss.so.3 (0x00007fde5d074000)
    libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007fde5cda9000)
    libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007fde5c9cc000)
    libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007fde5c76d000)
    libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fde5c460000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fde5c159000)
    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fde5bf42000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fde5bd24000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fde5b95e000)
    /lib64/ld-linux-x86-64.so.2 (0x00007fde5dc8e000)
    libltdl.so.7 => /usr/lib/x86_64-linux-gnu/libltdl.so.7 (0x00007fde5b754000)
    libshishi.so.0 => /usr/lib/libshishi.so.0 (0x00007fde5b4fa000)
    libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007fde5b2ca000)
    libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007fde5b0c6000)
    libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007fde5aebb000)
    libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007fde5acb6000)
    libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fde5aa9b000)
    libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007fde5a886000)
    libgnutls.so.26 => /usr/lib/x86_64-linux-gnu/libgnutls.so.26 (0x00007fde5a5c8000)
    libgcrypt.so.11 => /lib/x86_64-linux-gnu/libgcrypt.so.11 (0x00007fde5a348000)
    libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fde5a142000)
    libidn.so.11 => /usr/lib/x86_64-linux-gnu/libidn.so.11 (0x00007fde59f0f000)
    libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fde59cf5000)
    libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007fde59ab3000)
    libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007fde598ab000)

当我尝试测试驱动程序时，这是响应：

vagrant@vagrant-ubuntu-trusty-64:~$ isql -v MSSQL sa <password>
[28000][unixODBC][Microsoft][ODBC Driver 13 for SQL Server][SQL Server]Login failed for user 'sa'.
[ISQL]ERROR: Could not SQLConnect

在 SQL Server 错误日志中，我有这个：

2016-04-22 13:35:04.52 Logon       Error: 18456, Severity: 14, State: 8.
2016-04-22 13:35:04.52 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <my_ip>]

我可以使用 sa 用户登录到命名服务器，并使用 Microsoft SQL Server Management Studio 登录“SQL Server 身份验证”，所以我不认为这是一个“Windows 身份验证”问题，这似乎是此错误严重性的标准答案-状态组合。

我不知道从这里去哪里。任何帮助是极大的赞赏！！！

linux ubuntu odbc sql-server-2012 unixodbc