How To Clean Up Airwatch Db To Make It Better

Annihilation the uses a database needs to accept the database settings configured correctly, this includes all the VMware tools. I've had a couple of customers contact me recently about VMware's AirWatch system because the transaction log on the database keeps growing. The reason in both cases so far is because the database is using the default settings and the transaction log was never backed up. I talked most this at Microsoft's TechEd conference a couple of years ago during my talk titled "Introduction to SQL Server Management for the Non-DBA". If you adopt a VMware themed slide deck, I've given basically the aforementioned presentation at VMworld likewise (registration required).

Fixing this is actually a actually uncomplicated fix. Yous need to do one of two things.

Alter the recovery model from Full to Uncomplicated.
Showtime taking transaction log backups of the database

Now, how do you select the i of these that you want to exercise? That's pretty easy. Do you need signal in time recover-ability of the database? If the respond to that question is yes, then select option two. If the answer to that question is no, so select option 1.

With well-nigh AirWatch systems you don't really intendance if the database is restored to what information technology looked like yesterday or 5 minutes ago, so you lot ordinarily don't need point in time recovery. So just change the database from Full to Simple and you're good to go. Doing this is really really piece of cake. Connect to the SQL server in SQL Server Direction Studio. Right click on the database and select properties. Change the recovery model from FULL to Uncomplicated, and so click OK. That's it the log won't grow any more.

If you need to reclaim the space considering the deejay is full, then you need to compress the log file. To practise this, click the "New Query" push button at the top of management studio and run the following command.

DBCC SHRINKFILE (2, 1024)

That'll compress the file down to i Gig and it "shouldn't" ever grow any larger than that. There's no outage to doing this, and no gamble to the organisation. Because of the way that shrinkfile works yous may need to run it a couple of times over a couple of days in order to actually get all the space back.

If you don't accept SQL Server Direction Studio, or you tin't find the properties, here's a script that'll do everything that I've described. Merely run this in the AirWatch database (it could be named anything so y'all have to change the database name in the USE statement from YourDatabaseName to whatever the name of your AirWatch database is).

Use YourDatabaseName GO declare @dbname sysname ready @dbname = db_name()  declare @sql nvarchar(thousand) gear up @sql = 'ALTER DATABASE [' + @dbname + '] SET RECOVERY Uncomplicated'  exec (@sql) GO CHECKPOINT GO CHECKPOINT GO DBCC SHRINKFILE (ii, 1024) GO

Denny