Changes for page Datenbankmanagement
Last modified by Sabrina V. on 2025/05/05 09:57
From version 7.1
edited by Sabrina V.
on 2025/05/05 09:57
on 2025/05/05 09:57
Change comment:
There is no comment for this version
To version 2.1
edited by Sabrina V.
on 2024/10/14 08:40
on 2024/10/14 08:40
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -22,7 +22,7 @@ 22 22 The purpose of reducing the size is therefore to free up space in the database. Either the database or the files it contains can be shrunk. 23 23 24 24 {{aagon.warnungsbox}} 25 -It is essential that you make a database backup before you reduce the size of the database or individual files. If you have not yet made a backup, you must do so urgently. You alone are responsible for ensuring that the database can be restored in the event of an error. Read here how to create an [[ACMP backup >>doc:.Vollständiges ACMP Backup durchführen.WebHome]]and how to [[restore>>doc:.Vollständiges ACMP Backup einspielen.WebHome]] it. 25 +It is essential that you make a database backup before you reduce the size of the database or individual files. If you have not yet made a backup, you must do so urgently. You alone are responsible for ensuring that the database can be restored in the event of an error. Read here how to create an [[ACMP backup >>doc:.Vollständiges ACMP Backup durchführen.WebHome]] and how to [[restore>>doc:.Vollständiges ACMP Backup einspielen.WebHome]] it. 26 26 {{/aagon.warnungsbox}} 27 27 28 28 == Shrink database == ... ... @@ -31,7 +31,7 @@ 31 31 When shrinking a database, make sure that applications such as ACMP or others are not accessing the database. If this is not the case, the shrink will not be optimal, will be very slow or will not be performed at all. So make sure that the relevant services do not access the ACMP database. Use the Activity Monitor to check for possible processes and stop them. 32 32 {{/aagon.infobox}} 33 33 34 -The size of a database is reduced by reducing the size of the database files. This applies to the areas of the database files that are completely free (see also [[Defragmenting the Indexes>>doc:||anchor="HInde xesDefragmentation"]]). If you only want to reduce the size of individual database files, use the [[//Reduce files//>>doc:||anchor="HDatenbankverkleinern"]] option.34 +The size of a database is reduced by reducing the size of the database files. This applies to the areas of the database files that are completely free (see also [[Defragmenting the Indexes>>doc:||anchor="HIndizesDefragmentierung"]]). If you only want to reduce the size of individual database files, use the [[//Reduce files//>>doc:||anchor="HDatenbankverkleinern"]] option. 35 35 36 36 After you have closed all relevant applications, processes and sessions, go to the Microsoft SQL Server Management Studio left-hand navigation and select the database you want to shrink. Right-click to open the context menu and click //Tasks// > //Contract// > //Database//. 37 37 ... ... @@ -165,7 +165,7 @@ 165 165 166 166 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. 167 167 168 -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. Thefirst columnintheview isthesort order. Select the //Latin1_General_CI_AS// collationthat we recommend(see also the graphic below). Thiscollation isused for bothUnicodeand non-Unicode.Inthesecond 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:168 +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: 169 169 170 170 |(% style="width:136px" %)**Recovery Model**|**Explanation** 171 171 |(% style="width:136px" %)Full|All database changes are logged. There are no time or size restrictions. Storage and backup requirements are significantly increased.