Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
gobeach
Starting Member
3 Posts |
 Posted - 2002-02-22 : 11:09:30
|
| We're having a database which run under System 1032 running VAX/VMS system. We want to convert it to PC application and doing the research to see what database application is easy and possible to convert to before we decide to do that. Please give us an advice, thanks!Edited by - gobeach on 02/22/2002 12:31:13 |
|
|
nlocklin
Yak Posting Veteran
69 Posts |
Posted - 2002-02-24 : 02:05:09
|
| Hi gobeach,I work for a group that is currently running System 1032 on a VAX/VMS system, and is in the process of migrating to a Microsoft environment using SQL Server. I'd be glad to answer any questions that you might have. You can e-mail me at locklin@nsabp.pitt.edu or send me a message through this site.Basically you have several options. Your best bet is to purchase the ODBC driver for System 1032. I've worked extensively with it, and have found it to be pretty painless. I currently use the ODBC driver to copy data between System 1032 on the VAX and our SQL Server every night. I put together a simple DTS package that imports the datasets from S1032 into SQL Server (or from SQL Server to S1032), and even handles situations where some of the data in the table is maintained in S1032, and some in SQL Server. It's pretty easy to set up, and effortless to maintain.You can also convert a System 1032 dataset to a Microsoft Access database, but it involves a lot more than using the ODBC driver:http://gri.gallaudet.edu/~kjcole/Tutorials/1032.htmlI'd strongly recommend getting the S1032 ODBC driver. I also think that SQL Server (and a Microsoft environment) is probably your best bet. It's pretty simple designing DTS packages to exchange data between SQL Server and S1032, and if your current applications are written in Fortran, the switch to Visual Basic is not dramatic. You can even use existing Fortran code in your PC applications for a while if you need to using Fortran.NET.--"I'm always doing that. I'm always messing up some mundane detail." |
 |
|
|
gobeach
Starting Member
3 Posts |
Posted - 2002-02-27 : 12:56:41
|
| Hi nlocklin,Thanks a lot for your helping. I also think that it's ms sql server is the best application to choose to convert from s1032. Could you please explain and give more detail (general steps) on how to convert it with s1032 odbc driver? Thank you very much!Edited by - gobeach on 02/27/2002 13:00:04 |
|
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2002-02-27 : 17:02:08
|
| He pretty much just did explain it. You might want to do a little reading and experiementing with DTS, then it will make some more sense.Damian |
|
|
|
nlocklin
Yak Posting Veteran
69 Posts |
Posted - 2002-02-27 : 23:09:30
|
| The System 1032 ODBC driver (which is what I'd recommend using) comes with a pretty good (although a little thick) manual.Basically how it works (after you've installed the S1032 ODBC driver on the VAX & clients) is as follows:- The ODBC driver creates a dictionary for your 1032 datasets on the VAX.- You can add datasets to the dictionary with a simple command (like "ADD TABLE MEMBERS /FILENAME=USR$:[DATADIR]MEMBERS.DMS")- After the dataset has been added to the S1032 ODBC dictionary, you can create a DTS package (usually even using the simple import/export wizard), specifying the 1032 driver as the source and selecting the datasets that you want to import.There are a few issues to watch out for. For example, when a new version of the dataset gets created on the VAX, the dictionary pointed will be to the version number it had when it was created so you have to re-add the dataset to the dictionary (unless there's some easier way to manage that that I haven't found yet). But basically transferring data back and forth from 1032 with SQL Server is very simple.--"I'm always doing that. I'm always messing up some mundane detail." |
|
|
|
|
|
|
|
|
Is that easy to convert from S1032 to SQL Server