- Aug 13 Wed 2014 15:25
-
Cannot alter the user 'dbo'. (Microsoft SQL Server, Error: 15150)
- Apr 30 Tue 2013 16:32
-
Microsoft SQL Server, Error: 3729
要刪除帳號或是Schema時出現:
Cannot drop schema '[SchemaName]' because it is being referenced by object '[TableName]' (Microsoft SQL Server, Error: 3729)
Solution:
USE [DATABASENAME]
GO
- Mar 04 Mon 2013 14:23
-
The error message in SQL Server Configuration Manager:The remote procedure call failed.[0x800706be]
OS:Windows 2012
安裝完SQL Server 2008 R2後,在SQL Server Configuration Manager的SQL Server Services中出現:
The remote procedure call failed.[0x800706be]
無法看到service的列表,
在安裝SQL Server 2008 R2 SP2後獲得解決
- Jan 04 Fri 2013 15:59
-
Database Suspect on SQL Server 2008 R2
- Dec 27 Thu 2012 17:18
-
SQL Server Service修改啟動帳號的密碼時出現:WMI Provider Error - Access is denied 0x80070005
因為SQL Server Service的啟動帳號是".\LocalAccount",
修改密碼時出現WMI Provider Error - Access is denied 0x80070005的錯誤訊息,
Solution:
將啟動帳號的欄位中的值由".\LocalAccount"改為"LocalAccount",
在輸入新密碼,就沒有出現錯誤訊息了
- Sep 03 Mon 2012 11:13
-
Database status is Suspect in SQL Server 2000
- Aug 10 Fri 2012 15:27
-
SQL Server 2008 R2各版本的功能差異
- Aug 10 Fri 2012 15:16
-
不用給予sysadmin角色,但是要可以使用SQL Server Profiler
想使用SQL Server Profiler,但是不想給予帳號有sysadmin角色,
在SQL Server 2005之後,可以另外給予權限,
GRANT ALTER TRACE TO [USER_ACCOUNT]
--移除權限
REVOKE ALTER TRACE FROM ehrsa
- Aug 01 Wed 2012 17:34
-
SQL Server Installation Center可以得知安裝資訊
Start -> All Programs -> Microsoft SQL Server <Version Number> -> Configuration Tools -> SQL Server Installation Center
在Tools section中,可以在Installed SQL Server features discovery report得到安裝在本機服務器中SQL Server的相關信息
- Aug 01 Wed 2012 17:21
-
判斷Table是否存在
方法一:
IF EXISTS (SELECT * FROM sys.tables WHERE name = N'[Table_Name]')
DROP TABLE [Table_Name]
方法二:
IF OBJECT_ID(N'[Table_Name]', N'U') IS NOT NULL
- Jul 26 Thu 2012 18:21
-
Error 3117 - The log or differential backup cannot be restored because no files are ready to rollforward
Restore database (restore full + transaction log) 時出現下列錯誤:
Msg 3117, Level 16, State 1, Line 1
The log or differential backup cannot be restored because no files are ready to roll forward.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
- Jul 26 Thu 2012 18:11
-
Error 3049 - BACKUP detected corruption in the database log
Backup Transaction Log時出現錯誤,
Msg 3049, Level 16, State 1, Line 1
BACKUP detected corruption in the database log. Check the errorlog for more information.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
