Jump to content
Sign in to follow this  
alioven

KSC unassigning reserved disk space on SQL Server [Solved]

Recommended Posts

Greetings,

 

This is a question about the backup function in KSC 10 (current version 10.2.575, patched). This is using a SQL Server database on a remote server. When KSC starts the backup, it does a big transaction that duplicates the database size while, we guess, it cleans up old events and data. After this, it saves the database to disk and then the files related to KSC. We've observed that after the database backup preparation is done, KSC cleans up the big transaction and then it makes SQL Server unassign the disk space allocated. This leaves SQL Server with little room for the next day new events and data and triggers its automatic growing function that will allocate again disk space for the data that is added in the next day.

 

For example:

 

- Prior to backup: Data size: 8 GB, Disk space allocated for DB by SQL Server: 10 GB (data and logs)

- During backup: Size is doubled, disk space allocated extended by the same proportion.

- After backup: Data size: 7 GB, Disk space allocated: 8 GB (KSC made SQL Server unassign the other 8 GB it used during backup).

 

Our IT department has their own control and optimization scripts for our SQL Server infrastructure, and this "optimization/clean up" by unassignation of disk space that KSC is forcing over SQL Server conflicts with those scripts. Also, this makes SQL Server assign new disk space every day when new data is collected from the workstations and it slighty affects the performance of the database due to small pauses to allocate the disk space and the subsequent fragmentation it causes. We understand KSC will clean up the database again at night backup but we would prefer to control this feature ourselves using our own SQL Server administration scripts.

 

Is it possible to control this final step of the backup function and disable the disk space de-assignation? The GUI has no option for this but may be the developers have some hidden control for it. If this is not implemented, could it be suggested for a future version of the product, please?

 

Kind regards.

Edited by alioven

Share this post


Link to post
Greetings,

 

This is a question about the backup function in KSC 10 (current version 10.2.575, patched). This is using a SQL Server database on a remote server. When KSC starts the backup, it does a big transaction that duplicates the database size while, we guess, it cleans up old events and data. After this, it saves the database to disk and then the files related to KSC. We've observed that after the database backup preparation is done, KSC cleans up the big transaction and then it makes SQL Server unassign the disk space allocated. This leaves SQL Server with little room for the next day new events and data and triggers its automatic growing function that will allocate again disk space for the data that is added in the next day.

 

For example:

 

- Prior to backup: Data size: 8 GB, Disk space allocated for DB by SQL Server: 10 GB (data and logs)

- During backup: Size is doubled, disk space allocated extended by the same proportion.

- After backup: Data size: 7 GB, Disk space allocated: 8 GB (KSC made SQL Server unassign the other 8 GB it used during backup).

 

Our IT department has their own control and optimization scripts for our SQL Server infrastructure, and this "optimization/clean up" by unassignation of disk space that KSC is forcing over SQL Server conflicts with those scripts. Also, this makes SQL Server assign new disk space every day when new data is collected from the workstations and it slighty affects the performance of the database due to small pauses to allocate the disk space and the subsequent fragmentation it causes. We understand KSC will clean up the database again at night backup but we would prefer to control this feature ourselves using our own SQL Server administration scripts.

 

Is it possible to control this final step of the backup function and disable the disk space de-assignation? The GUI has no option for this but may be the developers have some hidden control for it. If this is not implemented, could it be suggested for a future version of the product, please?

 

Kind regards.

 

Hello.

 

In existing versions of KSC, described specifics of the backup procedure are predefined, balanced for optimal load and performance, and therefore not availabe for tweaking.

You can suggest this as a feature for consideration in future versions by creating an incident in CompanyAccount and describing your cause.

 

Thank you!

Share this post


Link to post

Hello,

 

We guessed so. We've created a case in CA, INC000006061628 (in spanish) similar to the post above, it is still awaiting Technical Support reply, we will ask them to forward this as a future feature then.

 

Thank you.

Share this post


Link to post
Hello,

 

We guessed so. We've created a case in CA, INC000006061628 (in spanish) similar to the post above, it is still awaiting Technical Support reply, we will ask them to forward this as a future feature then.

 

Thank you.

 

Thank you for your feedback!

Please let us know if you have other questions.

Share this post


Link to post
Sign in to follow this  

×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.