I have had to format my laptop and re-install server 2005 developer edition. Im having trouble logging on. My computer name is 28NEWMANSLANE. I installed sql server with a default instance, where as last time i installed with a named instance.
I can not find out with name it has given itself.
am i correct saying that the logging in format would be
computername/instancename ?? using windows authentication
Regards
Rob
Hi,
I have two SQL SERVER Instances on the computer I am trying to connect to via VPN:
1) TEST
2. TEST/INST2
I can connect to the first with no problems.
When I am trying to connect to the second (with the Enterprise Manager/Query Analyzer and even with isql) - I get the following message:
"SQL SERVER does not exists or access denied".
I use the SQL SERVER user and password to connect (as login sa).
How can I connect to the second instance?
Thanks in advance.
Hi,
How can i connect to Named Instance of MSDE on remote server from Enterprice Manager in my local computer ?
Instance name is Helm
I can connect inside server like
osql -S -E .Helm
But how i access from remote machine using Enterprice Manager ?
Regards,
Yujin Boby
SQL Express 2014 was installed to support reporting for an application. I can connect to the server using the server name without any issue. When I run “select @@version”, I get SERVERNAMESQLEXPRESS, but I can’t connect to the server with SERVERNAMESQLEXPRESS. This is throwing off one of my script when trying to connect to the server.My script connects to the server using SERVERNAME for default instance or SERVERNAMEINSTANCENAME for named instance.
View 1 Replies View RelatedHi
I am really struggling with this problem.
I am connecting to several SQL 2000 servers on another LAN from my workstation and I have to go through a firewall.
I got the firewall people to open port 1433 and was then able to connect any server with a default instance using Query Anlyzer and the IP address of the Server.
When I try to connect from my workstation to a server with a named instance I am being blocked by the firewall before it gets to the server.
I went into Client Network Utility on my workstation and removed named pipes which only left Tcpip using port 1433.
Fire wall is now blocking nbname UDP 137.
Is there a setting somewhere on my workstation that I can force the traffic to the named instance to use Tcpip through port 1433.
Any Help would be great.
We have installed SQL 2000 SP4 on Windows 2000 Server. We created named instances on the SQL server.
When trying to connect to named instances from a remote sql client which is on windows 2000 and windows 2003, its throwing an error message saying that remote connections are disabled.
But, remote connections are enabled on the SQL server.
After changing the component services settings on windows 2003 where sql client is installed, we are able to connect to named instances.
But, after applying the same settings on another windows 2003 machine, we are unable to connect to the same instances.
We have another machine where we installed SQL 2005 on windows 2003 SP1. When trying to connect to named instances from any remote client, its throwing an error message saying that remote connections are disabled. But, remote connections are enabled in SQL server settings. We tried connecting to the instances by changing the component services settings but still we are facing the same issues.
Can you please help me on above issues?
I have SQL 05 and SQL 200o on same server . SQL 05 version is a named inatnce. But when i try to connect it from my computer first it doest show the name instance in the list and when i manulay write its name i got this error.
"A connection was successfully established with the server, but then an error occurred during the pre-login handshake. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)"
I went to check that remote connectiona nd SQL browsing is on or not but both were on . any ideas why this is happening and why the name is not coming in list of Server.
Thanks
I just installed Sql Server 2005, and opened the Sql Server management studio, and the connect to server dialog box popped up, i selected database engine, but what do I put in the server name box? I tried my computer name, and got an error, i tried localhost and got an error, i tried my computer name/localhost and got an error. I installed it as the default instance with windows authentication, and I verified that the sql server service is running, but I always get a login error. Can anyone help me get started?
View 5 Replies View RelatedI do hope someone can help
I have a windows server with SQL Express, I have followed the link here and still no luck
http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx
I have checked and checked again a thousand times
I can remote desktop and connect through SQL Management Express, but when I try this on my local machine I get the error 26
My knowledge is very limited and could do with some expert help
PS EDIT
I read somewhere that in TCP/IP properties all IP's should be set to 1433, is this correct
at the moment, apart from ALL IP which is set to 1433, IP1-9 are set to Dynamic Port =0, should I be setting all these to 1433
??
Can anyone tell me what are the necessary steps if I want to connect to a Remote SqlExpress Instance ? I am using Visual Studio 2005. When I tried to connect it says that the remote server does not allow remote connection. I have enabled all the protocols from Sql Server Configuration manager and disable the firewall. But it still not working. Pls Help me.
Thank You.
Hi everyone,
Please forgive me for the newbie question, I've done almost all of my DBA work on Oracle(on UNIX so I'm learning alot of AD stuff too) and am new to MS SQL Server.
I've got a SQL 2005 standard server that I'm trying to get to act as a publisher for a SQL 2005 Express instance, and I think I've narrowed down my problem to a connection issue.
(FYI, the Publisher works fine with another 2005 Standard server)
When I try to connect from the standard server to the express server using 'XYZSQLEXRESS' as my server name, it fails stating that it couldn't find the service, but I can connect just fine if I use 'XYZ' as the server name.
I think this is why I'm having trouble getting replication going as the replication wizard tells me that I have to connect via 'XYZSQLEXPRESS' in order to run the replication scripts.
Can anyone point me to the correct documentation to resolve this problem? Everything was easy-mode DBA work until we tried to add SQL Express to the mix, and I'm sort of running out of time on this one.
Thanks for any help!
Greetings friends,
Not sure if this is the right place for my question but here goes anyway.
I have an instance of SQL Server 2005 installed on my DEV PC. A colleague of mine wants to access my server from his machine which connected to the same network.
I logged on to SSMS and added him as a new login.
Will he be able to connect to it now or do I have to do more than just that?
Your help would be appreciated.
Good afternoon,
I currently develop/maintain VB 05' apps for PDA's and desktops. I've got a scanner app that scans labels to build/transmit orders via an HTTP byte stream. I'm currently building an inventory app that resides at the remote client (windows not web) and can eventually connect to my SQL Server @ corp. At this point SQL 2005 endpoints work on the internal network but fail to resolve remotely. I've read about connecting to a SQL Server via HTTP with ip specs embedded in the connect string but havnt been able to find an example. Outside of creating a VPN for connectivity, can anyone recommend connection ideas for my scenario? Is it true that endpoints are only recommended for intranet consumption?
Thanks,
ChrisG
I am attempting something that I have done many times before; however, in this instance it continues to fail.
I am trying to connect Management Studio to an instance of SQL Server 2005 Express over a VPN. The Management Studio connect dialog always fails with Error 26.
I have:
Enabled the instance for remote connections both TCP/IP and Named Pipes
Ensured that the instance is enabled for TCP/IP on the VPN address (10.2.1.1) and on port 1433
Ensured that the instance is running
Ensured that SQL Browser is running
Ensured that ports 1433 (TCP) and 1434 (UDP) are open on the firewall for inbound traffic
Rebooted the server following this configuration to ensure that the instance services are refreshed
Tried to connect from three separate clients (albeit on the same remote network)
Disabled the firewall to ensure no further complications (as a last resort)
I have this exact same setup functioning on a separate server.
There is an additional backstory to this problem; however, I will not complicate the scenario with it now. If you feel you can help then I can elaborate further on the servers history.
Thanks
James
I have opened up a port on a remote SQL instance and can see that the port is LISTENING when using the PortQry tool. I have also set the TCP port in the TCP/IP properties in the IPAll section for that instance, yet I am unable to connect and get an error of
Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1; handshake=14998; (.Net SqlClient Data Provider)
I have done this on other instances, although they were default instances, and it has always worked fine.
First time I've tried doing this - I have SQL Server 2012 installed on my local machine with an instance running (which was set up under an administrator account, not mine, which has no admin rights), and I'm trying to create a linked table from Access (also on the local machine) to a table on the server.
I tried creating a DSN using Windows Authentication, using the server name which is the same as my computer name, and got the error "Error 18452, Login failed. The login is from an untrusted domain and cannot be used with Windows authentication".
I then created a SQL authentication user ID and password, and tried the same thing using that instead, and got "Login failed for user <myusername>"
Is there some particular setting on the local instance I need to change to allow this kind of connection, or do I need to use something other than the server name to connect, such as an IP address? Remember that I have no admin access on this machine so any solution would have to avoid requiring that.
Hi,
The problem I have is this:
I have installed SQL Server 2005 Enterprise Edition on a W2K3 server that already has a SQL Server 2000 default instance installed. The installation appears to be a success. The problem is that having installed the client tools, and trying to connect, I get the following error message in a dialog:
"Cannot connect server SERVERNAMEINSTANCENAME
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)(Microsoft SQL Server)"
The funny thing is that I can connect to the SQL Server 2000 default instance that is on that server.
So it's obviously not a connection problem per se at my end i.e. bad dns etc which might stop me resolving the server name.
Googling for this error text gives the following advice on various web sites:
1. Check that the remote server allows connections.
It does, as other colleagues in my team have successfully installed the tools and can connect with no problems.
2. Check that the SQL Browser service is running.
It is, as without this running, my colleagues would not be able to connect either.
3. Open SQL Server Configuration Manager. Select "SQL Server 2005 Network Configuration | Protocols for MSSQLSERVER" then enable the protocols you need.
The required protocol (TCP/IP) is enabled. Named pipes is also enabled, although I don't think that we're using that. And shared memory is also enabled by default.
4. Open the firewall and add exceptions for sqlbrowser.exe or UDP port
1434
There is no firewall running at either end of the connection and as mentioned I can connect to the SS2K default instance.
5. Make sure that the server machine is reachable.
I can connect to the SS2K default instance so it must be reachable. I can't see that I would need to change any configuration settings as my colleagues are using exactly the same default settings for their connections and they work fine.
The only thing that I have done differently is that I originally installed the client tools using someone else's privileged account as I didn't have admin rights on my box. The client tools didn't work, so I got admin rights to my box, uninstalled the client tools and then reinstalled them using my account. Still no luck. Not sure if something is still hanging around after the uninstallation that would cause me a problem.
To help, I've also filled out the following questionnaire:
[1] Client side:
> What is the connection string in you app or DSN?
There isn't one. I'm trying to connect from the SQL Server Management Studio | 'Connect to Server' dialog.
> If client fails to connect, what is the client error messages?
"Cannot connect server Y
An error has occurred while establishing a connection to the server. When connecting to SQL Server
2005, this failure may be caused by the fact that under the default settings SQL Server does not
allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)(Microsoft SQL Server)"
Is the client remote or local to the SQL server machine? Remote
Can you ping your server? YES
Can you telnet to your SQL Server? YES
What is your client database provider? [SNAC | MDAC | ADO.NET1.0 | ADO.NET2.0| other (please specify] N/A
What is your client application? SQL Management Studio
Is your client computer in the same domain as the Server computer? Different domains
What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes]. All 3 protocols are enabled
Do you have aliases configured that match the server name portion of your connection string? No
Do you select force encryption on server and/or client? No
[2] Server side:
What is the MS SQL version? SQL Server 2005
What is the SKU of MS SQL? Enterprise
What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. All 3
Does the server start successfully? YES. Other people can connect to the same instance.
If SQL Server is a named instance, is the SQL browser enabled? YES
What is the account that the SQL Server is running under? Domain Account
Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? N/A. Firewall not running.
Do you make firewall exception for SQL Browser UDP port 1434? N/A. Firewall not running.
What tool or Application are you using to connect to SQL Server SQL Server Management Studio
[3] Platform:
What is the OS version? Windows 2003 (Server side), Windows XP Pro Version 2002 SP 2
Do you have third party antivirus, anti-spareware software installed? Symantec AntiVirus
[4] Misc:
If you have certificate configuration issue: N/A
Has anybody else come across this problem, as I've run out of ideas.
Many thanks,
Greetings,
I have a VB 2003 .NET application that I wrote for a customer that connects to a named instance of SQL 2000. Until recently it has been working fine. Lately the program either pops a timeout failure within a few seconds or a general network error. I've increased the connection timeout settings to 90 seconds but the error still pops within a few seconds. I'm thinking something has changed in the environment that prevents a clean connection to the named instance of SQL server.
How should this issue be troubleshoot to determine the problem and what areas need to be looked at?
Thanks
I've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamicsFINANCE) using SQL authentication from local SSMS, I get below error message:
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)
I assigned a static port number to the named instance [dynamicsFINANCE] 1450. I also setup the firewall rule to allow access to Port 1450.
Hi fellows,
I have to migrate all objects alogwith all constraints,SP,Triggers, indexes etc from Development instance to Production instance of a DB, all those things are created through wizard ie. Sql server 2000 Enterprise Manager. if i use DTS it only mirates data along with tables and views but constraints,SP,Triggers, indexes etc not yet copied.
can any body help me how can I solve this problem by copying all objects alogwith all constraints,SP,Triggers etc from Development instance to Production instance.
This is Sql server 2000 Cluster environment.
thanks in advance for any help
rahman
I have a 3 node cluster on which I have installed SSAS as it's own insntance. I have created this as a named instance and can connect to it by serverinstance if I'm on the server itself. However from my desktop I get the error saying instance was not found on server name.
I have defined an alternate port and setup firewall rules and can connect via server:port but not serverinstance. Prior to making this change SSAS was running on default port of 2383 and I could connect just by servername.
I have read many articles for previous versions saying that clustered SSAS will always use 2383 and that you must connect just using servername. However and this is were it gets strange. I have a 2 node UAT cluster with SSAS setup exactly the same way I've described above and I can connect from my desktop as serverinstance.
Should I be able to connect as serverinstances for a named clustered instance in 2012 ?
Hi, I have a task in hand to migrate (upgrade) from SQL2K named instance to SQL2K5 default instance. There are many intranet applications touching current SQL2K. I would like to perform this upgrade such that I don't have to touch any application code - meaning I don't have to change the connectionstring to point to new Default instance. How can I achieve this?
So, in otherwords, here is what I want to achieve:
Current Server: SQL2K: SERVER_AINSTANCE_A (named instance)
Upgraded Server: SQL2K5: SERVERB (default instance)
If I have both default, I could achive this by setting up DNS alias after migration done so that any call for SERVER_A would point to SERVER_B. But in my case, I don't have SERVER_A, I have named instance. Is there any solution?
Regards,
Vipul
Hi,
I want to move one database from the source SQL Server 2000 instance to a new SQL 2000 instance in another machine. I have five user databases in this source SQL instance. How should be my approach to move this single database out of this ? My understanding is restoring this database in the new instance, copying all logins to the new instance and then copying the jobs, DTS packages, alerts, operators only specific to this database will do it. Please let me know if this is exactly what I should do ..
Thanks in advance..
Regards,
Himansu
Hi,
I want to move one database from the source SQL Server 2000 instance to a new SQL 2000 instance in another machine. I have five user databases in this source SQL instance. How should be my approach to move this single database out of this ? My understanding is restoring this database in the new instance, copying all logins to the new instance and then copying the jobs, DTS packages, alerts, operators only specific to this database will do it. Please let me know if this is exactly what I should do ..
Thanks in advance..
Regards,
Himansu
I am trying to set up a Named Instance of SQL 2000 on the same machine that has a default instance of SQL 7.0. The setup always completes and I am able to register the Named Instance of the SQL Server with which it was installed on. However, when I try to connect the users to the database, with both windows and SQL authentication, I receive a SQL server not found error. I have tried an alias setup as well as physically specifying the port number in settup up an ODBC connection.
Has anyone ran into similar problems?
Also, has anyone been able to successfully complete the process as mentioned above?
I have a server with sql server 2005 installed as the default instance -- I have a piece of software that needs SQL2000 to be the default instance. Is there a way other than install new sql2005 named instance and move databases to rename my SQL2005 instance from <machinename> to <machinename>sql05 for example?
Bryan
Hi all,
i have installed SQL client instance on my Desktop "Machine-A", and i used to connect to SQLServer2000 running on another "Machine-B" by using valid username and password.
i created a DTS package and i used to run it. im very confused how the communication happens between the two machines and which process run where and which initiates which and which machine allocates waht resources. im really interested to know all these things. if any one know plz help me out.
Thanks in advance.
I have SQL Server 2000 Standard Edition (sp3a) running on a windows 2003 (sp4) Server.
It is a Production Server with 3 NAMED Instances and NO Default Instance.
Does anyone know if I can rerun the SQL Server Install and add a DEFAULT Instance to this box without disrupting the other Named Instances???
I work for a mid size company with the usual collection of enterprise applications. We are trying to consolidate our SQL environment consisting of around 100 databases none of which are over 100GB with the average database size around 5GB. Recently a large server was purchased as the "Big Daddy" SQL box. Obviously not all the databases will be moved to this one box but within reason a number can.
My question: What is the best way to configure the box?
1 OS & 1 Default Instance - How do we isolate loops memory leaks etc...
1 OS & Multiple instances, ie:Dedicated instance for each application. - How do you allocate CPU & memory, allow for optimum performance without putting others at risk from a rouge process?
Virtualized OS for each application with a default instance - Too much overhead impacts performance?
Future plans include offsite replication, perhaps mirroring with failover.
I'd appreciate anyone else's thoughts ideas? How have you tackled this problem in your environment?
Thanks
Scott
I installed SQL Server 2005 recently on a cluster. I didn't go for the default instance and instead I named the instance option. Now I would like to migrate everything from the named instance to the default instance, which I haven't yet installed.
Is this an easy process? What about the logins and the maintenance plans and jobs? Is there anything else I need to be aware of?
Hi
I've never had to do this, but when I downloaded the Web Workflow Approvals Starter Kit, it requested that I install the database into a User Instance of .SQLEXPRESS.
Now the problem is, I've installed it onto a default instance, so I was wondering whether you can create a named instance on top of a default instance... and if so, how would you do that?
Cheers
Chris
Got windows Vista Business edition, installed Visual Web Developer Express, SQL Server 2005 Express SP2, SQL Server Management Studio SP1 in that order. I was developing in VWD express without problems using WinXP but now on Vista Business, the local connection to SQL server appears to be a problem.
I know there's nothing wrong with my web.config or anything like that as it was working perfectly prior to running under Vista. If i specify the database on the live website, it works fine. If I specify the test database in app_data folder, I get the following exception:-
Server Error in '/UKSD' Application.
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[SqlException (0x80131904): Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +736211
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1959
System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +33
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +237
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +374
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +192
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197
System.Web.Security.SqlRoleProvider.GetRolesForUser(String username) +771
System.Web.Security.RolePrincipal.IsInRole(String role) +272
System.Web.Configuration.AuthorizationRule.IsTheUserInAnyRole(StringCollection roles, IPrincipal principal) +120
System.Web.Configuration.AuthorizationRule.IsUserAllowed(IPrincipal user, String verb) +300
System.Web.Configuration.AuthorizationRuleCollection.IsUserAllowed(IPrincipal user, String verb) +191
System.Web.Security.UrlAuthorizationModule.OnEnter(Object source, EventArgs eventArgs) +3509206
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
Version Information: Microsoft .NET Framework Version:2.0.50727.312; ASP.NET Version:2.0.50727.312
I am taking a guess it's somerthing to do with access issues, but can't find anything out on searching the forums etc..
I am setup as an administrator, running VWD as an administrator and for the record, SQL Server Management Studio express works fine.
Another small issue, when I run the application from VWD, I always have to minimise the application and restore it as the graphics get corrupt.
Please help!! I cannot debug when running of the live website.
The box I am trying to connect to is running two instances of SQL Server.
There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'.
I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" />
However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried:
<add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" />
but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used:
<add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" />
but this doesn't work either.
Am I mssing something here? Any help much appreciated
Thanks...