vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| After creating database in SQL Server , it generates .mdf , .ndf datafiles . Generally if we get those datafiles then we can create the database with tables/data on another machine by using those datafiles. I want to know, if we can we protect this? I don't want another user to take those files and create database on another SQL Server. Is there any option available in SQL server while creating database to protect this file with password or any darn thing for protection that would not allow to create the database by using those file or any workaround. Thanks in advance for your help. |
| ||||
| "Ashwani" <engg_akyadav@yahoo.com> wrote in message news:c1710804.0410050549.7c3ab340@posting.google.c om... > After creating database in SQL Server , it generates .mdf , .ndf > datafiles . > Generally if we get those datafiles then we can create the database > with tables/data on another machine by using those datafiles. > > I want to know, if we can we protect this? I don't want another user > to take those files and create database on another SQL Server. Is > there any option available in SQL server while creating database to > protect this file with password or any darn thing for protection that > would not allow to create the database by using those file or any > workaround. > > Thanks in advance for your help. No, that's not possible (you can set a password on a backup set, though). However, since only administrators should be able to access the server filesystem, the best approach is simply to ensure that you're following standard security procedures: NTFS permissions are properly set (administrators and the MSSQL service only), no users have direct access to the filesystem, no one has sysadmin access except sysadmins etc. You can use the MBSA to check your current security configuration: http://www.microsoft.com/technet/sec.../mbsahome.mspx Also see the resources here about securing SQL Server: http://www.microsoft.com/sql/techinf...ty/default.asp Simon |