Showing posts with label remotely. Show all posts
Showing posts with label remotely. Show all posts

Sunday, February 19, 2012

accessing the database remotely from non-microsoft platform

I have a query of the kind brains of this group.

Is it possible to access a microsoft sqlserver database (for select, insert,
update, delete, and for miscellaneous administrative actions such as table
and index creation and deletion) remotely from a compiled C program (and/or,
from Perl) running on a NON microsoft platform, such as Sun's Solaris and/or
Linux?

What toolset(s) could be used (on the UNIX/Linux end) for such a purpose?
Would it require a corresponding special toolset to be installed on the
Windows server end as well? (I'd prefer not to have to do that if
possible.)

If you are not now rolling on the floor laughing at the "heresy" of such a
notion, thanks in advance.

Dan
drlevy@.glowing.com (replace 'glowing' with 'lucent')Some suggestions here:

http://www.sommarskog.se/mssqlperl/unix.html

Simon

Thursday, February 16, 2012

Accessing SQL Server remotely

Dear All,

I have created a database on my SQL server, I want to access my database through C# .NET project . By just installing the software on the client side I would be able to access my SQL server remotely.

On internet can i Do that?

Plz let me know any solution for this.

Regards,

Anil Dhiman

DId I understand you right that you want to connect through the internet to your SQL Server ? Then you have to redirect/forward port 1433 of the connected internet gateway to the SQL Server that you have within your infrastructure.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

Hi Anil,

Also keep in mind that your server is a named instance, then it may not necessarily be using port 1433. I this case, you may need to make sure that SQL Browser is started and UDP port 1434 is opened on the firewall in addition to the instance port. These KB articles may be of some assistance for configuring the firewall:

http://support.microsoft.com/kb/287932/en-us
http://support.microsoft.com/kb/841249/en-us

Alternatively, the client's connection string can explicitly contain the connection port in which case, you don't need SQL Browser.

Il-Sung./

Sunday, February 12, 2012

Accessing Remotely located SQL Server via Access

Hi,

I need the code to create a connection between the Sql server using ACCESS form.

Can I do this. If yes . can you help mw with it.

Currently I am accessing the server with remote desktop connection

Regards,

Jay

There is a fairly useful resource for this process in Access help under "Import or link SQL database tables or data from other ODBC data sources". Just search for that string in Access help, and there will be a whole bunch of information on this topic. Hopefully, this will provide you with all you need to connect to SQL server.

Hope this helps!

John (MSFT)

|||

There is a fairly useful resource for this process in Access help under "Import or link SQL database tables or data from other ODBC data sources". Just search for that string in Access help, and there will be a whole bunch of information on this topic. Hopefully, this will provide you with all you need to connect to SQL server.

Hope this helps!

John (MSFT)

|||

Open the destination database (access database which you want linked to SQL Server)
On the External Data tab, in the Import group, click More.
Click ODBC Database.
Click Link to the data source by creating a linked table, and then click OK.

Click New to create a new data source name (DSN).
The Create New Data Source Wizard starts.

In the wizard, select SQL Server in the list of drivers, and then click Next.

Click Next, review the summary information, and then click Finish to complete the Create New Data Source Wizard.
The Create a New Data Source to SQL Server Wizard starts.

In the wizard, type a description of the data source in the Description box. This step is optional.
Under Which SQL Server do you want to connect to, in the Server box, type or select the name of the SQL Server computer to which you want to connect, and then click Next to continue.
On this page of the wizard, you might need to get information from the SQL Server database administrator, such as whether to use Windows NT authentication or SQL Server authentication. Click Next to continue.
On the next page of the wizard, you might need to get more information from the SQL Server database administrator. If you want to connect to a specific database, ensure that the Change the default database to check box is selected, select the SQL Server database that you want to work with, and then click Next.
Click Finish. Review the summary information, and then click Test Data Source.
Review the test results, and then click OK to close the SQL Server ODBC Data Source Test dialog box.
If the test was successful, click OK again to complete the wizard, or click Cancel to return to the wizard and make changes to your settings.


Click OK.
Access displays the Link Tables dialog box.

Under Tables, click each table or view that you want to link to, and then click OK.

