I am a VB6 programmer and I'm really new to SQL Express, I have always used ACCESS because it was so easy to deploy. I've now written a VB6 program which uses SQL Express and I want to know how to deploy it. Basically my PC will host the SQL database as it has SQL Express loaded onto it. I now want to install my EXE onto other Client's PC and have them read/write to the database on my machine.
Besides the EXE program, what software do I need to load onto the Client's PC so they can access my SQLExpress database...? (eg: Net Framework, SQLExpress, etc).
Also, if my machine is called ABC123, in my connectionstring do I just put in
ABC123sqlexpress as the datasource..?. Will this be enough for the other PCs to connect to mine ?
I have written a VB program using an SQLExpress database on my machine, and I want other users to remotely access it. From what I have read, all I have to do for the Client machines is load on SQL Native Client and install the EXE. I have also enabled TCI/IP etc and setup the exceptions on my firewall. My connectionstring is
When I run the EXE on the client machine, I get the following error...
Cannot open database <mydata> requested by the login. The login failed.
I am totally new to SQL and would appreciate any help in getting this setup. Do I need to put my login details into the connection string so other PCs can log into my database..?
ACCESS was never this hard to deploy, but I really want to learn SQL.
- When I disable "allow remote connections to this server" from server properties>connection page, I can still remotely connect to the server from SSMS...so what is the impact of enable/disabling it?
- what is the impact of changing the remote query timeout (on the same page) from default value?
I have a database on my computer with a series of tables in it. I have sql server management studio express 2005 handling them. How would I make it so I can access the database remotely, over the internet (a non-local network)
Hi,I am having a hard time setting up an SQL Server 2000 DeveloperEdition instance for remote clients. The instance is running well andI can connect to it on the local computer. When I try connecting fromanother computer using Enterprise Manager with the server's IP as theinstance name, I always get the usual "Specified SQL Server not found"error. I have used Enterprise Manager many times to connect to localand remote servers (which were set up by someone else obviously).I used the client network utility on the client to make an alias forthis server and have it use the TCP/IP library for port 1433.I understand that SQL Server listens on port 1433 for connections. Ihave a firewall on the server and setup 1433 forwarding. But when Iuse Enterprise Manager to try to register the server, the firewalldoesn't even show a connection attempt on port 1433 (it logs allconnection attempts).When I use telnet to port 1433, the firewall logs the attempt butthere is still no connection, as if the server isn't actuallylistening on 1433 at all. I can't seem to find any help on getting theserver listening, as if it supposed to be easy to set up so I don'tknow what I'm missing. I guess I have the following questions:1) Does anything have to be done on the server side to set it up tolisten for remote client connections?2) How do I set the port on which the server listens in case I want tochange from 1433?3) Does anything have to be set up on the client side other than usingthe client network utility?4) Why does Enterprise Manager not seem to even attempt a connectionon port 1433 when I try to register this server?Any help is appreciated.
Hello, I know that this has been asked several times, but none of the answers that I've found seem to help me. I've been programming a C# client app that helps netadmins at my school file and solve tickets. I use an SQL 2005 backend; it works just fine on my dev computer (with C# express installed) which doubles as the SQL server. Now, when I move to a different computer, w/o Visual C# or SQL installed, I get. "Request for the permission of type 'System.Data.SqlClientPermission, System.Data, Version=2.0.0.0,Culture=neutral,PublicKeyToken=(RANDOMVALUE)' failed."
I have a SQL Server 2014 installation on a server (CHRIS-PCCHRISSQL).I have SQL Server 2014 management studio installed on local server called Pootle.I have gone through the configuration on server (CHRIS-PCCHRISSQL) inc the following:
(1) I have set up a user on CHRIS-PCCHRISSQL called sqladminuser at server level with the Server Roles of 'Public' and 'SysAdmin'
(2) The computers are both on the same homegroup.
(3) On Chris-PC , I have opened up the firewall port 1433 as Inbound Rule
(4) On Chris-PC, Within SQL Server Configuration Manager,the 'SQL Server Network Configuration for Protocols for CHRISSQL' have been set up as follows:
- The TCP protocol is enabled - I have set up IP2 as follows:
Active: Yes Enabled: No IP Addres: 192.168.0.3
However when I try to connect from SQL Server Management Studio 2014 on my local machine Pootle to Chris-PCCHRISSQL using SQL Server Authentication with the user sqladminuser
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)how to set up a remote connection from SQL Server Management Studio on my local machine Pootle to CHRIS-PCCHRISSQL
I have written a VB component to execute a SSIS package stored in SQL server.
I am using the Microsoft.sqlserver.dts.dtsclient, dtsconnection/dtscommand
and executereader and everything works perfect on the local machine. This is descibed in a msdn site .
But my customer have a remote SQL server and want no extra BI clients/SQL server clients etc on the client machine, only an ordinary windows client and network connection to the SQL server.
My question is: Can you still use dtsclient or do you have to do in some other way?
I want to give a client access to a SQL Server 7 database sitting on a different NT domain without setting up a trust relationship between the two domains. Has anyone tried doing this?
The reason I want to put an ip address on connection string i just want to create connection strings as people do in their work. When the app tried access the connection string it gives the error in the attachment.
Because I haven't used this user/password for a long time I'm pretty sure the user name and password is correct but i have the following questions
1. Assume the user and password is incorrect, is there way to reset this? 2. what other configuration that i need to do in order to make teh C# app access this Database?
If I give the user access dbo on 1 of the database, when he logon using SQL Server Management Studio for running query etc, can he only see his database instead of other as well system database?
Is there any best practise in term of setting the SQL client for 2005?
Please advise which kind of connection should be establish from excel 95 to MS SQL Server.
From my thought, I understand that the connection depends on Windows version rather than excel version. Thus, I just think that there will not be any issue connecting to SQL Server from Excel 5.0a.
Kindly advise if there is any addtional point to concern/consider further. What could be issue connecting to SQL Server 2005 from Excel 5.0a.
I've installed SQL 2005 Express, enabled local and Remote connections but my client app cannot connect to the SQL server. I'm getting access denied or SQL does not exists. Any idea's on how to resolve this issue?
I have a quick question regarding domains and workgroups.
Currently I am working on an issue in the office of a small business. Right now there are 3 client computers that connect to a dell server running windows std. server 2003. The server has sql running on it that takes care of the invoicing system. Two out of the three work stations are able to use the database fine, but there is one that is unable to connect to the database. The only different that I could find is that the two workstations that DO work are currently set to use a workgroup, whereas the one workstation that does NOT work is set to use a domain...... I tried switching that computer to workgroup, but then I was unable to login as the normal user that I had always logged in as before.....
What can I do to solve this dilemma?
Any help would be greatly appreciated!
I apologize if this is the wrong forum for this, and if it is, if someone would point me to the correct one I would appreciate it.
Hi, I have a server (WIN 2000 server), is connected with many clients mostly having Win 2000 Professional OS. My application is developed in VB 6.0 and we have MS SQL Server 2000 DB in our server. All the clients with win 2000 professional have no problem with connecting and accessing my SQL Database. But few of my WIN XP clients don€™t connect to database thru my application. It gives error as follows.
Runtime error Login Failed for user €˜(null)€™ . Reason: Not associated with a trusted SQL Connection.
I have a requirement to set up an Oracle linked server, Ive never done this before and in fact never touched Oracle so I dont really know what I am doing.
So in a previous thread I discovered that in order to actually subscribe to any publication, the publisher needs to be a well-known network name, requiring DNS resolution. You can't simply point a SQLExpress instance at an ip addressinstance and have it resolve the communications.
Hi guys,I'm not sure if I'm just bad at googling but I can't seem to find a way to set an ASP.NET 2.0 web application to connect to SQL Server 2005 using the current client's user credentials. My web application is using Integrated Windows Authentication so its Page.User.Identity is set to a DOMAINusername value... I want to pass that to my connectionstring or have my connections pick up the identity automatically and use that Identity when accessing the db server.Oh and another thing, my IIS Application Pool is using a specific Identity itself, so I don't know if that might affect the above.Hope someone could help.
I'm using SQL Server to store session state. The Sql Server is on the local network but not on the web server. I use impersonation and use account credentials for the ASPNET worker process:
I've checked and given the user i'm impersonating the ability to do everything. I've granted access on all necessary files, added them to the DB and made the user a db_owner of the ASPState table. I can log in to a machine as the user, then access sql server using the windows authentication. I granted 'act as part of the operating system', 'access this computer from a network', 'log on as a service', 'log on as a batch job' on both the remote computer hosting sql server and the web server.
The strange thing is i installed the asp session state tables on my development machine, using the same configuration file to run everything, and was able to add an object to session state without any problem. But when i specify the remote server, i'm denied.
i use that to connect to the remote SQL server, which has status of port 1433 at "Stealth"... do i need to open the port complete, if yes how i do that ?
I want to access the other server from my Enterprise Manager by using <server_name>.<db_name>.<tab_name>.<procedure>/table_name.
Pls. let me know the steps I have to take I have added two remote logins in both the server. I also gave trusted right by using sp_remoteoption procedure and still I get the message 'the object <server_name> not accessible>
Please reply at the earliest, as I am right noe accessing the other servers data by bcp-out and bcpin into this server.............
I am trying to access SQL server remotely (over the internet). I would like to use query analyser as my front end tool. Can anyone point out the procedure to do the same. I have the IP address and the host string.
My ISP provide MS SQL Server. I can create my database name, dbusername and dbpassword through control panel and then I can access the database in ASP using this connection string "Provider=SQLOLEDB;UID=dbusername; PWD=dbpasword".
Before, I could also use my enterprise manager to create a new sql server registration using my web url, dbusername and dbpassword. But now it seems that my ISP blocks the port or something and ask me do everything through the control panel.
Does anyone have some idea to connect to a remote server thorough enterprise manager based on the infromation I have?
Does anyone know of a good place to find instructions on how to set up remote access to my SQL Server. I have been unsuccessful finding anything on this topic.
I'm writing a piece of software that is designed to access data from SQL server. The office's server has SQL server version 7 installed. The software works perfectly when running on a computer on the network in the office. I however am trying to work out how to use use the software from my home computer and connect to the SQL server database remotely. I've never done this before and I'm finding it hard to find the right information.
Firstly, is it easy to do this? What do I need to do with the server in the office to allow this to work? Do I need any extra hardware/software? How will my software connect to SQL server? Is it as simple as changing the connection string to something like the server's ip address and sql server name?
I'm writing the software in Visual Studio 2005 professional and programming in VB.
I'm using the SQL Native Client to connect my VB6 application to my SQL Server 2005 database. My SQL Server 2005 database has ANSI_NULLS turned off. I have a query embedded in my VB6 application that uses the syntax "fieldName = NULL" in the WHERE clause. When I execute the query via the SQL Native Client, the query returns zero rows. When I execute the same query via the old OLEDB driver, the query returns many rows. If I change my query to "fieldName IS NULL" syntax, the problem goes away. However, I am more interested in figuring out why ANSI_NULLS are turned on when using the SQL Native Client even though my database has them turned off. Is there a connection string property that I can use with the SQL Native Client to ensure that the query is executed with ANSI_NULLS off?
I am trying to read the databases attached to the Sql Server 2005.... my code works fine for Sql Server 2000 but when i try it with Sql Server 2005 it gives me error that "Under Current Settings SQL Server 2005 does not allow remote connections".
Can anybody tell me where to change these settings... i tried my best to find it but :(....
If possible to connect our remote server from my end ?.what r the possiblities is there.tell me some ideas,i already tried it to register our remote server database thru ODBC but it not connected properly but i ve tried in our intranet/network it's working fine.
I was just trying out Microsoft SQL Server 2000. I created a sample application which reads in 2 values from a textbox and writes it into a databse. This application works fine on my computer and the values are written to the database (In the connection string, I give my IP address as the datasource so that anyone on the internet can hit this database). However, when I copy this application to another computer and try to run it, it gives me an error "SQL Server does not exist or access is denied." I know this is a minor problem with some setting, but I haven't been able to find the solution on the internet. Can someone whose worked with Microsoft SQL Server 2000 please help me out.
