TestStand Database

[WayneR1]

Is there anyway to flush the database without shutting down TestStand?

I have a project that generates lots of data and with a 2G file limit for the database it get full within a few day. TestStand runs contiunally so i was wondering if there is a way to copy and rename the existing file and then copy an empty database file back in without stopping Teststand?

Thanks for any help.

[Dennis_Knutson]

What database are you using?

[WayneR1]

I am using the Generic Recordset that is built in to TestStand 2013.

[Norbert_B]

This doesn't answer the question. It answer how the database has to look like for TS to be able to log into it.

What is the DB provider you are using?

Please note that TS is a client of the database. The client has to call into the database for modification of the data inside the database. So it is depending on the database provider if there is an easy way to "reset" the database/tables.

Also you might find Google a good source for information regarding SQL table 'resets'.

Norbert

[WayneR1]

Sorry, i misunderstood the question.

It is set up in TestStand to use the Access Database, this generates the TestStand Resuls.mdb in C:\Users\Public\Documents\National Instruments\TestStand 2013\Components\Models directory. When TestStand logs results it generates a locking file TestStand Results.ldb (I think that is the extension) and this file does not get released until the current sequence is stopped exited.

Because my application generates vast amounts of results the .mdb file get full in a couple of days, this is in a production environment so the operator can not stop TestStand from running in order to copy\rename the full database file to something else and then generate a fresh database file.

If I select a different Database Management System, say Oracle, would i get a larger .mdb file? Is the fact that i have set it to Access limiting the size the file can get too.

Thanks for the help. 

[Dennis_Knutson · Accepted solution]

You would obviously not have an mdb file with Oracle or SQL Server but, yes, the file size limit would be much higher. The management would be more robust and the locking would not be so obtrusive.

[Dennis_Knutson]

I don't know much about Oracle but be aware of the difference between SQL Server and the express version. The free version does have size limitations.