Create databases and database user

In Microsoft SQL Server Management Studio:

1. Right-click databases, and select New Database…

2. In Database name, enter ZyDB, and click OK.

3. Right-click databases, and select New Database…

4. In Database name, enter ZyStatDB, and click OK.

In Microsoft SQL Server Management Studio:

1. Right-click security, and select New > Login…

2. In Login name, enter ZyUser

3. Select SQL Server authentication

4. Clear User must change password at next login, Enforce password expiration, and Enforce password policy

5. Enter the password for MSSQL user ZyUser

6. In Default Language, select English

7. Click User Mapping

8. In Users mapped to this login, select ZyDB

9. In Database role membership for ZyDB, select db_owner

10. In Users mapped to this login, select ZyStatDB

11. In Database role membership for ZyStatDB, select db_owner

12. Click OK

Verify that database recovery model, database maintenance, and backup configuration are properly taken care of.

If no transaction log backup job is configured for regular execution, and Recovery model for a database is set to Full or Bulk-logged, the database transaction log files (LDF files) will expand until the disk is full. In that case, verify that the database recovery model for ZyDB and ZyStatDB is simple.

To verify the recovery model:

1. In SQL Server Management Studio, right-click the ZyDB database and select Properties

2. Click Options

3. In Recovery model, you can choose between Simple, Full, or Bulk-logged.

   • If your backup strategy includes transaction log backups for regular execution, select Full

   • If your backup strategy doesn't include transaction log backups for regular execution, select Simple

4. Repeat the steps for the ZyStatDB database

For SQL Server Express, simple is default. However, for SQL Server Standard or Enterprise editions, the default is full, and that means that the log disk is likely to run out of space at some point, if you don't set up transaction log backup jobs for regular execution as a part of your database backup strategy.

For more information, see Proactively monitor disk usage of SQL Server