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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL.INI configuration file help

Status
Not open for further replies.

GuysonGuy

IS-IT--Management
Aug 4, 2006
3
US
I have SQLConsole installed on a client machine. When I try and launch the application, I get an error message that says: "Could not connect to the SQLConsole database. Would you like to create the local database?" If I click yes, the Create SQLConsole database Wizard appears and prompts for a username and password. I enter the credentials for the local machine, and I get this error message "Database name not configured".

Below are the contents of my sql.ini file:

;
; Centura Software Corporation 1996
; SQLBase INItialization file
;
;-------------------------------------------------------------------
; SECTION: Database engines (Windows, Win32, NetWare).
;-------------------------------------------------------------------
;
; NOTES:
; -----
; - SORT and SORTCACHE: In general, the sum of these two parameters
; should not be more than 1/4 th the total real memory available on
; the system. For eg. on a 32 MB machine, the combined values of SORT
; and SORTCACHE could be as high as 8MB.
;
; - DBDIR, LOGDIR and TEMPDIR: These parameters direct the placement of
; database, log and temporary files. For systems with multiple disks,
; immediate performance gains can be realized by directing these files
; to different disk subsystems. For eg. on a system with two disk
; subsystems, DISK1 and DISK2, you may want to set 'DBDIR=DISK1' and
; 'LOGDIR=DISK2' so that I/O throughput is maximized.
;

[dbwservr.comments]
;
; Windows
;-------------
; This section is for the LOCAL Multi-Tasking windows database engine.
; Multiple Windows applications may connect to it at the same time.
; Each is treated as a separate transaction.
;
; System incompatibilities can exist among DBWSERVR, Windows 3.x, and
; SMARTDRV. These incompatibilities can cause outages and/or loss of data if
; the correct settings are not used. For DBWSERVR, always use DIRECTIO=0. For
; SMARTDRV, always disable write caching for disk drives where databases
; exist that DBWSERVR may use. Please refer to the Release Notes for further
; information.
;
[dbwservr]
servername=server1
cache=1500
sortcache=1000
locktimeout=2
directio=0

[dbntsrv.comments]
;
; Win32 (Windows 95 and NT)
;-------------------------------
; This section is for the SQLBase Win32 database server. You can
; specify which communication protocol(s) the server can use as well as which
; protocol(s) a database can use.
;
[dbntsrv]
dbname=ISLAND,SQLAPIPE
servername=server5,sqlapipe
cache=2000
sortcache=2000
readonly=0
oracleouterjoin=0
logfileprealloc=0
partitions=0
optimizerlevel=2
locktimeout=275

[dbntsrv.gui]

[dbntsrv.dll]
comdll=sqlapipe

[dbntsrv.apipe]

[dbntsrv.ntnbi]

[dbntsrv.ws32]

[dbnt50sv.comments]
;
; This section is for the 25-User SQLBase Win32 database server.
;
[dbnt50sv]
servername=server1,sqlapipe
dbname=island,sqlapipe
cache=2000
sortcache=2000

[dbnt50sv.gui]

[dbnt50sv.dll]
comdll=sqlapipe

[dbnt50sv.apipe]

[dbnt50sv.ntnbi]

[dbnt50sv.ws32]

[dbnt25sv.comments]
;
; This section is for the 25-User SQLBase Win32 database server.
;
[dbnt25sv]
servername=server1,sqlapipe
dbname=island,sqlapipe
cache=2000
sortcache=2000

[dbnt25sv.gui]

[dbnt25sv.dll]
comdll=sqlapipe

[dbnt25sv.apipe]

[dbnt25sv.ntnbi]

[dbnt25sv.ws32]

[dbnt10sv.comments]
;
; This section is for the 10-User SQLBase Win32 database server.
;
[dbnt10sv]
servername=server1,sqlapipe
dbname=island,sqlapipe
cache=2000
sortcache=2000

[dbnt10sv.gui]

[dbnt10sv.dll]
comdll=sqlapipe

[dbnt10sv.apipe]

[dbnt10sv.ntnbi]

[dbnt10sv.ws32]

[dbnt5sv.comments]
;
; This section is for the 5-User SQLBase Win32 database server.
;
[dbnt5sv]
servername=server1,sqlapipe
dbname=island,sqlapipe
cache=2000
sortcache=2000

