Changes for page Datenbankmanagement

Last modified by Sabrina V. on 2026/10/06 06:31

Manage
- Copy
Actions
- Export
- Print Preview
Viewers
- Source
- Children
- Content

From version 1.1

edited by jklein
on 2024/08/13 08:28

Change comment: Imported from XAR

To version 9.1

edited by Sabrina V.
on 2026/10/06 06:31

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.jklein
++XWiki.SV

Content

@@ -9,7 +9,7 @@
  Even if the database is working properly, there are bound to be problems over time, such as indexes becoming fragmented, logs taking up a lot of space, or the database itself simply becoming too large. The result is often a drop in performance, longer load times when retrieving data, or unpredictable behaviour of the database. In short, the database system no longer works as it should, or cannot be started at all until more space is created.
--To counteract this, you should always take the time to maintain your existing database system. Below are some recommendations and hints on how to maintain your ACMP database and some useful countermeasures you can take.
++To counteract this, you should always take the time to maintain your existing database system. Below are some recommendations and hints on how to maintain your acmp database and some useful countermeasures you can take.
  {{aagon.infobox}}
  The following examples are based on working with Microsoft SQL Server Management Studio. We recommend that you install the application that allows you to connect to a server to perform database maintenance. The Studio does not need to be installed on the server running the SQL Server instance!
@@ -22,22 +22,21 @@
  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.
  {{aagon.warnungsbox}}
--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.
++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.
  {{/aagon.warnungsbox}}
  == Shrink database ==
  {{aagon.infobox}}
--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.
++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.
  {{/aagon.infobox}}
