I have an application that uses SQL Server Express Edition. Unfortunately it can connect only to local instance. The problem is I have a remote instance bought from one of internet providers.
The question is, id there any possibility to make some kind of "local alias" for remote database? Maybe I can install another instance locally and perform some kind of mirror or replication (I can only install Express Edition as I have no funds for any other version)?
I'd like to push this question as I am looking for the exact same thing. I have Microsoft Business Contact Manager installed and it only allows me to connect to local (local network) SQL Express instances... however I do have a SQL 2008 database instance available from an internet hosting service. Is there a tool/solution which would create some kind of a local node so BCM would see it as a local instance but the communcation would happen "in the background" with the remote database?
Related
I developed an app with vb.net to update a SQL Server database.
The app is connected with SQL Server in my computer and seems working very well.
But my target is to put this database in the common mass storage to be updated with this app from 20 people (20 client PC).
My questions are:
how to do to install the database in the common mass storage?
should the SQL Server Express be installed in the 20 client computers?
how to connect the app to the database (located in the common server) using ADO.net?
Thanks in advance
It really depends. If everybody is suppose to use the same data I would look at putting up a sql server that everyone can access on the network. If the data needs to be used from computers outside of a local network I would look at getting a database from a web host. For these instances you would have to update the server to your connection string to the url of the new sql server. If everyone is using there own data it is ok to use there own sql express instance.
I am a system administrator for a small firm. Now we consider to rollout Windows Server 2008 R2 for the firm.
We plan to implement Active Directory.
We would also like to upgrade RDMS, from SQL server 2000 to SQL Server 2014.
We can afford to buy just one server due to size of our organization, so we plan to implement both of AD and SQL Server 2014 on the same machine.
However, Microsoft recommends not to install SQL Server 2014 on a domain controller.
I have checked the reasons, but I don't understand what is the problem, so if someone answers my questions bellow, it's really helpful.
(1)You cannot run SQL Server services on a domain controller under a local service account.
→If we run SQL Server on a domain controller under a domain user account, what would happens?
(2)After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller.
You must uninstall SQL Server before you change the host computer to a domain controller.
→We plan to promote our server to a domain controller before installing SQL server 2014 and don't plan to de-promote to
member server because it's our only server. Is our plan wrong?
(3)After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member.
You must uninstall SQL Server before you change the host computer to a domain member.
→We don't plan to de-promote to member server because it's our only server. Is our plan wrong?
(4)SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
→We don't plan to install failover cluster, so we think that it's not problem. Are we wrong?
(5)SQL Server Setup cannot create security groups or provision SQL Server service accounts
on a read-only domain controller. In this scenario, Setup will fail.
→Because We have just one server, so it never be a read-only domain controller, so we think that it's not problem. Are we wrong?
Actually, I guess if we clear (1), we can install SQL server 2014 on our domain controller.
Thanks for reading all of sentences.
I hope someone give us answers.
Warmest Regards,
Yoshiaki Fujita, Tokyo, Japan
I'm newbie for Amazon EC2.
I'm given an assignment where I've to connect VS 2008 to Sql Express 2005.
VS and Sql Express are running on separate Amazon machine.
(I mean, I've to do 2 separate Remote Desktop Connection to access both).
I've no clue how to connect to the Sql Express.
I've been trying different options found in search on google, stackoverflow etc...
But no luck.
Any help is appreciated.
Assuming that you have a connection string (to server ec-xxxxxxx.xxx.amazon.com), your problem could be that the .Net instance (let's call it NET) and the SQL Server instance (SQL) don't have the rights to see each other.
Create two instances with the different security groups
On both groups, you'll like want to open RDP (you probably have that already as I can read)
On the SQL instance security group create an inbound rule for port 1433 and open it only for the security group of WEB. Otherwise, the whole world can access your SQL Server Express database. Like this, only the WEB instance can access it. You need to paste the security group id of WEB into the inbound rule for SQL to do that.
Good luck.
I want to access SQL server via an application (it is a desktop application) which is installed on remote location, where as SQL server installed in Main Office, where other applications are also accessing same SQL server on LAN.
Is it possible to do it?
Yes, technically this is not problem. Once installed, SQL Server will react both on the internal IP and external - if the Firewall is configured to forward SQL-Server Traffic (TCP 1433).
BUT - from security point it's not a good idea to expose your SQL Server directly to the internet. In the past there have been several security problems that would have exposed more than you wanted to expose. I would suggest external users, not inside your LAN use a VPN Connection to get inside your internal Network. I work every day over VPN with SQL Server and it's stable and secure.
How do I connect to an SQL Server remotely and administer my database objects? I need to connect to my database located on the web hosting company's server. I have the server name, IP address, my database username & password. I have an installation of SQL Server 2000 in my machine.
Can I use SQL Server Enterprise Manager for this? A step by step guide would be very helpful.
Yes, you can use Enterprise Manager (or SQL Server Management Studio, even if it's an Express version) to connect to any SQL Server (of the same or lower version as the tool you're using) you have TCP/IP connectivity to. Just launch it, enter the DNS host name or IP address in the 'Server Name' box and hit Connect.
Two things may prevent this from working:
Your SQL Server isn't set up for TCP/IP connectivity. This is the default setting from version 2005 onwards, and can be changed using the SQL Server Configuration Manager.
There is a firewall between you and your SQL Server blocking TCP/IP traffic. This is an entirely sensible construction: you do NOT want your database server to be available from the general Internet, as this is a huge security risk. In fact, if your hosting company allows this kind of access by default, I'd be looking for a different provider...
Anyway, what seems to be needed in your scenario is: a) the hosting company enabling TCP/IP on your SQL Server instance, b) them providing you with secure access to the IP address that instance is running on.
This will involve some kind of VPN or SSH port-forwarding soluition, or at least an IP filter, where only 'trusted' IP addresses can access the SQL Server (which is not a great solution, but can be used if nothing else can be implemented). You'll have to discuss these requirements with your hosting company.
Yes you can do this but how you do this will be dependent on your hosting setup.
As Brannon suggests you will need to open port 1433 on the firewall. This would be a dangerous thing to do on its own so you would combine it with a VPN. It can be quite tricky to set this up through and you could end up blocking yourself from access to the server and needing the hosting companies help to reset it.
Another option would be some of the web management tools such as:
http://www.microsoft.com/downloads/details.aspx?familyid=C039A798-C57A-419E-ACBC-2A332CB7F959&displaylang=en
http://www.mylittleadmin.com/en/welcome.aspx
It is possible, but a lot of things need to align for you to be able to connect.
Enterprise Manager and SQL Management Studio just use a standard client connection to SQL. The default TCP/IP port is 1433, but the host needs to allow that port through the firewall. If you are using a named instance, then I believe you also need to be able to connect to port 1434.
Most administrators do not allow direct access to the SQL Server from outside the firewall. In that case, if you can connect to the host over VPN then you should be able to connect directly to the server with Enterprise Manager or SQL Management Studio.