Re: network permissions for Btrieve (PSQL 8.x) files

This is possible with all versions of Pervasive.SQL V8.5 and higher
(including v8.6, v8.7, v9.0, and v9.1).

What you want is the "Advanced Security" infromation -- for which you
should read the manual carefully (plan to have an hour of quiet time to
review the contents and concentrate on it), and then implement on a
test server first. It isn't very clear unless you understand the
database, but once implemented, you can lock out all user access from
the OS level (in fact, don't even need READ access to the database) and
still use the database from both Btrieve and SQL/ODBC.

The added security is WELL worth the time investment, but don't
shortchange the process -- plan to have lots of time to test before you
do this in a live environment...
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - July 19-22 ***
*** Chicago: Pervasive DataExchange Class - July 27-29 ***

nmm wrote:

> Hi,
>
> we have the following problem. On a Win2KServer (or Win2003Server) we
> have PSQL 8.x installed. Than we have a set of Btrive-files and a
> application, that accesses that files via btrieve (not SQL/ODBC -
> just native Btrieve BTRCALL-API).
>
> In this situation the clients must know the real networkpaths to that
> btrieve-files. As far as we know: to update/insert records the
> client-user must have write-rights on that btrieve-files.
>
> Now the question: is it possible to restrict the write-rights to that
> files for the usual client-users (on windows-level), but make
> pervasiveSQL-Server able to update/insert nevertheless?
>
> The PSQL-server-service on the Win2003server runs under higher rights
> than the client-users.
>
> In former Novell-versions this was possible!
>
> Any hint will be wellcome.
>
> Regards
> M. Malarski
.

Relevant Pages

  • Re: Maintenance Plan Caused System To Hang
    ... ran DBCC CHECKDB) I was connected to the server through Terminal Services. ... Even though the server has 2 GB of RAM and is used exclusively for SQL 2005, ... maintenance plan in SQL 2005 and ran it. ... Back up the database and transaction log ...
    (comp.databases.ms-sqlserver)
  • Strategy for a databse
    ... I have some experience with building a database of people, ... regular trips but often also charters of various lenghts. ... I need to plan ... For all these things, and many others I have reports, in Excel format, ...
    (microsoft.public.access.gettingstarted)
  • Re: DBCC Checkdb,
    ... Fehler beim Maintenance Plan mit dem ich leider nichts anfangen kann. ... ich habe zur leichteren Fehlerfindung alle weiteren Step disabled - es ... bleibt nur der erste Step Check Databases über. ... The Check Database Integrity task and the Execute T-SQL Statement task in a maintenance plan may lose database context in certain circumstances in SQL Server 2005 builds 3042 through 3053 ...
    (microsoft.public.de.sqlserver)
  • Re: Wiki software for genealogy (long)
    ... "When we've ironed out the bugs, this will be the one everyone wants" hands-down over any given 5-year plan of business. ... You can kludge most of 'em into doing the other, and you can even browbeat 'em into doing a migration database, but they won't do 'em as well as a dedicated program will. ... Which is why a first requirement should be for a package, not a single program, to be built around a database for which a decent toolset is available - at the very least for reporting. ... If the data is accessible in that way and the data model is well designed in the first place a whole set of programs can be built round it, either by the vendor or by sufficiently skilled users. ...
    (soc.genealogy.britain)