--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.
++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="HIndexesDefragmentation"]]). If you only want to reduce the size of individual database files, use the [[//Reduce files//>>doc:||anchor="HReducingthesizeoffiles"]] option.
  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//.
  {{figure}}
--(% style="text-align:center" %)
--[[image:66_Datenbank_Datenbank verkleinern_690.png]]
++[[image:66_Datenbank_Datenbank verkleinern_690.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Shrink database
@@ -62,14 +62,13 @@
  If you do not want to reduce the size of an entire database directly, but only selected database files and/or groups of files, you can make such changes separately. This can be useful if, for example, you can identify which of your database files are very large and you want to reduce their size. In this case, the size of the database will be reduced by reducing the size of individual files or groups of files.
  {{aagon.infobox}}
--Please note that this procedure does not free up any allocated database space. To do this, you must include all the database files, which can be done using the  [[Shrink database>>doc:||anchor="HDatenbankverkleinern"]] option.
++Please note that this procedure does not free up any allocated database space. To do this, you must include all the database files, which can be done using the [[Shrink database>>doc:||anchor="HShrinkdatabase"]] option.
  {{/aagon.infobox}}
  In Microsoft SQL Server Management Studio, open the database in which you want to shrink files. Right-click to open the context menu and select //Tasks// > //Shrink// > //Files//.
  {{figure}}
--(% style="text-align:center" %)
--[[image:66_Datenbank_Datei verkleinern_690.png]]
++[[image:66_Datenbank_Datei verkleinern_690.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Reducing the size of files
@@ -76,7 +76,7 @@
  {{/figureCaption}}
  {{/figure}}
--In the //Database// row you can check that you have selected the correct database. In this case you should see the name of the ACMP database. In the pictures above this is called "ACMP". You can now select the type under the //Database Files and File Groups// heading.
++In the //Database// row you can check that you have selected the correct database. In this case you should see the name of the acmp database. In the pictures above this is called "acmp". You can now select the type under the //Database Files and File Groups// heading.
  {{aagon.infobox}}
  Depending on the file type selected, the user interface may vary slightly as not all fields are always available.
@@ -110,17 +110,16 @@
  Make sure that your user account has the appropriate rights to perform a defragmentation.
  {{/aagon.warnungsbox}}
--Click //Connect// and the Management Studio will open in the background. Navigate to the Object Explorer on the left hand side of the menu bar and open the ACMP database.
++Click //Connect// and the Management Studio will open in the background. Navigate to the Object Explorer on the left hand side of the menu bar and open the acmp database.
  {{aagon.infobox}}
  Make sure you select the correct database from the drop down box to avoid making changes to the wrong database.
  {{/aagon.infobox}}
--Executions Right click on the ACMP Database and select //New Query// from the context menu that opens.
++Executions Right click on the acmp Database and select //New Query// from the context menu that opens.
  {{figure}}
--(% style="text-align:center" %)
--[[image:66_Datenbank_Aufruf einer neuen Abfrage_478.png]]
++[[image:66_Datenbank_Aufruf einer neuen Abfrage_478.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Insert new query
@@ -135,8 +135,7 @@
  ##EXEC ap_index_defrag 0,0##
  {{figure}}
--(% style="text-align:center" %)
--[[image:66_Datenbank_Ausführung einer neuen Abfrage_837.png]]
++[[image:66_Datenbank_Ausführung einer neuen Abfrage_837.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Execute query SQL script in query
@@ -144,20 +144,20 @@
  {{/figure}}
  {{aagon.infobox}}
--Make sure that you have selected the correct entry from the available databases (here: ACMP), so that you can run the query on the correct database.
++Make sure that you have selected the correct entry from the available databases (here: acmp), so that you can run the query on the correct database.
  {{/aagon.infobox}}
  Then click on //Executions//. Two tabs (Results and Messages) will open at the bottom of the Editor, displaying messages after each execution (whether successful or not). Close Microsoft SQL Server Management Studio when you are finished.
--The command rebuilds the indexes of the ACMP database and also performs a reduction of the database..
++The command rebuilds the indexes of the acmp database and also performs a reduction of the database..
  {{aagon.warnungsbox}}
  Running the above SQL script in combination with [[backup>>doc:.Vollständiges ACMP Backup durchführen.WebHome]] should be done regularly (e.g. once a month) to avoid possible database problems.
  {{/aagon.warnungsbox}}
--= ACMP database too large due to log files =
++= acmp database too large due to log files =
--The ACMP database can also fill up quickly and become too large because of the log files.
++The acmp database can also fill up quickly and become too large because of the log files.
  The log files are important for two reasons:
@@ -167,20 +167,19 @@
  The log files are located under //MSSQL\Data//. However, the database and the log file should each be on a separate disk, which not only separates them but also improves performance. The files are saved as MDF or LDF files, where the MDF files contain the actual data and are therefore often larger than the LDF file. The LDF file is a support file that stores information about the transaction logs. Check both the location and the size of the files.
--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.
++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. 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:
++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:
  |(% 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.
  |(% style="width:136px" %)Bulk logged|As with the full recovery model, a log backup is created, but this model uses slightly less storage and keeps the backup smaller. It can be used, for example, for an import with a large number of records.
--|(% style="width:136px" %)Simple|The log memory is automatically freed as this model can only write to files up to a certain size. The oldest data is deleted when the size is reached. This model is often used for the ACMP database.
++|(% style="width:136px" %)Simple|The log memory is automatically freed as this model can only write to files up to a certain size. The oldest data is deleted when the size is reached. This model is often used for the acmp database.
  If "Full" or "Bulk logged" is set in the drop-down field, change the entry to "Simple".
  {{figure}}
--(% style="text-align:center" %)
--[[image:66_Datenbank_Datenbankeigenschaften_698.png]]
++[[image:66_Datenbank_Datenbankeigenschaften_698.png||data-cmp-info="10" data-xwiki-image-style-alignment="center"]]
  {{figureCaption}}
  Customize recovery model
@@ -189,4 +189,4 @@
  Then click //OK// and the window will close.
--Then reduce the size of your database. To do this, follow the steps in the section [[Shrinking the database>>https://learn.microsoft.com/de-de/previous-versions/sql/sql-server-2008-r2/ms189275(v=sql.105)?redirectedfrom=MSDN) ||anchor="HDatenbankverkleinern"]].
++Then reduce the size of your database. To do this, follow the steps in the section [[Shrinking the database>>https://learn.microsoft.com/de-de/previous-versions/sql/sql-server-2008-r2/ms189275(v=sql.105)?redirectedfrom=MSDN) ]].