deepfreeze for computers with databases

Hello I’m considering Deep freeze for business. I have 8 Microsoft pos embedded 2009 and 2 Microsoft 2008 servers. Even though I don’t want configuration changes done, I need databases to change. I was wondering how deep freeze deals with systems with databases. Can you please help me understand how the system Works, thank you very much.

Normally in most workspaces, databases aren't on workstations, but on the servers instead, and more often than not they don't include things like DeepFreeze.

DeepFreeze is useful in untrusted terminals that may be easily compromised, like where browsers with careless users runs, but those are terrible locations for databases, which are secured in servers instead. And since the servers have more safe environments than workstations, and since you lose every file on it if you use it, you don't want DeepFreeze there.

So don't worry about databases, keep them away from the users and DeepFreeze what the users will touch directly.

Alejandro85 said:

Normally in most workspaces, databases aren't on workstations, but on the servers instead, and more often than not they don't include things like DeepFreeze.

DeepFreeze is useful in untrusted terminals that may be easily compromised, like where browsers with careless users runs, but those are terrible locations for databases, which are secured in servers instead. And since the servers have more safe environments than workstations, and since you lose every file on it if you use it, you don't want DeepFreeze there.

So don't worry about databases, keep them away from the users and DeepFreeze what the users will touch directly.

I get your point but im struggling with some viruses which corrupt windows files, but does not harm the database on workstation. On the other hand I have seen that deepfreeze has an app for servers, I was thinking of leaving the database in the thawed area.

kivi12 said:

im struggling with some viruses which corrupt windows files

In that case the very first thing you MUST do is to reformat all affected computers. Things like DeepFreeze can help to prevent reinfection, but only if you can ensure it wasn't infected in the first place.
Assuming the virus wasn't powerful enough to tamper with the DeepFreeze image.

kivi12 said:

but does not harm the database on workstation.

You can never ensure that, once a virus entered your system, it can do whatever the user can, so if the user can read and write a database, so can the virus (wheter or not it really does, it depends on what is the exact malware, but you should never rely on this).

However, having a database on a workstation is a terrible mistake, for more than security. For starters, you can't easily share it among users, which impedes teamwork, or need to share from a workstation, which complicates network configuraton.
But most important it prevents proper backups, as the IT staff won't go into each computer to backup what's important there. Also, there is the security issue of the computer becoming compromised, and the user having full access to take the DB with him if he really wants.

Generally speaking, it's often said that the only important thing in the network are the servers, so that's where all the attention should go. Any data on workstations is considered temporary and unimportant, so it's not cared for. That's why databases and important files are ons propertly secured servers.

kivi12 said:

On the other hand I have seen that deepfreeze has an app for servers, I was thinking of leaving the database in the thawed area.

DeepFreeze is not a good idea for servers (and I can't think why they need a different program at all). Servers aren't public untrusted places, but controled work areas with secured systems in them. There is little need for it, as any change made was made by an administrator or a properly autorized user. Normal backups cover accidental damage or a virus infection.