The maximum ProISAM record size is now -r16000 with a maximum file size of 1.9 GB. We started using this size in version 7. See help topic 720111 in the 22.214.171.124 online documentation.
- Stef likes this
Jump to content
Posted by Joy Chapman on 26 April 2016 - 04:05 PM
How old is it? Well, very old... feel free to laugh:
04/26/16 McDonnell Information Systems CAT//PTS_TR
** * **
pppppppppppppp nnnnnnnnnnnnn oooooooooooooo ** ** **
PPPPPPPPPPPPPPPP RRRRRRRRRRRRRRR OOOOOOOOOOOOOOOO ** ** **
PPP PPP RRR RRR OOO OOO ** ** **
PPPppppppppppPPP RRRnnnnnnnnnRRR OOO OOO ** ** **
PPPPPPPPPPPPPP RRRRRRRRRRRRR OOO OOO ** ** **
PPP RRR RRR OOO OOO ** ** **
PPP RRR RRR OOOooooooooooOOO ** ** **
PPP RRR RRR OOOOOOOOOOOOOO ** ** **
Version : 2.2000 Revision : r02.3.0 May 09, 94 Bootstrap Revision : 2.2.007
Posted by Ross Bevin on 15 April 2016 - 06:06 PM
It's quite simple. This is what I would do for each file.
1. Copy the ProISAM ProIV filedef to a file with say a small 's' appended to the name. E.g. GL_MSTR to GL_MSTRs.
2. In the file definition header change GL_MSTRs to file type SQLSERVE. Set the physical name as GL_MSTR. You will also have to go into the storage tab and set the Ext Type, format and alternate name for each field. Alpha fields are ALPHA and numeric fields are NUMBER. For NUMBER the format is <total field length including precision>.<precision>. If the number can be a negative append the format with an "S". E.g. S8.2 (can store a max of 999999.99-)
3. In the file definition window use the SQL icons to create and save the script to a text file for GL_MSTRs.
4. In SQL Server Management Studio open the script previously created and execute it in the right database to create the table.
5. Create an update function that reads all of GL_MSTR in look mode and adds to GL_MSTRs in add mode.
6. Delete file definition GL_MSTR.
7. Rename file definition GL_MSTRs as GL_MSTR.
8. Regen functions that use GL_MSTR.
You will need to update your c:\windows\pro4v8.ini file with the appropriate SQL database settings. You will also need to create an ODBC driver on the server that has the ProIV kernel; it needs to point to the SQL Server database.
When I did this for our system in 2003 I automated the process by writing a series of functions that used the filedef bootstrap files to create one SQL table creation script file. I also wrote a function that automated the file renaming. If your system is large you may want to consider this route.
A word of caution with moving to SQL Server. Depending on how your system is written/structured you may encounter a lot of table locking. This is especially true for control files where you say get the next available invoice number. In ProISAM you can have a logical update that gets and increments the number. After the record is written it is unlocked and other sessions can read and update it. This is not true for SQL tables. Typically you will have to either exit the function to commit the records or execute a commit command in logic. Executing the commit command can have unwanted consequences with other tables you are processing. Because of this we continue to maintain our control files in ProISAM.
Hope this helps!
Posted by kapoof on 05 January 2016 - 08:57 AM
Posted by DARREN on 25 February 2014 - 10:40 PM
Agreed, but the values that can be selected for both the variables (which are given meaningful names for the purpose of display) and the selection values are table driven and are validated. The only way that SQL injection could occur is if the DBA did it himself.
Posted by Richard Bassett on 25 February 2014 - 02:32 PM
Obligatory Little Bobby Tables reference:
The serious point to remember is that using dynamic SQL enables SQL injection attacks, so you should always put in place appropriate sanitization of the variable text you are splicing into your SQL, otherwise bad things can happen to good people.
Posted by Neil Mellis on 20 January 2014 - 02:10 AM
No real gotchas with Postgresql. I did get caught out when moving from 8.1 to 9.2 and experienced initial cache building on my whole inventory. which turned out to be a bad index that behaved differently between versions.
When creating/converting tables I don't use the script creator within Proiv as this is a bit loose I just define it properly in pgAdmin.
I chose to use Postgresql to reduce cost of deployment on smaller user systems and provide a cross platform compatibility for Linux and Windows. The use of a ISO SQL also means that an up scale to Oracle is pretty straight forward.
I also chose to hybrid my data between pro-isam and the database. Most new stuff is mainly DB and designed to take advantage of it. Legacy only gets migrated when I need it - usually for more efficient retrieval or during larger changes.
Posted by Neil Mellis on 16 January 2014 - 12:43 AM
Don't forget that proiv lock logic doesn't work with postgresql so any lock will result in a spinning session until the lock owner releases. NG were going to look into handling this but no news yet.
I ended up having to use a pro-isam lock file where I really need critical tables to be managed properly.
Doing this also has the advantage that you only have to 'B' mode the pro-isam file with the keys and the lock logic gives you an opportunity for the user to respond to the lock or a timed/count retry prior to any table access. The pro-isam file can double as an audit as Neil B has suggested.
By using this method iscollect will clean up the pro-isam lock on a session failure no need for user/admin lock screens etc.
Posted by Kelvin Rapley on 09 October 2013 - 12:59 PM
Posted by Ross Bevin on 07 February 2013 - 01:41 PM
Posted by Lewis Mccabe on 14 April 2011 - 04:46 AM
Posted by DARREN on 16 April 2010 - 12:58 PM