[dbnt5sv.gui]

[dbnt5sv.dll]
comdll=sqlapipe

[dbnt5sv.apipe]

[dbnt5sv.ntnbi]

[dbnt5sv.ws32]

[dbnt2sv.comments]
;
; This section is for the 2-User SQLBase Win32 database server.
;
[dbnt2sv]
servername=server1,sqlapipe
dbname=island,sqlapipe
cache=2000
sortcache=2000

[dbnt2sv.gui]

[dbnt2sv.dll]
comdll=sqlapipe

[dbnt2sv.apipe]

[dbnt2sv.ntnbi]

[dbnt2sv.ws32]

[dbnt1sv.comments]
;
; This section is for the 1-User SQLBase Win32 database server.
;
[dbnt1sv]
servername=server1,sqlapipe
dbname=monitor
password=sysadm
dbdir=c:\SQLBASE
cache=32000
sortcache=32000
readonly=0
logfileprealloc=0
partitions=1
optimizerlevel=2
locktimeout=275

[dbnt1sv.gui]

[dbnt1sv.dll]
comdll=sqlapipe

[dbnt1sv.apipe]

[dbnt1sv.ntnbi]

[dbnt1sv.ws32]

[dbnservr.comments]
;
; NetWare
;-------------
; This section is for the SQLBase NLM database server. This is a NetWare 3.x
; Loadable Module (NLM) and is loaded on the NetWare file server. You can
; specify which communication protocol(s) the server can use as well as which
; protocol(s) a database can use.
;
[dbnservr]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbnservr.dll]
comdll=sqlspx

[dbnservr.spx]
retry=20

[dbn50svr.comments]
;
; This section is for the SQLBase NLM database server (50-user version). This
; is a NetWare Loadable Module (NLM) and is loaded on the NetWare file server.
; You can specify which communication protocol(s) the server can use as well
; as which protocol(s) a database can use.
;
[dbn50svr]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbn50svr.dll]
comdll=sqlspx

[dbn50svr.spx]

[dbn25svr.comments]
;
; This section is for the SQLBase NLM database server (25-user version). This
; is a NetWare Loadable Module (NLM) and is loaded on the NetWare file server.
; You can specify which communication protocol(s) the server can use as well
; as which protocol(s) a database can use.
;
[dbn25svr]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbn25svr.dll]
comdll=sqlspx

[dbn25svr.spx]

[dbn10svr.comments]
;
; This section is for the SQLBase NLM database server (10-user version). This
; is a NetWare Loadable Module (NLM) and is loaded on the NetWare file server.
; You can specify which communication protocol(s) the server can use as well
; as which protocol(s) a database can use.
;
[dbn10svr]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbn10svr.dll]
comdll=sqlspx

[dbn10svr.spx]

[dbn5srvr.comments]
;
; This section is for the SQLBase NLM database server (5-user version). This
; is a NetWare Loadable Module (NLM) and is loaded on the NetWare file server.
; You can specify which communication protocol(s) the server can use as well
; as which protocol(s) a database can use.
;
[dbn5srvr]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbn5srvr.dll]
comdll=sqlspx

[dbn5srvr.spx]

[dbn2srvr.comments]
;
; This section is for the SQLBase NLM database server (2-user version). This
; is a NetWare Loadable Module (NLM) and is loaded on the NetWare file server.
; You can specify which communication protocol(s) the server can use as well
; as which protocol(s) a database can use.
;
[dbn2srvr]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbn2srvr.dll]
comdll=sqlspx

[dbn2srvr.spx]

[dbnwsrv.comments]
;
; This section is for the SQLBase NLM database server that runs on Netware 4.x
; This is a NetWare Loadable Module (NLM) and is loaded on the NetWare file
; server.
;
[dbnwsrv]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbnwsrv.dll]
comdll=sqlspx

[dbnwsrv.spx]

[dbnw50sv.comments]
;
; This section is for the SQLBase NLM database server (50-user version) that
; runs on Netware 4.x. This is a NetWare Loadable Module (NLM) and is
; loaded on the NetWare file server.
;
[dbnw50sv]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbnw50sv.dll]
comdll=sqlspx

[dbnw50sv.spx]

