Database Size

[EKL]

My company started using TestStand not too long ago and we are logging results to MS SQL Server 2005 using the Generic Insert schema.  The database file size has grown very quickly and I am hoping someone can help me keep this under control.  Even though ANSI Padding is set to OFF at the database, TestStand records data with trailing spaces anyway so that varchar fields are filled up.  For example, PATH in PROP_RESULT is of type varchar(1024) but the great majority of the "data" is made up of blank spaces.

I know very little about TestStand itself and am primarily involved with database administration.  Does anyone have a solution to this problem other than writing a script to periodically lop off the trailing blank spaces in every field?  Is there something else that is contributing to this file size growth?  I've considered using big ints instead of GUIDs but it's kind of too late for that.  Any suggestions would be greatly appreciated.  Thanks.

[Perry_S]

Hi EKL,

What Version of TestStand are you using? What Operating System is Teststand runnig on? Are you logging the report files or are you getting the results and logging those with modules written to perform those tasks?

Regards,

Perry S.

[EKL]

Thanks for your reply.

We are using TestStand 4.2.1 on Windows XP Pro and Windows 7 machines.

I'm not sure what is meant by logging the report files vs using modules.  Under Configure Database, I simply pointed TS to the server and database and entered the necessary credentials.

[SteveChandler]

I don't know how to do this in Test Stand. But if I were the database admin I would write a trigger or a rule that trims the whitespace on insert.

[Perry_S]

Hi EKL,

Could you post a simple example that re-creats your issue? That would help me to figure out where the white spaces are being added and if there is a way to stop it.

Perry S.

[Rodéric]

If I were you I would resize some elements maybe varchar (255) and delete some tables/columns that are not necessary maybe you don't need the error message if you already have the error code

Maybe you just need the uut_result not all the step_result (you can clean the steps that passed and keep the failed ones)

if you delete a column or table you have to edit TestSTand scheme to connect to the database (otherwise TestSTand will recreate the missing items)

Hope this helps