Md Haidar Ali Khan's questions

让我们从一个名为 DB1 的 MySQL 数据库开始。因为我想在DB2中恢复DB1数据库的mysqldump备份。DB2 数据库是同一 Host Server 机器中的另一个数据库。

因为我已经通过（MySQL Workbench 以及 SQLyog Ultimate Tool）将 DB1 mysqldump 备份文件恢复到 DB2 数据库。恢复通过成功恢复。但是 DB2 数据库中没有任何表、视图、存储过程、函数、触发器和事件表或数据。我也经历了用不同的名字恢复 mysql 数据库，但在某个地方运气不好。

我的环境如下：

Operating system version  :   Microsoft Windows Server 2012 R2 Stanadard
Handware information      :   VMware, Inc. VMware Virtual Platform
Processors                :   Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60 GHz
Intalled memory (RAM)     :   24 GB
Installed MySQL Server version : Server version 5.7.24 community edition
The DEFAULT CHARACTER SET of database : utf8
The Backup of DB1 database is 26 GB.

注意：因为我想要 DB2 数据库中 DB1 数据库的所有内容。

我的问题是如何在同一台主机上获取 DB1 数据库中的所有tables（、、、、、和）数据。ViewsStored ProcsFunctionsTriggersevent tables

正如我想说的，我们将在一个生产服务器中SQL Server Standard 2012 SP1 edition降级SQL Server Express 2012 SP4。

目前我想在该服务器中保留 SQL Server Standard 2012 SP1，并且我想安装 SQL Server Express 2012 SP4。除非 SQL Server Express 2012 SP4 不会投入生产。直到我想保留 SQL Server 2012 Standard SP1。

我的问题是我可以同时在同一台服务器上安装 SQL Server Express 2012 SP4 和 SQL Server Standard 2012 SP1。

注意：假设 Running SQL Server 2012 Standard SP1 实例名称为ABC. 我可以安装ABCSQL Server 2012 Express SP4 的相同实例名称 ( ) 还是会有所不同。

在 MongoDB shell 中，如何查看我正在使用的当前数据库的特定集合中的所有文档？

当我尝试通过查询时

> db.getCollection().find()

要得到如下所述的错误

2017-10-14T00:57:34.363+0530 E QUERY    [thread1] Error: collection constructor called with undefined argument :
DB.prototype.getCollection@src/mongo/shell/db.js:34:16
@(shell):1:1

我还在这里上传了 mongo shell 命令提示符的屏幕截图

我想说我是 mongodb 的新手，今天我试图恢复转储文件。我在我的 mongod 中得到Assertion failure _state.get()during mongorestoredump，当时进程卡住了。mongodb环境如下：

Mongodb version is - 3.2.16-11-g1abb660
O.S - Windows 7 Enterprise 32-bit
mongodb is running in Domain account.

当我从我的网站发送以下restore转储日志时mongod

