If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup

You might have to re-create the publication as indicated...

Nice step by step illustration at-->http://blogs.msdn.com/sqlserverfaq/archive/2009/03/31/setting-up-database-mirroring-in-sql-server-2008-using-t-sql-when-the-database-is-encrypted-using-transparent-data-encryption.aspx

MJ

Check-->http://www.pragmaticworks.com/Products/Business-Intelligence/DTSxChange/

DTS xChange - DTS to SSIS Migration

DTS xChange is an enterprise ready tool to convert DTS packages to SSIS 2005/2008 with very little manual effort. DTS xChange...

First try to find what exactly is consuming the most in proc. cache.

SELECT name,

[MB used] = SUM(single_pages_kb + multi_pages_kb)/1024.0

FROM ...

Good read-->http://sqlblog.com/blogs/kalen_delaney/archive/2007/12/08/hyperthreaded-or-not.aspx

MJ

Read -->http://sqlserverpedia.com/blog/sql-server-bloggers/identifying-the-high-cpu-sql-instance/

and you will get to know howto link them with correct instances using process ID.

MJ

http://www.databasejournal.com/features/mssql/article.php/3841271/T-SQL-Best-Practices--Parameter-Sniffing.htm

MJ

Better remove that node from MSCS and then proceed with any uninstallation/maintenance.

In 2000

Evict Node from Microsoft Cluster Service (MSCS). To evict a node

from MSCS, from...

u r right.

This event type or event group can be specified when you create Event Notifications to monitor and respond to activity in the database or server instance.

http://msdn.microsoft.com/en-us/library/ms180599(SQL.90).aspx

MJ

Do a sp_helpuser against ur db and see if ur login comes in output with required permissions.

MJ

Nice licensing tool

http://www.microsoft.com/licensing/mla/product.aspx

MJ

Take help from -->http://www.mssqltips.com/tip.asp?tip=1860

Also, include type column from backupset table for type of backup performed.

MJ

Login with that id and execute SELECT * FROM fn_my_permissions (NULL, 'DATABASE');

to see what permissions user has in db and compare them.

http://msdn.microsoft.com/en-us/library/ms176097.aspx

It looks only 32GB would be addressable by OS in such case. Better configure each instance max server memory in such a way that when all instances failover to one...

Moin,

Please specify your OS and SQL version/Edition.

Windows Server 2003, Standard Edition supports physical memory up to 4 GB.

Windows Server 2003, Enterprise Edition supports physical memory up to 32 GB.

Windows Server...