database management

The database is stored where ever you create it.

I don't know about the import/export/cleaning question you have, but I do know hat what we are using right now, with DP+ 5.2 and SQL Server 2008 R2, our database has a max of 4g, and after nearly 4 years, I've made it to 1.5g. So, I'm not sure how worried you need to be about the limit.

Also, are you using DataPageStats.exe which creates an XML file and DataImporter to push it to the database, or connecting directly to it? We use the former method, with a remotely located database for multiple computers to import data, and with tho9se XML files, you always have a backup to your created database backup. (And a backup backup, and daily datapage computer backup, and a backup database from when we upgraded... :square

It took a lot of trial and error till I finally succeeded sending from pcdmis to dp+, all is working as far as data coming thru....it's connecting directly to it thru ODBC data source & SQL express. When the database is created there are only 2 files that show up in the location I set up, one with a .mdf (main database file) & one with .ldf (log database file) extensions. These files do not change size at all, even though I have many parts and transactions in datapage...this can't be where actual data is stored?

sdaley, you should be seeing the mdf file grow. If you are not, then you need to double check that you're looking at the right mdf file. Our mdf file is just over 1.5 gigabytes right now.

Hi VinniUSMC,

Thanks for your responses. There is only one .mdf file in the directory where database is created (only the two files total) and they do not change size on any of the 3 machines. All the data is coming thru as expected... data, trace values, etc. Guess I'll see if tech support will talk to me.

RT and + are not the same animal and should not be treated the same. With RT each part has it's on database and with + you only have one database and all parts are stored in that database.
Unless data is corrupt, you should not be deleting any data from the Datapage+ database.

The database location is going to be where ever it was created and if you don't know then you need to have someone who has experience with MSSQL investigate it.

RT and + are not the same animal and should not be treated the same. With RT each part has it's on database and with + you only have one database and all parts are stored in that database.
Unless data is corrupt, you should not be deleting any data from the Datapage+ database.

The database location is going to be where ever it was created and if you don't know then you need to have someone who has experience with MSSQL investigate it.

ummmm, no, there is NOT a database for each part in RT, they are all in ONE file, ONE database. You can, however, make as many databases as you want.

Peter,

As I've stated numerous times all the data is coming thru as intended, I created the database so I know its location . I am totally aware RT and + are different animals, just as Unix RT and Windows RT are different animals, I'm still using Unix on 3 machines. We run a lot of parts and I'm sure it will use up the 2 gig limit eventually, this is why I'm certain the database will need backed up and cleaned at some point. I will continue to investigate this anomaly.

Thanks

Thank you Matt !!

Peter,

As I've stated numerous times all the data is coming thru as intended, I created the database so I know its location . I am totally aware RT and + are different animals, just as Unix RT and Windows RT are different animals, I'm still using Unix on 3 machines. We run a lot of parts and I'm sure it will use up the 2 gig limit eventually, this is why I'm certain the database will need backed up and cleaned at some point. I will continue to investigate this anomaly.

Thanks

Okay so SQL2008R2 should have a 10 gig data limit, that should be the version of SQL that was installed with 5.0. I just attach to a new database on a yearly basis and back up my .MDF and .LDF files, and yes these are the actual location of stored data. Your best friends if you don't know already are "Data sources(ODBC)" which is a tool built into Windows for creating links to a database that may have been broken or exists on a remote computer so you can create a DSN (Data Source Name). Also SSMS (SQL Server Management Studio) which you can use to detach and reattach a database to a SQL server, this is a tool that needs to be downloaded from Microsoft.

My typical course of action is to create a Database on a yearly basis and back them up in a secure location but leaving them attached to the SQL server in case I need to review old data. Database size is limited but number of databases is not so you can have as many databases connected to your SQL server as you want. In DP+ I just choose which database I want to connect to and as far as sending data you will need to change the database that you output to depending on the tools you use to get data in.

4 gig. I'm using it now, and it is definitely 4 gig. (At least, according to the error message we received when upgrading from 2011, and SQL2005).

Also, I would like to know more about this yearly DataBase thing you do. My IT is pretty helpful usually, but I need to know how to communicate things to him, or else I risk going off on 17 tangential journeys before maybe reaching my destination.

Are you saying that you start a new DataBase every year? So, like, CompanyDatabase2016, CompanyDatabase2017, and then, if you want to see old data, just change the database source within DataPage?

4 gig is the limit for 2008, 2008R2 has is supposed to have a 10 gig limit but this will be dependent on hardware too. You can't have a 10 gig database on a machine with 4 gigs of ram or a system still using fat32 which has a 4 gig file size limit.

But yes, I just create a new database called "CompanyDatabase2017" and switch all of my data sources to the new database, if I want to see old data then I just connect to the old database in Datapage. I then shut down the SQL service and copy the file for a backup, I do not delete it and then restart SQL. (Databases cannot be moved while the SQL service is running, alternately you can use SMSS to take the database offline and then bring it back up after it's been moved)