> Taskkill will be ok if no one user worked with yours database and no internal > process worked with your database. And it's not OK when you have more > than one database on such server, because you interrupt working sessions to > another databases.
All of which will not corrupt a database if Forced Write = ON, due to "careful writes algorithm" of the engine. This ensures that no database corruptions occur in the event of process termination on power failure. > I corrupted databases very well with such method. It's like sudden reboot > when users work. We kill tasks/processes all of the time, to both dev and production databases -- as the need requires (sometime you just need to boot/kill processes). We have *never* had any database corruption. Sean
