You are currently reviewing an older revision of this page.
There is an error message in the SELECTserver log files that the SQL transaction logs are full.
As time goes by, the disk space requirements for the SELECTserver database may fluctuate greatly. This is due to how SQL server functions and will require the database to be maintained. You can set SQL Server to automatically expand a database when it requires more space; and you can also set it to "shrink" so it can reclaim allocated but unused space. Sometimes it makes sense to enable autogrow and autoshrink events, and sometimes it doesn't.(See KB #315512 from Microsoft for information about enabling each of these options.)
ShrinkingData Files (*.MDF / *.NDF)
If you haven't enabled the auto-shrink setting, there may be times when your database has been cleared of significant amounts of data, and you'd like to reclaim the space on disk that the partially empty MDF file is taking up. To do this, you can use the DBCC SHRINKDATABASE command. See this MSDN entry for the technical documentation on the DBCC SHRINKDATABASE or DBCC SHRINKFILE commands:
To shrink the SQL Transaction logs, first figure out the database recovery mode. To find out if you database recover mode is set to full, bulk-logging, or simple right click on database, properties, click on Options in the window, 2nd drop down is the mode. Here is bit more info on DB recovery modes: http://msdn.microsoft.com/en-us/library/aa173531%28v=SQL.80%29.aspx
If your database recovery mode is set to FULL or bulk-logging, use the SQL statement below.
The example script looks like this
ALTERDATABASE [TestDb] SET RECOVERY SIMPLE WITH NO_WAIT
ALTERDATABASE [TestDb] SET RECOVERY FULL WITH NO_WAIT
When you use the statement above youhave to change some of the values to match your database for a test db. This iswhat it looks like with a database name of hdr_oma_2-15-11
ALTERDATABASE [SELECTserver] SET RECOVERY SIMPLE WITH NO_WAIT
DBCCSHRINKFILE(SELECTserver _Log, 1)
ALTERDATABASE [SELECTserver] SET RECOVERY FULL WITH NO_WAIT
In this case, SELECTserver is the name of the database as seen in sql management studio
SELECTserver_Log is the logical name of the transaction log. You can find this by right clicking on the database and selecting properties, click on 'files' and look in the 'logical name' column.
If your database recovery mode is set to Simple the script is a bit simpler,
So in my case
Increase SQL Server Performance for the SELECTServer
SELECTserver FAQ:http://communities.bentley.com/products/licensing/w/Licensing__Wiki/selectserver-general-faq.aspxDeployed SELECTserver Knowledge Requirements