Hi all,<br><br>I currently have a DTS package in SQL 7.0 to import a btrieve 6.15 database to a SQL 7.0 database. It works fine when I execute it manually. But when I schedule it to be run at a later time, it did not work. It shows a "record manager not loaded" error. I use an NT domain admin account to start the SQL agent service, so it is not a security issue (I think). Can somebody who is experienced with btrieve please help me out? Thanks.<br><br>ryoh
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Problem converting Btrieve 6.15 database to a MS-SQL 7 database 1
- Thread starter ryoh
- Start date
Guest_imported
New member
- Jan 1, 1970
- 0
Hi
This is not a reply but a question related to what ryoh has already posted.
I have a file with the extension '.btr'. Now iam required to read the data and transfer it to SQLServer database. I have no experience with mainframes nor do i have any idea about btrieve files.
I donot have any Btrieve or pervasive sql engine. All i know is that SQLServer supports Data Tranformation Service - DTS, which can import data from Btrieve.
So with the input i have, that is the btr file, i want to transfer the contents to SQLserver.
Can somebody help me with this?
Thanks in advance.
This is not a reply but a question related to what ryoh has already posted.
I have a file with the extension '.btr'. Now iam required to read the data and transfer it to SQLServer database. I have no experience with mainframes nor do i have any idea about btrieve files.
I donot have any Btrieve or pervasive sql engine. All i know is that SQLServer supports Data Tranformation Service - DTS, which can import data from Btrieve.
So with the input i have, that is the btr file, i want to transfer the contents to SQLserver.
Can somebody help me with this?
Thanks in advance.
-
1
- #3
Pervasivite
Instructor
#1 - You're Btrieve engine is simply not loaded. You probably have a Btrieve 6.15 workstation engine and so it does not run all the time, but it will load automatically when you start an application that calls the interface. You can also load the engine (i.e. record manager) in the Start Up folder or upgrade to a server engine that runs as a service all the time.
#2 - DTS will import from a Btrieve file through a Btrieve engine. You will have to get a Btrieve engine to run to read the file (and you may need DDFs) and that may be a problem since Btrieve 6.15 is not sold any more, but Pervasive sells Pervasive.SQL 2000i which has a Btrieve 7.9 engine inside and will read the files and should work fine with DTS.
Pervasivite
#2 - DTS will import from a Btrieve file through a Btrieve engine. You will have to get a Btrieve engine to run to read the file (and you may need DDFs) and that may be a problem since Btrieve 6.15 is not sold any more, but Pervasive sells Pervasive.SQL 2000i which has a Btrieve 7.9 engine inside and will read the files and should work fine with DTS.
Pervasivite
This is a further question relating to Pervasivite's reply to lal77.
I have Pervasive SQL 2000 and Microsoft SQL 7.0. I am told that I must transfer data from (what I am told is a Btrieve database) to an SQL 7.0 database. The "Btrieve database" consists of files with the extensions .dat, .lck and .ddf. Can anyone tell me how to start? Any clues greatly appreciated. Thanks!
rwmatt
I have Pervasive SQL 2000 and Microsoft SQL 7.0. I am told that I must transfer data from (what I am told is a Btrieve database) to an SQL 7.0 database. The "Btrieve database" consists of files with the extensions .dat, .lck and .ddf. Can anyone tell me how to start? Any clues greatly appreciated. Thanks!
rwmatt
Pervasivite
Instructor
Which Pervasive.SQL 2000 do you have? The workstation, workgroup, NT server, NW server, Linux server? Any of these can be run automatically on startup and kept running so they are available when DTS tries to access them. A whole lot of this is explained in the Pervasive Docs which should be with the engine, but can also be obtained from the Pervasive site. There is also info the in KB which can help in this.
As far as file extension, Btrieve and Pervasive.SQL (which is also a full Btrieve 7.x) do not require any particular ones. The .lck files you need to stay away from as those are lock files for the Btrieve 5.x file format and if you delete them it will lock you out of the files. It is highly recommended that you convert all 5.x files to either 6.x or 7.x unless you copy them to systems that only have 5.x engines and use them there. Even so it is highly recommended that you get Pervasive.SQL workstation engines for those systems so that you can convert the files to 6.x or 7.x which use a totally updated data integrity algorithm. The .DDF files contain the metadata or schema for the .dat files and these are required for access by 3rd party apps like DTS and ODBC so you should leave them alone except for checking them with the consistency check in the PCC. So the .dat files are definitly the ones that actually contain the data, however, in most cases you need the .ddf files to access the .dat files and the .lck files are present when an application has the files open and records or pages locked. The .ddf and .dat files would comprise what most folks consider a 'database'.
It would probably be advisable for someone with some Pervasive and Btrieve expertise to look this over and advise you on the best path to proceed.
Pervasivite
As far as file extension, Btrieve and Pervasive.SQL (which is also a full Btrieve 7.x) do not require any particular ones. The .lck files you need to stay away from as those are lock files for the Btrieve 5.x file format and if you delete them it will lock you out of the files. It is highly recommended that you convert all 5.x files to either 6.x or 7.x unless you copy them to systems that only have 5.x engines and use them there. Even so it is highly recommended that you get Pervasive.SQL workstation engines for those systems so that you can convert the files to 6.x or 7.x which use a totally updated data integrity algorithm. The .DDF files contain the metadata or schema for the .dat files and these are required for access by 3rd party apps like DTS and ODBC so you should leave them alone except for checking them with the consistency check in the PCC. So the .dat files are definitly the ones that actually contain the data, however, in most cases you need the .ddf files to access the .dat files and the .lck files are present when an application has the files open and records or pages locked. The .ddf and .dat files would comprise what most folks consider a 'database'.
It would probably be advisable for someone with some Pervasive and Btrieve expertise to look this over and advise you on the best path to proceed.
Pervasivite
- Status