Sql-server – What happenes to Data when Certificated expires in SQL Server 2005

From BOL: http://msdn.microsoft.com/en-us/library/ms191291.aspx

Control - Confers ownership-like capabilities on the grantee. The grantee effectively has all defined permissions on the securable. A principal that has been granted CONTROL can also grant permissions on the securable. Because the SQL Server security model is hierarchical, CONTROL at a particular scope implicitly includes CONTROL on all the securables under that scope. For example, CONTROL on a database implies all permissions on the database, all permissions on all assemblies in the database, all permissions on all schemas in the database, and all permissions on objects within all schemas within the database.

Essentially, when you grant control, you are giving the user full access to the certificate. You may want to check out the following links for more info on sql encryption... the SQL Server Central article is really well done and is probably your best bet for a guide for how to do this.

http://technet.microsoft.com/en-us/library/ms189586%28SQL.90%29.aspx

http://www.sqlservercentral.com/articles/SQL+Server+2005+-+Security/sql2005symmetricencryption/2291/

http://www.mssqltips.com/tip.asp?tip=1319

Sounds like a timeout setting. So your SSMS thinks it takes too long and cancels the connection for you. The SQL server roles back. But there is help. You are not the first person to encounter this.

See here.

For everybody who doesn't want to click the link. Here is the price winning answer:

After hitting the same error, I stumbled upon the corrent setting.

In the Management Studio, from the Tools menu, select Options, then click "Designers". There is an option called "Override connection string time-out value for table designer updates:" In the "Transaction time-out after:" box, you will see the magic 30 seconds