[dbnw25sv.comments]
;
; This section is for the SQLBase NLM database server (25-user version) that
; runs on Netware 4.x. This is a NetWare Loadable Module (NLM) and is
; loaded on the NetWare file server.
;
[dbnw25sv]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbnw25sv.dll]
comdll=sqlspx

[dbnw25sv.spx]

[dbnw10sv.comments]
;
; This section is for the SQLBase NLM database server (10-user version) that
; runs on Netware 4.x. This is a NetWare Loadable Module (NLM) and is
; loaded on the NetWare file server.
;
[dbnw10sv]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbnw10sv.dll]
comdll=sqlspx

[dbnw10sv.spx]

[dbnw5sv.comments]
;
; This section is for the SQLBase NLM database server (5-user version) that
; runs on Netware 4.x. This is a NetWare Loadable Module (NLM) and is
; loaded on the NetWare file server.
;
[dbnw5sv]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbnw5sv.dll]
comdll=sqlspx

[dbnw5sv.spx]

[dbnw2sv.comments]
;
; This section is for the SQLBase NLM database server (2-user version) that
; runs on Netware 4.x. This is a NetWare Loadable Module (NLM) and is
; loaded on the NetWare file server.
;
[dbnw2sv]
servername=server1,sqlspx
dbname=island,sqlspx
cache=2000
sortcache=2000
dbdir=db:\sqlbase

[dbnw2sv.dll]
comdll=sqlspx

[dbnw2sv.spx]

[client.comments]
;-----------------------------------------------------------------------
; SECTION: Client workstation sections (Windows, Win32, NetWare).
;-----------------------------------------------------------------------
[winclient.comments]
;
; Windows
;-------------
; Use this section to specify Windows client workstation parameters that are
; independent of the communications protocol(s) being used.
;
; This section is for the Windows client workstations. Here you will specify
; the COMmunication DLL(s) that the Windows application(s) intend to use.
; Use the following protocol(s) to connect to the specified SQLBase product:
;
; comdll SQLBase target
; ------ --------------
; sqldbw LOCAL single-user database engine (dbwindow.exe)
; sqlwsv LOCAL multi-tasking database engine (dbwservr.exe)
; sqlnbiow REMOTE database using NetBios
; sqlspxw4 REMOTE database on a Netware server
; sqlwsock REMOTE database using TCP/IP (WinSock)
;
[winclient]
clientname=WinUser

[winclient.dll]
comdll=sqlwsv

[winclient.nbiow]

[winclient.spxw4]

[winclient.wsock]

[win32client.comments]
;
; Win32 (Windows 95 or NT)
;--------------------------
; Use this section to specify Win32 client workstation parameters that
; are independent of the communications protocol(s) being used.
;
; This section is for the Win32 client workstations. Here you will specify
; the COMmunication DLL(s) that the Win32 application(s) intend to use.
; Use the following protocol(s) to connect to the specified SQLBase product:
;
; comdll SQLBase target
; ------ --------------
; sqlapipe LOCAL database using Anonymous Pipes
; sqlntnbi REMOTE database using NetBios
; sqlws32 REMOTE database using TCP/IP (WinSock)
; sqlspx32 REMOTE database using IPX/SPX (Win32 Novell Client)
; sqlwsspx REMOTE database using IPX/SPX (Win32 Microsoft Client)
;
[win32client]
clientname=Shop2x

[win32client.dll]
comdll=sqlws32

[win32client.apipe]

[win32client.ntnbi]

[win32client.ws32]
serverpath=server5,10.0.1.13/vmfg,pilot

[win32client.spx32]

[win32client.wsspx]

[nwclient.comments]
; Netware clients
;-------------------
; Add this to the sql.ini for netware clients for SQLAPI for Netware and 2pc.
; Use this section to specify Netware client workstation parameters that
; are independent of the communications protocol(s) being used.
;
[nwclient]
clientname=NWUser

[nwclient.dll]
comdll=sqlspx

[nwclient.spx]

[patch.comments]
;
; This section is only used if running the NLM Database Server on a
; NETFRAME machine.
;
[patch]

Can anyone offer some help as to why this is happening? I would be VERY greatful.
 
I have the SQL Console installed and can connect to the Database(s) that reside on the network server. Can view statistics, active sessions, cursor info, etc.

Has anyone here ever partitioned a database with this tool?

Can anyone give me some pointers as to what to watch out for?

Thank you in advance for your help.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top