Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Including port 1433 to the conn string?
Message
General information
Forum:
Microsoft SQL Server
Category:
Other
Environment versions
SQL Server:
SQL Server 2008
Miscellaneous
Thread ID:
01564928
Message ID:
01564944
Views:
33
My VFP 9 application connection string is using a slightly different syntax:

SERVER=SERVERNAME\SQLEXPRESS

Does it matter that my syntax is using "SERVER" and your example is "ADDRESS"? And that I use the Server name and not IP? My syntax works on many other customers' databases (the same application).

My main question was if by creating System DSN he made any difference and it helped. Or he thinks it made the difference. Right now the connection works but I would like to understand what made the difference between not working and started to work.

Thank you.

>>I agree and it works. But the customer tells me is that it started working only after he did the following two things:
>>1. In SQL Server Configuration protocols for SQLServer he Enabled Named Pipes (it was Disabled by default)
>>2. He also set up System DSN on the application server (where app resides) and unchecked the "dynamically determine port".
>>
>
>Your customer needs to get someone with SQL Server experience to make sure he is set up properly.
>
>TCP-IP is the protocol that should be in use, and the default port is 1433. If the SQL server is running as a named instance (like SQLEXPRESS), then your connectionstring will need to refer to the named instance..
>
>ADDRESS=175.33.33.09/SQLEXPRESS
>
>>I don't understand how the no 2 above made the difference in my application connecting to the SQL DSN-less.
>>
>>>1433 is default SQL Server port. Your application should work as is.
>>>
>>>>
>>>>The client informed me that in order for my VFP application to connect to the SQL Server it has to be done via DSN with the option "dynamically determine port" to be unchecked since the SQL server is listening on static port 1433. My VFP 9 application connects to the SQL Server via DSN-less ODBC connection. My question, if I include the SQL Server IP and the port in the connection string, should it work just like it would with DSN? For example, if I include in the connection string the following:
>>>>
>>>>"ADDRESS=175.33.33.09,1433"
>>>>
>>>>should it work? TIA.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Previous
Reply
Map
View

Click here to load this message in the networking platform