Changes for page Datenbankmanagement

Last modified by Sabrina V. on 2025/03/31 09:30

From 2.1 to 1.1 From 5.1 to 4.1

From version 4.1

edited by Sabrina V.
on 2025/01/24 07:12

Change comment: There is no comment for this version

To version 2.1

edited by Sabrina V.
on 2024/10/14 08:40

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -165,7 +165,7 @@
  If you have not set any or incomplete settings for the log files, you can change these in the properties of the ACMP Database. To do this, first exit the ACMP server service.
--Then open the Microsoft SQL Server Management Studio, log in using the login information and then select the ACMP Database in the navigation on the left. Execute a right-click on the ACMP Database and click on Properties in the context menu that opens. The database properties for the database open. Select the Options menu item. The first column in the view is the sort order. Select the //Latin1_General_CI_AS// collation that we recommend (see also the graphic below). This collation is used for both Unicode and non-Unicode. In the second position//, //define a //Recovery Model//. The [[Recovery Model>>https://learn.microsoft.com/de-de/previous-versions/sql/sql-server-2008-r2/ms189275(v=sql.105)?redirectedfrom=MSDN) ]] is an option with which you can define how a los is handled:
++Then open the Microsoft SQL Server Management Studio, log in using the login information and then select the ACMP Database in the navigation on the left. Execute a right-click on the ACMP Database and click on Properties in the context menu that opens. The database properties for the database open. Select the Options menu item. In the second position in the view is the entry Recovery Model. The [[Recovery Model>>https://learn.microsoft.com/de-de/previous-versions/sql/sql-server-2008-r2/ms189275(v=sql.105)?redirectedfrom=MSDN) ]] is an option with which you can define how a los is handled:
  |(% style="width:136px" %)**Recovery Model**|**Explanation**
  |(% style="width:136px" %)Full|All database changes are logged. There are no time or size restrictions. Storage and backup requirements are significantly increased.