Since my previous posts on security, I have come under a degree of pressure at work to secure Sequel Server using the same methods that everyone else will be using to secure source data (mainly text files) and statistical programs.

My colleagues' preferred method is to secure drives using Truecrypt. My issue with this is that, on my main computer, I have Sequel Server running on 4 physical drives: system files on C; temp db on E; data files on F and logfiles on G. This is efficient from the perspective of performance but I wonder how Sequel Server would react if all 4 drives were encrypted. At the least, I can see myself for ever entering passwords just to do any work - in effect, I would have to decrypt each drive before even running Sequel Server...presumably...In addition, I'm not convinced that Sequel Server will work at all with this arrangement. - My installation is on standalone boxes (no networking).

Can anyone advise me about the practical implications of using a disk encryption program in the way I describe above?

I am running 05 Developer under W Server 2003 x64 and also under XP x64.

Thanks.

Chris

 

 

Hi,

Earlier I have used SQL Shield in one of the instance we support and have a good experience of it.

Which edition of SQL Server you are using!! IMO If it is SQL Server 2005 the best option is to use built-in feature, refer Encryption (SQL Server) in BOL and http://www.databasejournal.com/features/mssql/article.php/3714031.

Regards

If you are using any encryption on the operating system level then you may hit major problems in SQL Server too, in thsi case as Hemant referred better usage of such encryption on database level can be achieved using 2005 or even 2008 version of SQL Server. If you are keen on security level on operating system then make sure to control or remove any access on the server in terms of users, put the SQL behind the firewall.

 Thanks, Hemant and Satya. I am running 64-bit 05 Developer under W Server 2003 x64 and also under XP x64.

 I have had a look at the suggested reference for managing encryption at the database level - and this looks like the best way forward (in fact, it looks pretty much ideal from my point of view). I will test it shortly and then, if it works, tell my colleagues that this is how I am going to do it!

Chris

First things first you cannot use DEVELOPER edition for production purpose, so please advice for what this system will be used.

 I am not using Developer Edition for production purposes. I use it to develop methods that enable me to output text data to statisticians. I never provide SQL solutions.

Chris