Turns out they aren't. Some ppl released database with size more than 500MB, uhm well, the db size is actually quite small, the internal SQL log files that are big.
Here imma show you how to reduce the size of your database files. Well, smaller the size, more efficient in process, and of course, more faster. This is prolly useless to you, but what heck i'll share it anyway :P
Here comes the boring part:
1) set the database properties (1 time only), (IMPORTANT: you must have 'sa'/administrator access to your SQL server, and you must login with 'sa' account)
Code:
USE [master] GO ALTER DATABASE [SRO_VT_ACCOUNT] SET RECOVERY SIMPLE WITH NO_WAIT ALTER DATABASE [SRO_VT_SHARD] SET RECOVERY SIMPLE WITH NO_WAIT ALTER DATABASE [SRO_VT_LOG] SET RECOVERY SIMPLE WITH NO_WAIT GO ALTER DATABASE [SRO_VT_ACCOUNT] SET AUTO_CLOSE ON WITH NO_WAIT ALTER DATABASE [SRO_VT_SHARD] SET AUTO_CLOSE ON WITH NO_WAIT ALTER DATABASE [SRO_VT_LOG] SET AUTO_CLOSE ON WITH NO_WAIT GO ALTER DATABASE [SRO_VT_ACCOUNT] SET AUTO_SHRINK ON WITH NO_WAIT ALTER DATABASE [SRO_VT_SHARD] SET AUTO_SHRINK ON WITH NO_WAIT ALTER DATABASE [SRO_VT_LOG] SET AUTO_SHRINK ON WITH NO_WAIT GO ALTER DATABASE [SRO_VT_ACCOUNT] SET AUTO_UPDATE_STATISTICS_ASYNC ON WITH NO_WAIT ALTER DATABASE [SRO_VT_SHARD] SET AUTO_UPDATE_STATISTICS_ASYNC ON WITH NO_WAIT ALTER DATABASE [SRO_VT_LOG] SET AUTO_UPDATE_STATISTICS_ASYNC ON WITH NO_WAIT GO
Code:
USE [master] GO DBCC SHRINKDATABASE ('SRO_VT_ACCOUNT') WITH NO_INFOMSGS; DBCC SHRINKDATABASE ('SRO_VT_SHARD') WITH NO_INFOMSGS; DBCC SHRINKDATABASE ('SRO_VT_LOG') WITH NO_INFOMSGS; GO DBCC UPDATEUSAGE ('SRO_VT_ACCOUNT') WITH NO_INFOMSGS; DBCC UPDATEUSAGE ('SRO_VT_SHARD') WITH NO_INFOMSGS; DBCC UPDATEUSAGE ('SRO_VT_LOG') WITH NO_INFOMSGS; GO
3) Now this is the result of database backup without SQL internal log and everything shrunk:
With that file size, you rar it, you'll get less than 10% total size :P, 100MB to 4MB , pretty efficient, maybe?
have fun