Product specifications

SQL Server
324 3BDS011222-510 B
SQL Server
SDL data collection never gives severe loads on the system. But it will give server
loads, when starts using the data stored in SDL database. This is caused by the
processes of data retrieval from the databases.
The following parameters can affect the system performance
• Number of users accessing SDL databases.
• Number of other databases supported by this particular database instance.
• Number of queries being run and their occurrences.
• Number of queries running concurrently and serially.
• Kind of transaction isolation level used.
• Transactions blocking SDL processing.
• Moved/deleted amount of oldest data in the SDL database.
If a given system can not comply with this requirement directly, then a number of
workarounds can be applied:
• Run the offending queries at times were there is no production activity.
• Lower the Transaction Isolation Level of the offending transactions.
(Transaction Isolation Levels for the SQL Server are in decreasing isolation
order. They are SERIALIZABLE, REPEATABLE READ, READ
COMMITTED and READ UNCOMMITTED). At the lowest isolation level no
database locking occurs.
• Shorten the offending transactions.
• Divide offending transactions into two or more separate transactions.
• Delete the oldest data in SDL database.
No database activity can block SDL function for a longer period of time, than half
of the wanted tolerance on timestamps of SDL Logs.
Deleting old data from SDL database is explained in System 800xA Post
Installation (3BUA000156*).