Must migrate back end from sybase to sql server - INI file changes?

[billdvldog]

Looking for some help from the PB gurus out there! Unfortunately I have to migrate a back end database from Sybase to SQL Server. I've figured out how to migrate the data, procedures, etc, so that part is done.

I have never dealt with PB before, but we have an old PB 6.5 application and I'd like to know what changes need to be made to the INI file to direct it to the new SQL Server back end. Here is how the INI file currently looks:

[Database]
DBMS=SYC Sybase System 10
Database=dbname
ServerName=svrname
Lock=
DbParm=appname=host=
Prompt=1
AutoCommit=false

The svrname references a section of the Sybase SQL.INI file. Any help would be greatly appreciated, as our old Sybase server on DEC Unix is not holding up well.

Thanks in advance,

Bill

 

[mbalent]

What version of SQL Server?

Matt

"Nature forges everything on the anvil of time

 

[billdvldog]

Sorry, SQL Server 2000.

 

[mbalent]

We use the OLE DB drivers to connect to our database as well and integraged security. Our connection syntax is:

SQLCA.DBMS = "OLE DB"
SQLCA.AutoCommit = False
SQLCA.DBParm = "PROVIDERSTRING='database=mydb;Trusted_Connection=Yes',PROVIDER='SQLOLEDB',DATASOURCE='myserver'"

Matt


"Nature forges everything on the anvil of time

 

[billdvldog]

Thanks Matt, I tried those changes, but it doesn't look like it's connecting. I think I'm going to have to tell them they will need to get a PB expert to come in. I'd like to learn PB, but I just don't have the spare time right now! Thanks for your help, I really appreciate it!

 

[cucho]

Try this

SQLCA.DBMS = "MSS Microsoft SQL Server 6.x"
SQLCA.AutoCommit = False
SQLCA.DBParm = ""

 

[billdvldog]

Should I use the same DBParm parameters from Matt's post?

Thanks,

Bill

 

[cucho]

I use this in the .ini file
Vendors=MICOSOFT
DBMS=MSS Microsoft SQL Server 6.x
ServerName='servername'
Database='dbname'
DBParm=AppName='',Log = 0, host='computername',DBTextLimit='32000'

If you need help my mail is pcucho@yahoo.com

 

[billdvldog]

Thanks cucho, but that didn't seem to work either. I keep getting a "Logon Failed. Please try again!" error message. I think that is a custom error though, and it comes up right away - there is no delay like it's trying to connect.

 

[cucho]

Did try to start SQL Profiler to debug the SQL Server session?
It could help you a lot.

 

[billdvldog]

Thanks cucho, I'll give it a try!