There is a Hotfix available on microsoft site.

Pl refer http://support.microsoft.com/kb/910416

How about you script out all of the stored procedures into one file, then do a replace on:

AS

Change it to:

WITH ENCRYPTION

AS

Just use notepad or any other text editor to do...

Replace your decrypt query with :

SELECT CONVERT(NVARCHAR(100),DecryptByKey(emppassword)) FROM dbo.Employees

i.e replace char with nVarchar.

For further help see: http://allaboutoraclemssql.blogspot.com/2008/06/sql-2005-encryption.html

SQL Password is a password recovery tool for MS SQL Server 2000, 2005, 2005 Express and MSDE 2000 (Microsoft SQL Server Desktop Engine).

You can either try to find the...

With Microsoft SQL Server 2000 it was possible to debug stored procedures from directly within Query With SQL Server 2005, however, this functionality was moved out of SQL Server Management...

Yes, as earlier posts says, use views.

Apart from that you can use encryption/decryption to hide values and allow to show table column.

use [database]

select name, physical_name from sys.database_files

To avoid deadlock, you must have through knowledge of your application.

1. Identify the deadlocking processes and the object sparticipating in deadlock.

2. Use program monitoring table, say Program_session having columns program_id...

1. Use "Create Script" to create tables. This will ensure the correct data structure abd its FK, PK and all constraints.

2. Use BCP Out and BCP In to copy...

1. Check the index fill factor .

Ideally it should be 70% for highly updating tables and 100% for rest DML opearations.

2. Check whether any anti-virus is installed on SQL server...

Turn off Hyper Threading on SQL 2005 host computers as the default.

HT-enabled motherboards show markedly degraded performance under heavy load. Disabling HT restores expected levels, according to reports from within...

Pl check the hardware configuration of both Dev and production server.

If CPU is bottleneck, then you should study and configure settings for parallelism, Hyperthreading.

You can use before insert and after insert and such triggers to store data in history and present table.

Yes, Jef, you are correct.This should apply to tables.

-Avishkar

If your database is read only (low number of updates), use a fillfactor of 100%.

If your database is write intensive (writes greatly exceed reads), use a fill factor somewhere...