“sql-server-administration”的相关标签问题

0 投票

1 回答

9455 浏览

sql - 数据库“tempdb”的事务日志已满

我只有对我正在查询的数据库的读取权限。从昨天开始，相同的查询一直在工作，但今天我在 sql server management studio 中遇到了以下错误。

数据库“tempdb”的事务日志已满。要找出日志中的空间不能被重用的原因，请参阅 sys.databases 中的 log_reuse_wait_desc 列

非常感谢任何想法或建议。提前致谢！！

2017-06-17T19:03:45.503

0 投票

0 回答

603 浏览

sql-server - SQL Server 连接错误：不支持将 IsolationLevel 设置为 ReadCommitted

我正在尝试从 Anypoint Studio 连接到 SQL Server，但出现以下错误：

这是我正在使用的连接字符串：

谢谢

sql-server mule anypoint-studio sql-server-administration

2017-08-04T21:03:32.710

0 投票

1 回答

158 浏览

sql-server - Detaching a database as a backup strategy

I've read dozens of articles about why this is a bad idea. The arguments against using a detached database as a backup are legion. However, I still think that in my case, it makes good sense. Realizing that those are often the words of admins who know too little, I'd like to put my strategy to the good folks here to see if someone can tell me why what I'm doing would be more properly done with the internal backup mechanism.

Let me address some of the common issues.

My database files are almost full, so the fact that backups only copy utilized pages isn't relevant to me;
I'm not using any filestream storage;
my application can handle small bursts of downtime when I detach and make a copy;
The various file permission nightmares that accompany detaching databases have already been solved.

The total size of the DB is about 1TB. My main reason for detaching and attaching instead of using backups is performance. In my testing, it is significantly faster to detach the database, make a copy of the underlying files, and attach the original files again than it is to perform a backup. During recovery, it is also significantly faster to attach files (even if I have to copy them to the proper location first) than it is to restore them.

I can get around the backup performance problem by using something other than a full backup, but that doesn't help when it comes to restoration. In the event of a disaster, I need to be back up and running quickly. My application can handle small amounts of downtime periodically, but any large stretch of downtime is disastrous. Restoring 1TB of database takes longer than the business wishes to tolerate for the application.

The last item I've often read is that detaching a database comes with some risk. Just like we ought to perform test restores of backups, I immediately attach any copied MDF/LDF/NDF files to a disaster recovery SQL Server to make sure the copy is good. I suppose my exposure here is that I could detach the database and break something such that the original DB files can no longer be re-attached. Honestly, I've never seen this, so if this is really a possibility, I feel that it's quite remote. I'm doing this nightly, so I'd lose a day's worth of reporting data in this (unlikely?) scenario.

Am I missing anything else?

sql-server database-design database-administration sql-server-administration

2018-09-04T15:06:10.070

0 投票

1 回答

141 浏览

sql-server-2012 - 扩展事件和 SQL Server Profiler

我了解扩展事件和 SQL Server Profiler 的概念，我觉得它们都在做同样的工作。我无法理解它们之间的主要区别。谁能解释一下扩展事件和 SQL Server Profiler 之间的主要区别？我们什么时候可以在生产环境中使用？SQL Server Profiler 是否更适合生产服务器？

sql-server-2012 sql-server-administration

2018-11-21T06:16:57.330

0 投票

1 回答

49 浏览