I'm installing Pervasive V10 and my application vendor does not yet have any setup instructions for this particular version of Pervasive so I'm flying a little blind and documenting as I go.

My system is Server 2008 Standard 64bit with Pervasive 10 v 10.00.151.000 installed and seems to be operating.

 (1)   According to the setup instructions for the application, I need to create DSN's on the server that correspond to the names of the databases on the server.  I do not have the option to use a Pervasive Driver when setting up a DSN.   Limited testing (e.g. no data) in the app seems to work, my pervasive 9.5 system does have them setup on the server.

(2)    On my Pervasive 9.5 server, I have the data dictionary paths and data location paths setup using UNC paths such as  \\mydbserver\someshare\data     Pervasive 10 doesn't seem to like this during new setup or when modifying the path after the dB is setup so its setup using physical paths.  For remote access from a client, should this really matter?  Everything I know says it should be a physical path but I'm not a Pervasive Guru

 (3)   On the Server engine - directories tab/screen - Transaction Log Directory - what occurs exactly in this directory, it is currently setup  on C:\programdata.......    I have 2 raid sets in this box, RAID-1 for the OS and Programs,  RAID-5 for the database files.   In my previous life I had a separate raid/spindle set for transaction logs but this system I do not believe has high enough overhead to warrant such but what is the growth potential of this directory as the RAID-5 volume is much larger.   Working directory is blank, what takes place in the "working directory" and what would its ideal location be?

Looking for insight

TNGPicard / Mark L
MCDBA 2003, MCSE:Security, CCNA

TNGPicard:

 (1)   According to the setup instructions for the application, I need to create DSN's on the server that correspond to the names of the databases on the server.  I do not have the option to use a Pervasive Driver when setting up a DSN.   Limited testing (e.g. no data) in the app seems to work, my pervasive 9.5 system does have them setup on the server.

On a 64 bit OS, you need to make sure you're using the 32 bit ODBC Administrator.  It's in C:\WINDOWS\SYSWOW64.   The 64 bit ODBC Admin does not read the 32 bit drivers.  You could also use the ODBC Administrator link in the PCC to get to the right one.   

TNGPicard:

(2)    On my Pervasive 9.5 server, I have the data dictionary paths and data location paths setup using UNC paths such as  \\mydbserver\someshare\data     Pervasive 10 doesn't seem to like this during new setup or when modifying the path after the dB is setup so its setup using physical paths.  For remote access from a client, should this really matter?  Everything I know says it should be a physical path but I'm not a Pervasive Guru

It shouldn't matter.  At the engine level, it's always going to be a physical path.  I would suggest creating the DSN/DBNs at the server and not from the client.  It's a little more effort but eliminates issues with it being a remote client.
 

TNGPicard:

(3)   On the Server engine - directories tab/screen - Transaction Log Directory - what occurs exactly in this directory, it is currently setup  on C:\programdata.......    I have 2 raid sets in this box, RAID-1 for the OS and Programs,  RAID-5 for the database files.   In my previous life I had a separate raid/spindle set for transaction logs but this system I do not believe has high enough overhead to warrant such but what is the growth potential of this directory as the RAID-5 volume is much larger.   Working directory is blank, what takes place in the "working directory" and what would its ideal location be?

The Transaction Log Directory specifies the location the MicroKernel uses to store the transaction log. 

The engine ignores this setting unless Transaction Durability or Transaction Logging is turned on.

The Working Directory is where temporary files are stored.  If it's blank, the engine uses the same directory as the data file.