2017-10-11T12:40:22.994+0300 I -        [conn11] Assertion failure _state.get() < 0 C:\data\mci\89fbcdee7b6a486969190f06feaabe28\src\src\mongo/util/concurrency/rwlock.h 204
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\util\log.cpp(136)                                                  mongo::logContext+0xba
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\util\assert_util.cpp(137)                                          mongo::verifyFailed+0x17e
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\mmap_windows.cpp(164)                           mongo::MemoryMappedFile::close+0x5a
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\mmap_windows.cpp(340)                           mongo::MemoryMappedFile::map+0x800
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\durable_mapped_file.cpp(261)                    mongo::DurableMappedFile::create+0x137
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\data_file.cpp(175)                              mongo::DataFile::open+0x167
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\mmap_v1_extent_manager.cpp(241)                 mongo::MmapV1ExtentManager::_addAFile+0x175
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\mmap_v1_extent_manager.cpp(393)                 mongo::MmapV1ExtentManager::_createExtent+0x8d
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\mmap_v1_extent_manager.cpp(497)                 mongo::MmapV1ExtentManager::allocateExtent+0x93
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\record_store_v1_base.cpp(528)                   mongo::RecordStoreV1Base::increaseStorageSize+0x2f
    2017-10-11T12:40:23.693+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\record_store_v1_simple.cpp(169)                 mongo::SimpleRecordStoreV1::allocRecord+0x28a
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\record_store_v1_base.cpp(353)                   mongo::RecordStoreV1Base::_insertRecord+0x8d
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\mmap_v1\record_store_v1_base.cpp(342)                   mongo::RecordStoreV1Base::insertRecord+0x145
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\storage\record_store.h(379)                                     mongo::RecordStore::insertRecords+0x6a
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\catalog\collection.cpp(443)                                     mongo::Collection::_insertDocuments+0x20b
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\catalog\collection.cpp(361)                                     mongo::Collection::insertDocuments+0x248
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\catalog\collection.cpp(378)                                     mongo::Collection::insertDocument+0x73
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\commands\write_commands\batch_executor.cpp(1048)                mongo::insertOne+0x155
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\commands\write_commands\batch_executor.cpp(784)                 mongo::WriteBatchExecutor::insertMany+0x15b
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\commands\write_commands\batch_executor.cpp(846)                 mongo::WriteBatchExecutor::execInserts+0x247
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\commands\write_commands\batch_executor.cpp(686)                 mongo::WriteBatchExecutor::bulkExecute+0x6f
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\commands\write_commands\batch_executor.cpp(332)                 mongo::WriteBatchExecutor::executeBatch+0x2d4
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\commands\write_commands\write_commands.cpp(146)                 mongo::WriteCmd::run+0x157
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\dbcommands.cpp(1468)                                            mongo::Command::run+0x791
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\dbcommands.cpp(1340)                                            mongo::Command::execCommand+0x75f
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\commands.cpp(505)                                               mongo::runCommands+0x282
    2017-10-11T12:40:23.694+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\instance.cpp(263)                                               mongo::receivedCommand+0x287
    2017-10-11T12:40:23.695+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\instance.cpp(520)                                               mongo::assembleResponse+0x51d
    2017-10-11T12:40:23.695+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\db\db.cpp(180)                                                     mongo::`anonymous namespace'::MyMessageHandler::process+0x93
    2017-10-11T12:40:23.695+0300 I CONTROL  [conn11] mongod.exe    ...\src\mongo\util\net\message_server_port.cpp(229)                              mongo::PortMessageServer::handleIncomingMsg+0x3f8
    2017-10-11T12:40:23.698+0300 I CONTROL  [conn11] mongod.exe    c:\program files (x86)\microsoft visual studio 12.0\vc\include\thr\xthread(187)  std::_LaunchPad<std::_Bind<1,void *,void * (__cdecl*const)(void *),nspr::Thr
    ead *> >::_Go+0x10
    2017-10-11T12:40:23.699+0300 I CONTROL  [conn11] mongod.exe    f:\dd\vctools\crt\crtw32\stdcpp\thr\threadcall.cpp(28)                           _Call_func+0x17
    2017-10-11T12:40:23.699+0300 I CONTROL  [conn11] mongod.exe    f:\dd\vctools\crt\crtw32\startup\threadex.c(376)                                 _callthreadstartex+0x1b
    2017-10-11T12:40:23.699+0300 I CONTROL  [conn11] mongod.exe    f:\dd\vctools\crt\crtw32\startup\threadex.c(354)                                 _threadstartex+0x7c
    2017-10-11T12:40:23.703+0300 I CONTROL  [conn11] kernel32.dll                                                                                   BaseThreadInitThunk+0x12
    2017-10-11T12:40:23.703+0300 I CONTROL  [conn11] ntdll.dll                                                                                      RtlInitializeExceptionChain+0xef
    2017-10-11T12:40:23.704+0300 I CONTROL  [conn11]
    2017-10-11T12:40:23.705+0300 I CONTROL  [conn13] MapViewOfFileEx for C:\data\db\citibike.2 at address 00000000 failed with errno:8 Not enough storage is available to process this command. (file size is 268435456) in Memo
    ryMappedFile::map
    2017-10-11T12:40:23.708+0300 I -        [conn13] Assertion failure _state.get() < 0 C:\data\mci\89fbcdee7b6a486969190f06feaabe28\src\src\mongo/util/concurrency/rwlock.h 204

我还附上了mongorestore转储错误和mongod屏幕截图

mongorestore 转储错误

mongod 错误

任何帮助或建议将不胜感激。

在import将excel数据导入 SQL Server 2012 Express 期间，User只有我收到错误。错误如下所述

Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'User'.

而我的导入语句TSQL代码如下：

Use DB1;
    Go
    select * INTO User
    from openrowset('MICROSOFT.ACE.OLEDB.12.0',
    'Excel 12.0; Database=C:\DBTableDataRecords\User.xlsx; HDR=yes; IMEX=1',
    'select * from [User$]');
    Go

注意：从上面的 TSQL 代码中，我能够导入 excel 数据以创建其他表名（用户表名除外）。即使我已经检查了MICROSOFT.ACE.OLEDB.12.0提供商链接服务器对象。'Allow inprocess'启用提供者选项的位置。

当我在 TSQL 下面提到的网络共享驱动器中进行备份时。

Use DatabaseName
Go
Backup Database DatabaseName
To Disk=N'H:\DatabaseBackup\DatabaseName.bak';
Go

我在 SSMS 中收到以下错误。

 Msg 3201, Level 16, State 1, Line 1

无法打开备份设备'H:\DatabaseBackup\DatabaseName.bak'。操作系统错误 3（系统找不到指定的路径。）。

Msg 3013, Level 16, State 1, Line 1

BACKUP DATABASE 异常终止。

正如我通过这个 TSQL 检查到 'xp_cmdshell' 一样。run_value & config_value 如下：

name       minimum  maximum config_value    run_value
xp_cmdshell 0           1     1               1

注意：这里H是我的网络共享。

任何建议将不胜感激。

是否可以使用SQL Server 管理对象 (SMO)编程更改密码过期的登录密码？

在工作时间，我多次从生产服务器收到此消息。我在 SQL Server 中拥有“sa”级权限。

工作环境

1. 微软 SQL Server 2012 速成版
2. 视窗服务器 2012 R2
3. VMware, Inc. VMware 虚拟平台

我注意到，在将 SQL Server 2012 Enterprise 迁移到 SQL Server 2012 Express 之后，每天都会在手动备份数据库后显示“虚假”虚拟备份。

当我执行此 T-SQL 以显示备份详细信息时

select * from msdb.dbo.backupset;

select * from msdb.dbo.backupmediafamily;

它显示备份详细信息以及手动备份详细信息和虚拟设备备份详细信息。我还附上了 backupset 和 backupmediafamily 的截图：

*编辑后*

我已经从 windows PowerShell 签出，SQLWriter 服务正在窗口服务中运行。我的 Windows Server 2012 R2 已经安装在域环境中。因此，虚拟备份是从 SQLWriter 服务运行的。

为什么它显示大部分自动备份在虚拟设备中使用NT AUTHORITY\SYSTEM用户名 & 默认情况下它显示虚拟设备及其一些虚拟位置的备份。但是我的 SQL Server 数据库没有附加任何 SAN 设备。

数据库位于 SQL Server 2012 Express 上。所以，SQL Server Agent Automatic Backup 没有任何选项。它如何在日志文件中显示自动备份。根据 MSDN https://msdn.microsoft.com/en-us/library/ms178018(v=sql.110).aspx & https://technet，它会自动采用表示虚拟设备位置的“Device_Type=7” .microsoft.com/en-us/library/ms190284(v=sql.110).aspx 如果“Device_Type=7”即虚拟设备。

但在这里我想说的是，在迁移数据库之前，数据库是在 SQL Server 2012 Enterprise 上并且设置了 SQL Server Agent 自动备份。但这次使用的是 SQL Server 2012 Express。

它甚至会自动备份“系统数据库”和“用户数据库”。

我的问题是，如果没有设置任何虚拟设备，那么为什么我的 SQL Server Express 数据库要进行虚拟备份。甚至这个数据库也是我的审计数据库。如果此备份将继续进行下去。

对我的审计数据有影响吗？

任何建议将不胜感激？

我想在单用户模式下启动我的 SQL Server Express 实例来进行一些故障排除，例如恢复主数据库。

我无法在 SQL Server 配置管理器中找到“启动参数”选项。

我找到了一些博客，例如http://mssqlfun.com/2014/09/04/how-to-start-sql-server-in-single-user-mode/，但是我无法将-m参数添加到'启动参数'。

请参阅下面的我的 SQL Server 配置管理器的屏幕截图：

我的工作环境是：

1. MS SQL Server 2012 速成版 11.1.3000.0
2. 视窗服务器 2012 R2
3. SQL server 2012 Express 安装在域中
4. 操作系统在 VMware 下运行

有没有可能通过控制台连接的方法？任何想法或建议将不胜感激。

我可以从这个 T-SQL 中看到启动参数：'select * from sys.dm_server_registry;'，但是我无法在 SQL Server 配置管理器中看到设置。

是否可以通过 DAC 连接 MS SQL Server 2012 Express。从 SQL Server 2012 Enterprise 迁移到 MS SQL Server 2012 Express 后，出现了一些性能问题。当我使用此 TSQL 签出时

select * from sys.dm_os_schedulers;

该计划未显示 DAC（专用管理员连接）计划程序 ID。

任何想法或建议将不胜感激。

我想说我已经浏览了一些 sql 博客和 MSDN BOL，但仍然有一些困惑。

1. SQL Server 2012 Express 的限制是 10 GB。这是基于实例还是基于每个数据库的限制？

2. SQL Server 2012 Express 的连接数：连接数有限制或无限制。

   如果我要使用服务器版本的操作系统，那么最大并发用户连接数是多少。

3. 限制来自数据库级别或操作系统级别。

4. 如果我将 Windows Server 2012 R2 与 SQL Server 2012 Express SP1 一起使用，那么最大并发连接数是多少？

5. 我们可以在单个 SQL Server 实例的引擎盖下保留多少个数据库。

任何帮助或建议将不胜感激

作为测试阶段，我安装了 SQL Server 2014 企业版的评估版。

当我通过 SQL Server Management Studio 分离数据库时，我看到两个选项：

1. 断开连接
2. 更新统计

这两个选项都会将数据库与 SQL Server 实例分离。这两个选项有什么区别？

我想说的是，根据公司政策，我们将 SQL Server 2012 Enterprise 降级为 SQL Server 2012 Express。

任何建议将不胜感激。

我想说的是，因为我想在 sql server 2012 中以单个帐户名配置多个数据库邮件。

这是 SQL-Cluster-DB ，因此根据头部的指示，如果任何 sql 作业将失败，则通知应该是我自己（即 DBA）以及系统管理员。

对于单个帐户名称，单个电子邮件 ID 可以正常工作。当我要像这样将带有一个邮件 ID 的“外发邮件服务器 (SMTP)”更改为两个邮件 ID 时：

Outgoing mail server (SMTP)
Email address : first mail id; second mail id
display name : MS SQL Server 2012 Backup notification
reply e-mail : first mail id; second mail id
Server name : (My company mail server)                    Port NO:(my company smtp mail port no)

在电子邮件地址中配置多个邮件 ID 后，我收到此错误

由于邮件服务器故障，无法将邮件发送给收件人。（使用帐户 1 (2015-12-02T10:36:37) 发送邮件。异常消息：无法将邮件发送到邮件服务器。（指定的 字符串不是电子邮件地址所需的格式。）。）

当我从电子邮件地址中删除一个电子邮件 ID 以及回复 SMTP 需要配置的电子邮件时，测试邮件工作正常。

我的问题是这样的： 1）是否可以在一个帐户中配置多个电子邮件 ID 警报通知）再次需要“第二个帐户名称”来进行第二个电子邮件警报通知。

我的 SQL server 2012 工作环境是这样的：

1) windows server 2012 R2
1) Microsoft SQL Server Standard (64-bit)
3)SQL Server is in Cluster Environment (that's why multiple sql alerts notification required)
4)System is in Domain environment.
5)It's Online Server

任何建议或帮助将不胜感激。

我想说，今天我遇到的任何与 Microosft SQL Server 2012 相关的事件。我在办公时间的开始工作时间登录了 Microsoft SQL Server 2012，但是在我公司工作时间的中间，我得到了（ Microsoft SQL Server，错误：18487) 类似错误消息

===================================

Cannot show requested dialog.

===================================

Cannot show requested dialog. (SqlMgmt)

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.AllocateDialog(XmlDocument initializationXml, 

IServiceProvider dialogServiceProvider, CDataContainer dc)
   at 

Microsoft.SqlServer.Management.SqlMgmt.DefaultLaunchFormHostedControlAllocator.Microsoft.SqlServer.Management.SqlMgmt.ILaunchFormHostedControlAll

ocator.CreateDialog(XmlDocument initializationXml, IServiceProvider dialogServiceProvider)
   at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm.InitializeForm(XmlDocument doc, IServiceProvider provider, ISqlControlCollection control)
   at Microsoft.SqlServer.Management.SqlMgmt.LaunchForm..ctor(XmlDocument doc, IServiceProvider provider)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ToolMenuItemHelper.OnCreateAndShowForm(IServiceProvider sp, XmlDocument doc)
   at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()

===================================

Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
   at Microsoft.SqlServer.Management.SqlManagerUI.CreateLogin.CheckObjects(String login)
   at Microsoft.SqlServer.Management.SqlManagerUI.CreateLogin..ctor(CDataContainer context)

===================================

Failed to connect to server ServerName. (Microsoft.SqlServer.ConnectionInfo)

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
   at Microsoft.SqlServer.Management.Common.ConnectionManager.PoolConnect()
   at Microsoft.SqlServer.Management.Common.ConnectionManager.get_DatabaseEngineType()
   at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.UpdateConnectionInfoIfCloud(Object& connectionInfo, Urn urn, Boolean& isUpdated)
   at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)

===================================

Login failed for user 'SQLLoginID'.  Reason: The password of the account has expired. (.Net SqlClient Data Provider)

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

------------------------------
Server Name: ServerName
Error Number: 18487
Severity: 14
State: 1
Line Number: 65536


------------------------------
Program Location:

   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean 

asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet 

bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet 

bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, 

Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, 

Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential 

credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, 

SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, 

SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object 

poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, 

DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, 

DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory 

connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, 

TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)
   at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()

我已经在 stackExchange 站点中浏览了与此主题相关的所有内容。主要是 Aaron Bertrand 所有与此主题相关的博客文章，例如Does sys.sql_logins.is_policy_checked 是否意味着该策略已被检查？和验证现有用户的密码策略以及https://dba.stackexchange.com/search?q=password+policy。

但我想问这个问题，这就是为什么要问 sql 专家。

与 SQL Server 专家 Aaron Bertrand 和其他我的高级 StackExchange SQL 专家相比，我是 SQL Server 的新手。根据工作环境政策，系统管理员没有共享“本地安全设置策略”。所以，我没有确切的“密码最长使用期限”到期信息。我已经多次遇到上述与更改密码有关的错误。

从 T-SQL 查询

select * from sys.sql_logins;

在此查询之后，我知道所有 sql syslogin 详细信息，例如is_policy_checked、is_expiration_checked、create_date和modify_date。

从 modify_date 我知道 sql 登录修改日期的确切日期。此外，从上面的查询可以清楚地看出哪个用户应用了“强制密码策略”和“强制密码过期”以及他们的 SQL 登录。

在我的环境中，我有一个 Microsoft SQL Server 2012 的“sa”用户。但我无权检查本地安全设置->帐户策略->最大密码年龄。

任何与此错误相关的提示或线索将不胜感激。

从过去两天开始，我可以在 SQL Server 错误日志中看到以下内容。

AppDomain 2 (mssqlsystemresource.dbo[runtime].1) unloaded.
&
AppDomain 2 (mssqlsystemresource.dbo[runtime].1) is marked for unload due to memory pressure.

我有这样的系统环境：

OS- microosft windows server 2012 R2 Standard
processors - Intel(R) Xeon(R) CPU E5-2670 0 @2.60 GHz
Installed Memory (RAM) - 8GB
Hardware Information - VMWare, Inc. VMware Virtual Platform
SQL Server - Microsoft SQL Server Enterprise (64-bit)

我已经在本地服务器中签出了昨天的事件日志。我发现了这些事件

Server Name ID  Severity    Source            Log      Date and Time
ABC    1008 Error   Microsoft-Windows-Perflib Application 10/01/2015 2:21
ABC     2   Error   TeamCentral      Application      9/30/2015 4:20:41 PM
ABC    1309 Warning ASP.NET 4.0.30319.0 Application 9/30/2015 4:20:41 PM
ABC   10016 Error Microsoft-Windows-DistributedCOM System 9/30/2015 4:06:23 PM
ABC   10016 Error   Microsoft-Windows-DistributedCOM    System  9/30/2015 4:00:04 PM
ABC 10016   Error   Microsoft-Windows-DistributedCOM    System  9/30/2015 4:00:02 PM
ABC 2   Error   TeamCentral Application 9/30/2015 3:55:13 PM
ABC 1309    Warning ASP.NET 4.0.30319.0 Application 9/30/2015 3:55:13 PM
ABC 10016   Error   Microsoft-Windows-DistributedCOM    System  9/30/2015 3:40:06 PM
ABC 10016   Error   Microsoft-Windows-DistributedCOM    System  9/30/2015 3:40:03 PM
ABC 1309    Warning ASP.NET 4.0.30319.0 Application 9/30/2015 3:23:54 PM
ABC 2   Error   TeamCentral Application 9/30/2015 3:23:54 PM
ABC 2   Error   TeamCentral Application 9/30/2015 3:22:48 PM
ABC 1309    Warning ASP.NET 4.0.30319.0 Application 9/30/2015 3:22:48 PM
ABC 2   Error   TeamCentral Application 9/30/2015 3:21:43 PM
ABC 1309    Warning ASP.NET 4.0.30319.0 Application 9/30/2015 3:21:43 PM
ABC 2   Error   TeamCentral Application 9/30/2015 3:18:24 PM
ABC 1309    Warning ASP.NET 4.0.30319.0 Application 9/30/2015 3:18:24 PM
ABC 2   Error   TeamCentral Application 9/30/2015 3:16:49 PM
ABC 1309    Warning ASP.NET 4.0.30319.0 Application 9/30/2015 3:16:49 PM
ABC 1309    Warning ASP.NET 4.0.30319.0 Application 9/30/2015 3:15:43 PM
ABC 2   Error   TeamCentral Application 9/30/2015 3:15:43 PM
ABC 1010    Error   Microsoft-Windows-Perflib   Application 9/30/2015 10:42:00 AM

在事件中，我收到了这样的消息：

    Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 9/30/2015 4:20:41 PM 
Event time (UTC): 9/30/2015 1:20:41 PM 
Event ID: 72c24cb89beb4d7f80bec250aaa686e3 
Event sequence: 757 
Event occurrence: 17 
Event detail code: 0 

Application information: 
    Application domain: /XX/XXXX/1/ROOT/TeamCentral-2-130850431401577570 
    Trust level: Full 
    Application Virtual Path: /TeamCentral 
    Application Path: C:\XXXX\wwwroot\TeamCentral\ 
    Machine name: ABC

Process information: 
    Process ID: 2180 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\NETWORK SERVICE 

Exception information: 
    Exception type: HttpException 
    Exception message: The remote host closed the connection. The error code is 0x800704CD.
   at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
   at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
   at System.Web.HttpResponse.Flush(Boolean finalFlush, Boolean async)
   at System.Web.HttpWriter.WriteFromStream(Byte[] data, Int32 offset, Int32 size)
   at DevExpress.Web.ASPxClasses.Internal.HttpUtils.WriteFileToResponse(Page page, MemoryStream stream, String fileName, Boolean saveAsFile, String fileFormat, String contentType)
   at DevExpress.Web.ASPxClasses.Internal.HttpUtils.WriteFileToResponse(Page page, MemoryStream stream, String fileName, Boolean saveAsFile, String fileFormat)
   at DevExpress.Web.ASPxGridView.Export.ASPxGridViewExporter.WriteToResponse(String fileName, Boolean saveAsFile, String fileFormat, ExportToStream getStream, ExportOptionsBase options)
   at DevExpress.Web.ASPxGridView.Export.ASPxGridViewExporter.WriteXlsxToResponse(String fileName, Boolean saveAsFile)
   at DevExpress.Web.ASPxGridView.Export.ASPxGridViewExporter.WriteXlsxToResponse(String fileName)
   at InfoArch.Web.Grid.ExportHelper.Response(ExportFileType fileType, Grid structure)
   at InfoArch.Web.Grid.GridManager.SaveToXlsx(String filename)
   at System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e)
   at System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)



Request information: 
    Request URL: http://ABC/TeamCentral/Reporting/GridView.aspx?layoutid=38&mf=report&where=&description=PZF6Q0PKJzWQDHkN08mydZNuJ3fZ(:#cd6TgCAL0hv4u4=&screenheight=618 
    Request path: /TeamCentral/Reporting/GridView.aspx 
    User host address:XXX.XXX.XX.XXX 
    User: rafeek 
    Is authenticated: True 
    Authentication Type:  
    Thread account name: NT AUTHORITY\NETWORK SERVICE 

Thread information: 
    Thread ID: 190 
    Thread account name: NT AUTHORITY\NETWORK SERVICE 
    Is impersonating: False 
    Stack trace:    at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
   at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
   at System.Web.HttpResponse.Flush(Boolean finalFlush, Boolean async)
   at System.Web.HttpWriter.WriteFromStream(Byte[] data, Int32 offset, Int32 size)
   at DevExpress.Web.ASPxClasses.Internal.HttpUtils.WriteFileToResponse(Page page, MemoryStream stream, String fileName, Boolean saveAsFile, String fileFormat, String contentType)
   at DevExpress.Web.ASPxClasses.Internal.HttpUtils.WriteFileToResponse(Page page, MemoryStream stream, String fileName, Boolean saveAsFile, String fileFormat)
   at DevExpress.Web.ASPxGridView.Export.ASPxGridViewExporter.WriteToResponse(String fileName, Boolean saveAsFile, String fileFormat, ExportToStream getStream, ExportOptionsBase options)
   at DevExpress.Web.ASPxGridView.Export.ASPxGridViewExporter.WriteXlsxToResponse(String fileName, Boolean saveAsFile)
   at DevExpress.Web.ASPxGridView.Export.ASPxGridViewExporter.WriteXlsxToResponse(String fileName)
   at InfoArch.Web.Grid.ExportHelper.Response(ExportFileType fileType, Grid structure)
   at InfoArch.Web.Grid.GridManager.SaveToXlsx(String filename)
   at System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e)
   at System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)


Custom event details: 

在提出问题之前，我已经通过 Stackexchange，我发现 ref App 域由于内存压力而被标记为卸载，但从某些角度来看，无法理解事件日志消息。

的输出select @@version；

Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) Oct 19 2012 13:38:57 版权所有 (c) Microsoft Corporation Enterprise Edition (64-bit) o​​n Windows NT 6.2 (Build 9200:) (Hypervisor)

和输出 exec sp_configure；

Name                    minimum     maximum      config_value     run_value 
max server memory (MB)   128        2147483647    2147483647     2147483647

任何建议将不胜感激。

我想说的是，我每天都会在日志文件中收到消息。

首先 I/O is freeze on Database (DatabaseName) 消息出现在日志中。消息就像

I/O 在数据库 (DatabaseName) 上被冻结。无需用户操作。但是，如果 I/O 没有立即恢复，您可以取消备份。

然后 I/O 在 Database(DatabaseName) 消息上恢复，如下所示

已在数据库 (DatabaseName) 上恢复 I/O。无需用户操作。

最后，数据库的备份已经成功完成，就像这条消息

无需用户操作

这是我的生产审计数据库，软件环境如下：

Windows Server 2012 R2
SQL Server 2012
VMware Tools

我的生产数据库“恢复模式”是“完全”恢复模式。并从 SQL Server 中的哪个登录 ID 设置维护计划备份。对所有数据库具有“ sysadmin ”权限。

备份已通过“维护计划”备份设置在特定时间安排，例如每天下午 4 点。Always Backup 在他们的计划时间间隔内成功完成。

为什么在计划备份时间会生成此类日志消息。这种消息是否会影响我的生产数据库性能。将是我的生产数据库中（备份/恢复）数据一致性的任何问题。

任何建议将不胜感激。

我已经使用 MySQL Enterprise“在线备份”选项配置了我的生产 MySQL 数据库。配置成功通过。当分配的调度程序尝试进​​行备份时，我得到以下来自 MySQL 数据库的日志错误。

一切都很好，就像 MySQL 表一样，因为这是我的生产数据库。我在 MySQL 数据库中有 44 个表，大部分表在INNODB引擎中，也有MyISAM引擎。

MySQL Enterprise Backup version 3.11.1 Windows-6.0-x86 [Tue 11/04/2014 ] 
Copyright (c) 2003, 2014, Oracle and/or its affiliates. All Rights Reserved.



mysqlbackup: INFO: Starting with following command line ...
 C:\MySQL Backup\meb-3.11.1-windows-x86-32bit\meb-3.11.1-windows-x86-32bit\bin\mysqlbackup.exe 
        --defaults-file=C:\MySQL Backup\80db2ec0-a3df-11e4-bceb-4c72b9719f9c.cnf 
        --backup-dir=C:\MySQL Backup\Fullbackup\2015-01-24_21-15-00 
        --show-progress=stdout backup 

 mysqlbackup: INFO: 
 mysqlbackup: INFO: MySQL server version is '5.7.5-m15-log'.
 mysqlbackup: INFO: Got some server configuration information from running server.

IMPORTANT: Please check that mysqlbackup run completes successfully.
           At the end of a successful 'backup' run mysqlbackup
           prints "mysqlbackup completed OK!".

150124 21:15:01 mysqlbackup: INFO: MEB logfile created at C:\MySQL Backup\Fullbackup\2015-01-24_21-15-00\meta\MEB_2015-01-24.21-15-01_backup.log

--------------------------------------------------------------------
                       Server Repository Options:
--------------------------------------------------------------------
  datadir = C:\ProgramData\MySQL\MySQL Server 5.7\Data\
  innodb_data_home_dir = 
  innodb_data_file_path = ibdata1:12M:autoextend
  innodb_log_group_home_dir = C:\ProgramData\MySQL\MySQL Server 5.7\Data\
  innodb_log_files_in_group = 2
  innodb_log_file_size = 50331648
  innodb_page_size = 16384
  innodb_checksum_algorithm = crc32
  innodb_undo_directory = C:\ProgramData\MySQL\MySQL Server 5.7\Data\
  innodb_undo_tablespaces = 0
  innodb_undo_logs = 128

--------------------------------------------------------------------
                       Backup Config Options:
--------------------------------------------------------------------
  datadir = C:\MySQL Backup\Fullbackup\2015-01-24_21-15-00\datadir
  innodb_data_home_dir = C:\MySQL Backup\Fullbackup\2015-01-24_21-15-00\datadir
  innodb_data_file_path = ibdata1:12M:autoextend
  innodb_log_group_home_dir = C:\MySQL Backup\Fullbackup\2015-01-24_21-15-00\datadir
  innodb_log_files_in_group = 2
  innodb_log_file_size = 50331648
  innodb_page_size = 16384
  innodb_checksum_algorithm = crc32
  innodb_undo_directory = C:\MySQL Backup\Fullbackup\2015-01-24_21-15-00\datadir
  innodb_undo_tablespaces = 0
  innodb_undo_logs = 128

 mysqlbackup: INFO: Unique generated backup id for this is 14221143009241185

 mysqlbackup: INFO: Creating 14 buffers each of size 16777216.
150124 21:15:03 mysqlbackup: INFO: Full Backup operation starts with following threads
        1 read-threads    6 process-threads    1 write-threads
150124 21:15:03 mysqlbackup: INFO: System tablespace file format is Antelope.
150124 21:15:03 mysqlbackup: INFO: Starting to copy all innodb files...
 mysqlbackup: INFO: Could not find binlog index file. binlogs will not be copied for this backup.
 Point-In-Time-Recovery will not be possible.
 If this is online backup then server may not have started with --log-bin.
 You may specify its location with --log-bin-index option.
Progress: 0 of 111 MB; state: Copying system tablespace
150124 21:15:04 mysqlbackup: INFO: Found checkpoint at lsn 33399309.
150124 21:15:04 mysqlbackup: INFO: Starting log scan from lsn 33399296.
150124 21:15:04 mysqlbackup: INFO: Copying log...
150124 21:15:04 mysqlbackup: INFO: Copying C:\ProgramData\MySQL\MySQL Server 5.7\Data\ibdata1 (Antelope file format).
InnoDB: ############### CORRUPT LOG RECORD FOUND
InnoDB: Log record type 56, space id 0, page number 0
InnoDB: Log parsing proceeded successfully up to 33399309
InnoDB: Previous log record type 0, is multi 0
InnoDB: Recv offset 0, prev 0
InnoDB: Hex dump of corrupt log starting 100 bytes before the start
InnoDB: of the previous log rec,
InnoDB: and ending 100 bytes after the start of the corrupt rec:
 len 200; hex 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000a0008b000000a011000000000000000000102000001020000de31c1800000004380000000001fda20d00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000; asc                                                                                                     8                                                                                                   ;
InnoDB: WARNING: the log file may have been corrupt and it
InnoDB: is possible that the log scan did not proceed
InnoDB: far enough in recovery! Please run CHECK TABLE
InnoDB: on your InnoDB tables to check that they are ok!
InnoDB: If mysqld crashes after this recovery, look at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
150124 21:15:04 mysqlbackup: ERROR: FOUND CORRUPT LOG: cannot continue!
Progress: 16 of 111 MB; state: Copying system tablespace

mysqlbackup failed with errors!

我无法从我的 MySQL 错误日志中找出确切的错误。