Encrypted data size by original size, algorithm ?

I want to know encrypted data's size for designing database field size.

For example, cardnumber varchar(20) Encrypted by Triple_DES and PassPhrase, How match size does need to encrypted data store field.

I think the size does not depend to PassPhrase char length.

Regards,
Yoshihiro Kawabata

The simplest way is to just encrypt the largest piece of data that you will store using the encryption algorithm of your choice and take note of the size of the resulting blob. That will be the size of the field. There is also a formula that allows you to compute this, but it also includes the size of a header which might expand in future versions of SQL Server. I suggest to always leave several bytes more to account for changes in the format of encrypted data.

Thanks
Laurentiu

|||

Here's a post that describes how to determine the length of the encrypted data for SQL Server 2005:

http://blogs.msdn.com/yukondoit/archive/2005/11/24/496521.aspx

Thanks
Laurentiu

Encrypted data size by original size, algorithm ?

I want to know encrypted data's size for designing database field size.

For example, cardnumber varchar(20) Encrypted by Triple_DES and PassPhrase, How match size does need to encrypted data store field.

I think the size does not depend to PassPhrase char length.

Regards,
Yoshihiro Kawabata

The simplest way is to just encrypt the largest piece of data that you will store using the encryption algorithm of your choice and take note of the size of the resulting blob. That will be the size of the field. There is also a formula that allows you to compute this, but it also includes the size of a header which might expand in future versions of SQL Server. I suggest to always leave several bytes more to account for changes in the format of encrypted data.

Thanks
Laurentiu

|||

Here's a post that describes how to determine the length of the encrypted data for SQL Server 2005:

http://blogs.msdn.com/yukondoit/archive/2005/11/24/496521.aspx

Thanks
Laurentiu

Empty Warning box appears with only OK button (2 processes started) when I open Microsoft SQL se

Hello,

I'm new to SQL server 2005. I installed SQL server 2005 and had some problems with the original install. I therefore uninstalled SQL server 2005. Rebooted and than installed SQL server 2005 again. Everything appears to have installed correctly except for the fact that when I start SQL Server Management Suite I get 2 copies running in the foreground. The last copy of the SQL Server Management Suite shows a dialogue box that contain a warning sign (yellow triangle) with no text but an OK button is in the dialogue box. When I press the OK button, this instance of SQL Server Management Suite kills itself. The first instance is now given window focus and it brings up the "Connect to Server" dialogue box. I can connect to my local server and run a script to add columns to the database. But everytime I bring up SQL Server Management Suite, I always end up with 2 copies running and I have to hit the OK button to get rid of the second copy. Can anyone help me get ride of this annoying problem?

Hello,

I solved this problem! I installed windows XP Pro updates and one of the updates was the Update for .NET Framework 3.0 x86(KB932471). When I went to add/remove programs and removed this update, Microsoft SQL server management suite came up just like it is suppose to (only one instance running and the "Conncet to Server" Dialogue box is present.

JoAnn