Size Comparison of SwSQL with MS SQL

From support-works
Jump to: navigation, search



Status: Published
Version: 1.1
Authors: HTL QA
Applies to: Supportworks ESP

Size Comparison of SwSQL with MS SQL

The chart below compares the amount of space various quantities of specific types of database content stored by Supportworks will occupy in SwSQL and MS SQL, respectively. The two size columns show the cumulative totals as you keep adding the content indicated. Note that the space taken up by transaction logs is not included, so that a like-for-like comparison can be given.

Database Content SwSQL Actual Size (KB) MS SQL Actual Size (KB)
Blank database 0 3145
Clean installation 232 3145
1 site record 236 3145
1 charge centre record 239 3145
1 customer record 248 3145
10 site records 249 3145
100 customer records 263 3145
1 logged call (1 record in opencall + updatedb with 1000 words) 303 3145
10 calls logged 395 3145
50 calls logged 754 3145
100 calls logged 1177 3145
200 calls logged 2155 4194
300 calls logged 3114 5242
400 calls logged 4044 6291
500 calls logged 4981 7340
600 calls logged 5912 8388
700 calls logged 6857 9437
800 calls logged 7777 10485
900 calls logged 8710 11534
1000 calls logged 9652 12582
1000 calls then updated with 1 update of 1000 words 18246 20971
1000 calls then updated with 2nd update of 1000 words 26756 30408
1000 calls then updated with 3rd update of 500 words 31152 38797

General Observations

  • For a service desk with a rapid turn-around of calls (and therefore a low to medium volume at any given time), the MS SQL database is substantially larger than the corresponding MySQL database.
  • For a service desk with a high volume of calls, with one or two updates being required on average, the difference reduces to about 10%-15%.
  • For a service desk with a high volume of calls that have multiple updates totalling more than 2000 words, the difference is likely to increase again.
Personal tools
Namespaces

Variants
Views
Actions
Navigation
Tools