Regards,

Designing-Systems.com

Thursday, February 9, 2012

Accessing named instance remotely

I've got an instance of SQL server running on my website. I have port
1433 open and I can connect to it via enterprise manager across the
internet just by using the domain name in the server name box.
I recently installed SQL 2K5 beta 2 on the same box and gave it a
different name. I should be able to connect to it using
domainname\instancename correct? For some reason I can't connect to
it. I guess I don't know whether this is something particular to 2K5
or not, or do I need to do something specific for any named instance?
That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegr oups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>
|||You will have to specify a PORT NUMBER unless you also have UDP PORT 1434
opened on your firewall.
If you also have dynamic defined, which would not be recommended in your
configuration, you may have to open up several inbound ports to cover those
that SQL Server may use.
You would be better off blocking inbound UDP 1434, configuring your named
instance to use a specific port, say 1533, and then also open up inbound TCP
1533.
Out of curiosity, why would you expose a SQL Server installation to the
public network?
Sincerely,
Anthony Thomas

"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23AZc8EZ$EHA.2568@.TK2MSFTNGP10.phx.gbl...
That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegr oups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>

Accessing named instance remotely

I've got an instance of SQL server running on my website. I have port
1433 open and I can connect to it via enterprise manager across the
internet just by using the domain name in the server name box.
I recently installed SQL 2K5 beta 2 on the same box and gave it a
different name. I should be able to connect to it using
domainname\instancename correct? For some reason I can't connect to
it. I guess I don't know whether this is something particular to 2K5
or not, or do I need to do something specific for any named instance?That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
--
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegroups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>|||You will have to specify a PORT NUMBER unless you also have UDP PORT 1434
opened on your firewall.
If you also have dynamic defined, which would not be recommended in your
configuration, you may have to open up several inbound ports to cover those
that SQL Server may use.
You would be better off blocking inbound UDP 1434, configuring your named
instance to use a specific port, say 1533, and then also open up inbound TCP
1533.
Out of curiosity, why would you expose a SQL Server installation to the
public network?
Sincerely,
Anthony Thomas
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23AZc8EZ$EHA.2568@.TK2MSFTNGP10.phx.gbl...
That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
--
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegroups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>

Accessing named instance remotely

I've got an instance of SQL server running on my website. I have port
1433 open and I can connect to it via enterprise manager across the
internet just by using the domain name in the server name box.
I recently installed SQL 2K5 beta 2 on the same box and gave it a
different name. I should be able to connect to it using
domainname\instancename correct? For some reason I can't connect to
it. I guess I don't know whether this is something particular to 2K5
or not, or do I need to do something specific for any named instance?That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegroups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>|||You will have to specify a PORT NUMBER unless you also have UDP PORT 1434
opened on your firewall.
If you also have dynamic defined, which would not be recommended in your
configuration, you may have to open up several inbound ports to cover those
that SQL Server may use.
You would be better off blocking inbound UDP 1434, configuring your named
instance to use a specific port, say 1533, and then also open up inbound TCP
1533.
Out of curiosity, why would you expose a SQL Server installation to the
public network?
Sincerely,
Anthony Thomas
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:%23AZc8EZ$EHA.2568@.TK2MSFTNGP10.phx.gbl...
That should be enough, assuming you have TCP/IP enabled. If nothing in
http://www.aspfaq.com/sql2005/show.asp?id=3 helps, please post to the SQL
Server 2005 newsgroups. (See http://www.aspfaq.com/sql2005/show.asp?id=1)
http://www.aspfaq.com/
(Reverse address to reply.)
<erithtotl@.gmail.com> wrote in message
news:1106075082.815158.287290@.z14g2000cwz.googlegroups.com...
> I've got an instance of SQL server running on my website. I have port
> 1433 open and I can connect to it via enterprise manager across the
> internet just by using the domain name in the server name box.
> I recently installed SQL 2K5 beta 2 on the same box and gave it a
> different name. I should be able to connect to it using
> domainname\instancename correct? For some reason I can't connect to
> it. I guess I don't know whether this is something particular to 2K5
> or not, or do I need to do something specific for any named instance?
>