I'm developing a VB app to manipulate data in a table. I've created an SQL server (local) and have successfully connected to and manipulated data in a database that I created. I would like to be able to run the app on another machine and connect to the same server. I'm having trouble determining what the server name is. Tried a few things but get the "server does not exist" message. Server is set to authenticate SQL server and windows.
Is this happening because my server is (local)? If so how do I change it to permit remote access?
Any assistance would be appreciated.if you have only one sql server in that box, than the default name of the sql server is the name of the windows box. when you try to connect from another box, make sure that the client box has sql server drivers, create a DSN that point to the SQL Server box (using windows server name or ip address), every thing should go fine from there.|||C-Nag
Thanks! I thought there was a simple solution. I'm more familiear with MSAccess and should of thought of this. With access it would require the same.sql
Showing posts with label connected. Show all posts
Showing posts with label connected. Show all posts
Friday, March 23, 2012
Wednesday, March 7, 2012
Remote DB - best practices?
We have an application requirement that calls for a local running Windows
Froms application that will need to be connected to a central database over
the internet. Data volumes will be small but latency is a concern. My
first thought is to simply have a connectionstring to the remote db.
Another thought is to connect via web services. I'm thinking that WCF or
Remoting would be too much work.
Anyway, what is the best way? From a development standpoint? From an
operational durability standpoint?
Thanks,
TI think querying your databases using stored procedures via web services is
a good and secure way.
--
Ekrem Önsoy
"Tina" <TinaMSeaburn@.nospamexcite.com> wrote in message
news:exL3RCRBIHA.4836@.TK2MSFTNGP06.phx.gbl...
> We have an application requirement that calls for a local running Windows
> Froms application that will need to be connected to a central database
> over the internet. Data volumes will be small but latency is a concern.
> My first thought is to simply have a connectionstring to the remote db.
> Another thought is to connect via web services. I'm thinking that WCF or
> Remoting would be too much work.
> Anyway, what is the best way? From a development standpoint? From an
> operational durability standpoint?
> Thanks,
> T
>
Froms application that will need to be connected to a central database over
the internet. Data volumes will be small but latency is a concern. My
first thought is to simply have a connectionstring to the remote db.
Another thought is to connect via web services. I'm thinking that WCF or
Remoting would be too much work.
Anyway, what is the best way? From a development standpoint? From an
operational durability standpoint?
Thanks,
TI think querying your databases using stored procedures via web services is
a good and secure way.
--
Ekrem Önsoy
"Tina" <TinaMSeaburn@.nospamexcite.com> wrote in message
news:exL3RCRBIHA.4836@.TK2MSFTNGP06.phx.gbl...
> We have an application requirement that calls for a local running Windows
> Froms application that will need to be connected to a central database
> over the internet. Data volumes will be small but latency is a concern.
> My first thought is to simply have a connectionstring to the remote db.
> Another thought is to connect via web services. I'm thinking that WCF or
> Remoting would be too much work.
> Anyway, what is the best way? From a development standpoint? From an
> operational durability standpoint?
> Thanks,
> T
>
Subscribe to:
Posts (Atom)