Migrate Oracle "Connect By" clause to TSQL

Hi,

Since this is my first post, if there are any violations in the rules of the forum, please let me know so that I can correct myself from next time.

I am currently working on migrating some oracle stored procedures to TSQL. One of the stored procedures uses "Connect By" clause in a select query, provided by Oracle. Is there a standard way to migrate this clause when we migrate this to SQL Server TSQL Stored Procedure.

For example:

I have a query in the oracle stored proc like:

SELECT id FROM t1 START WITH t1.id = p_id CONNECT BY
PRIOR t1.id = t1.parent_p_id

where p_id is an IN parameter passed to the stored procedure.

Please note that I have assumed "Connect By" clause syntax and usage is known to anyone who replies for this post.

Thanks for your help.

--
SriUnfortunately, there is no off-the-shelve recursive command available in TSQL, but it will be in the next (Yukon) release.|||No kidding?

[marching band playing]
THANK GOD
[/marching band playing]

Microsofts Sql web admin and sqldmo

Hello all,

has anyone had the opportunity to try the sql web admin tool? if so, i have one question.

How can i use this to connect to a remote sql/msde server?

in the server textbox on the login screen i try 'machine name'\'instance name', along with the sa username and password. This does not work however.

am i just entering the wrong value , or do i need to change the code of the .connect method to allow for remote connections?

TIA.

-C-By "does not work", do you mean you are getting an error?

I have been successful using Web Data Administrator to connect to a remote database. The remote database must have mixed authentication (SQL Server and Windows). and you must be using a valid login and password. I accessed the server using the IP address.

As an additional point, I was VPN authenticated on the remote network before connecting.

Terri

Microsoft.AnalysisServices.AdomdClient

Can anyone tell me if it's possible connect analysis services to an mobile application using AdomdClient..
If yes, how i do this?
If you are asking - is there a version of AdomdClient written for Windows Mobile, the answer is no. However, you can use XMLA directly to send queries to an Analysis Services server from any client|||Thank you. I can get data from Analysis Services, but now i want to show decision trees on mobile.. Do you know some king of AnalysisServices Viewer component for Mobile ?
|||There isn't that I know of, maybe you can modify the sample web viewer (inlcuded with SQL 2005) for this purpose?

Microsoft SqlServer Desktop Engine Connection Problem

i installed the MSDE2000A on server and i tried to connect from client machine through vb Application using connection string. Server anad client are in LAN. but Some systems able to connect and some systems are unable to connect.

i am getting the error:

"SqlServer does not exist or access denied "

for non connected machines.

the server is listening from these machines. but not connecting to MSDE.

can anyone give me solution what may be the cause.Ensure the System DSN used and login must have required privileges to connect to SQL server.

What is the authentication mode used?

Try:
1. Make sure the SQL server is on
2. Ping the server machine
3. Try connecting to the IP address rather than the server name

Review information from this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;328306) for potential causes and resolve it.|||i am using user authentication mode.
i have set DISABLENETWORKPROTOCOLS=0
i have done pinging through IP Address.
i am able ping database.
after doing all these test .. still getting same error...

is there any other possibilities....

Originally posted by Satya
Ensure the System DSN used and login must have required privileges to connect to SQL server.

What is the authentication mode used?

Try:
1. Make sure the SQL server is on
2. Ping the server machine
3. Try connecting to the IP address rather than the server name

Review information from this KBA (http://support.microsoft.com/default.aspx?scid=kb;en-us;328306) for potential causes and resolve it.|||Review points listed in the knowledgebase article.

i am using user authentication mode.
SQL Server does have only 2 modes - Windows only or mixed. Which on e is yours?

i have set DISABLENETWORKPROTOCOLS=0
Don't know about this protocol in SQL, it should be named-pipes, TCP/ip or Multi-protocol. From Start--> programs --> goto MSSQLServer program group and select Server network utility and check for enabled protocols.
i am able ping database.
How can you do that in SQL?|||mine is MIXEDMODE.

this is obtained by setting parameter SECURITYMODE=SQL

i am sorry to tell u that i ping to database.

not database... it is server.

i am able to ping to server where i installed MSDE.

Originally posted by Satya
Review points listed in the knowledgebase article.

SQL Server does have only 2 modes - Windows only or mixed. Which on e is yours?

Don't know about this protocol in SQL, it should be named-pipes, TCP/ip or Multi-protocol. From Start--> programs --> goto MSSQLServer program group and select Server network utility and check for enabled protocols.

How can you do that in SQL?|||I'm probably being silly, but could you have installed SQL as a named server and tried to access it as a default (unnamed) server?

-PatP|||Check for any h/w issues on server installed by referring to event viewer log.

Microsoft SQL Sever management Studio: Failed to open connection dialog

Does anyone encount the following problem before? When I tried to connect to Microsoft SQL server 2005 with MS SQL Server Management Studio, I received: "Failed to open connection dialog" message with additional information is "Package 'Mircrosoft SQL Server Object Explorer' failed to load.

This's just happened recently. Although I am receiving that message, I still able access into database with different types of connection.

Can someone shred some light?

Thanks

Tommy.

Have you attempted to connect the server using another client's machine.|||

This looks like some of your .NET components have corrupted. Reinstalling the same should help.

Thanks,
Kuntal

|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

|||

Good morning ( or afternoon for me )

Goo and helpful answer whether you have the cd disk but if you have downloaded from Microsoft (for example Express Edition or School version ), i think i must contact Microsoft to have the agreement to downloa and validate again

Have a nice day

Microsoft SQL Sever management Studio: Failed to open connection dialog

Does anyone encount the following problem before? When I tried to connect to Microsoft SQL server 2005 with MS SQL Server Management Studio, I received: "Failed to open connection dialog" message with additional information is "Package 'Mircrosoft SQL Server Object Explorer' failed to load.

This's just happened recently. Although I am receiving that message, I still able access into database with different types of connection.

Can someone shred some light?

Thanks

Tommy.

Have you attempted to connect the server using another client's machine.|||

This looks like some of your .NET components have corrupted. Reinstalling the same should help.

Thanks,
Kuntal

|||

The most likely cause of this is if a file has been deleted or corrupted. Does repairing the SQL Server management tools fix the problem?

Repairing SQL Server is a command-line operation. You can repair by inserting the installation media into the disk drive and typing the following:

start /wait <CD or DVD Drive>\setup.exe /qb REINSTALL=SQL_Tools90 REINSTALLMODE=OMUS

You can find more information on installing SQL Server from the command line here: http://msdn2.microsoft.com/en-us/library/ms144259.aspx

|||

Good morning ( or afternoon for me )

Goo and helpful answer whether you have the cd disk but if you have downloaded from Microsoft (for example Express Edition or School version ), i think i must contact Microsoft to have the agreement to downloa and validate again

Have a nice day

Microsoft SQL Server, Error: 87 17march

Source computer: SQL server 2005 SP1
Remote computer : SQLEXPRESS
When I try to register/connect with remote server (named instance) using sql
server management studio I am getting following error:
TITLE: New Server Registration
--
Testing the registered server failed. Verify the server name, login
credentials, and database, and then click Test again.
--
ADDITIONAL INFORMATION:
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: 25 - Connection string is not
valid) (Microsoft SQL Server, Error: 87)
Thanks
Ontario, canadaSource computer: SQL server 2005 SP1 (Microsoft windows nt 5.1)
Remote computer : Microsoft SQL server express edition (Microsoft windows
nt 5.1)
-
ontario, canada
"db" wrote:
> Source computer: SQL server 2005 SP1
> Remote computer : SQLEXPRESS
>
> When I try to register/connect with remote server (named instance) using sql
> server management studio I am getting following error:
> TITLE: New Server Registration
> --
> Testing the registered server failed. Verify the server name, login
> credentials, and database, and then click Test again.
> --
> ADDITIONAL INFORMATION:
> 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: 25 - Connection string is not
> valid) (Microsoft SQL Server, Error: 87)
>
> Thanks
> Ontario, canada

Microsoft SQL Server, Error: 87 17march

Source computer: SQL server 2005 SP1
Remote computer : SQLEXPRESS
When I try to register/connect with remote server (named instance) using sql
server management studio I am getting following error:
TITLE: New Server Registration
Testing the registered server failed. Verify the server name, login
credentials, and database, and then click Test again.
ADDITIONAL INFORMATION:
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: 25 - Connection string is not
valid) (Microsoft SQL Server, Error: 87)
Thanks
Ontario, canada
Source computer: SQL server 2005 SP1 (Microsoft windows nt 5.1)
Remote computer : Microsoft SQL server express edition (Microsoft windows
nt 5.1)
-
ontario, canada
"db" wrote:

> Source computer: SQL server 2005 SP1
> Remote computer : SQLEXPRESS
>
> When I try to register/connect with remote server (named instance) using sql
> server management studio I am getting following error:
> TITLE: New Server Registration
> --
> Testing the registered server failed. Verify the server name, login
> credentials, and database, and then click Test again.
> --
> ADDITIONAL INFORMATION:
> 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: 25 - Connection string is not
> valid) (Microsoft SQL Server, Error: 87)
>
> Thanks
> Ontario, canada

Microsoft SQL Server, Error: 53

hi, i am trying to acces my database but i get this error. I allowed remote
connections in sql server 2005 but i still get the error.
TITLE: Connect to Server
Cannot connect to MSSQLSERVER.
ADDITIONAL INFORMATION:
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
Hoping for some help , kind regards xenta.
How is the client configured? Check with cliconfg.exe.
What app are you using? If not a tool like QA, SSMS etc, then what does the connection string look
like?
How is the server configured? Check with SQL Server Configuration Manager. Does it listen to Named
Pipes, for instance.
The error states that the client tries to connect using Named Pipes.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"zentax" <millionsmillions@.hotmail.com> wrote in message
news:eYGOxgcdHHA.2088@.TK2MSFTNGP05.phx.gbl...
> hi, i am trying to acces my database but i get this error. I allowed remote connections in sql
> server 2005 but i still get the error.
> TITLE: Connect to Server
> --
> Cannot connect to MSSQLSERVER.
> --
> ADDITIONAL INFORMATION:
> 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: Named Pipes Provider, error: 40 - Could not open a
> connection to SQL Server) (Microsoft SQL Server, Error: 53)
>
> Hoping for some help , kind regards xenta.
>
>

Microsoft SQL Server, Error: 53

hi, i am trying to acces my database but i get this error. I allowed remote
connections in sql server 2005 but i still get the error.
TITLE: Connect to Server
--
Cannot connect to MSSQLSERVER.
ADDITIONAL INFORMATION:
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
Hoping for some help , kind regards xenta.How is the client configured? Check with cliconfg.exe.
What app are you using? If not a tool like QA, SSMS etc, then what does the
connection string look
like?
How is the server configured? Check with SQL Server Configuration Manager. D
oes it listen to Named
Pipes, for instance.
The error states that the client tries to connect using Named Pipes.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"zentax" <millionsmillions@.hotmail.com> wrote in message
news:eYGOxgcdHHA.2088@.TK2MSFTNGP05.phx.gbl...
> hi, i am trying to acces my database but i get this error. I allowed remot
e connections in sql
> server 2005 but i still get the error.
> TITLE: Connect to Server
> --
> Cannot connect to MSSQLSERVER.
> --
> ADDITIONAL INFORMATION:
> 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: Named Pipes Provider, error:
40 - Could not open a
> connection to SQL Server) (Microsoft SQL Server, Error: 53)
>
> Hoping for some help , kind regards xenta.
>
>

Microsoft SQL Server, Error: 53

hi, i am trying to acces my database but i get this error. I allowed remote
connections in sql server 2005 but i still get the error.
TITLE: Connect to Server
--
Cannot connect to MSSQLSERVER.
--
ADDITIONAL INFORMATION:
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
Hoping for some help , kind regards xenta.How is the client configured? Check with cliconfg.exe.
What app are you using? If not a tool like QA, SSMS etc, then what does the connection string look
like?
How is the server configured? Check with SQL Server Configuration Manager. Does it listen to Named
Pipes, for instance.
The error states that the client tries to connect using Named Pipes.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"zentax" <millionsmillions@.hotmail.com> wrote in message
news:eYGOxgcdHHA.2088@.TK2MSFTNGP05.phx.gbl...
> hi, i am trying to acces my database but i get this error. I allowed remote connections in sql
> server 2005 but i still get the error.
> TITLE: Connect to Server
> --
> Cannot connect to MSSQLSERVER.
> --
> ADDITIONAL INFORMATION:
> 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: Named Pipes Provider, error: 40 - Could not open a
> connection to SQL Server) (Microsoft SQL Server, Error: 53)
>
> Hoping for some help , kind regards xenta.
>
>

Microsoft SQL Server, Error: 15314

When I try to connect to MS SQL Server 2005 standard edition it appear the error message as [Either no algorithm has been specified or the bitlength and the algorithm specified for the key are not available in this installation of windows (Microsoft SQL Server, Error: 15314)].

Please anyone explain me how this error message mean. How to solve this matter to avoid this happen anymore.

Thank you

Simba

If you are on windows 2000 then this is probably due to the existence of a symmetric key with the AES alogorithm.

Check the create symmetric key entry in Books Online and check the following topic: Choosing an Encryption Algorithm

HTH,

-Steven Gott

SDE/T

SQL Server

|||

Thanks Steven for your reply.

I am using Window Advanced Server 2003. The error does not happen every time I login to the SQL Server 2005 but it just happens sometimes. I mean I have a website that connects to SQL Server. My users can use properly just sometimes they cannot connect to the database. So I have to try to connect directly to database and it appears the error.

Simba

|||

Looks like a symmetric key issue as this is a one key that is used for both encryption and decryption. This is a fast, commonly used method for encryption. As with a certificate, many parameters are available when creating Symmetric Keys. In most cases, we only need a limited set of parameters. You can refer to Books Online for all the parameters.

Are you using any specific encryption algorithm?

Microsoft SQL Server, Error: 10053

O get this error when trying to connect to my database. About 5 minutes ago it was working fine...seems to go in and out. We have native client installed in this server as well so not sure why I keep having connection issues. I tried both Windows Authentification and local sql account, both are very choppy, sometimes works sometimes doesn't.

TITLE: Connect to Server

Cannot connect to BG-SQL2005.

ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An established connection was aborted by the software in your host machine.) (Microsoft SQL Server, Error: 10053)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10053&LinkId=20476

BUTTONS:

OK

I am also getting this error when trying to ALTER one of my stored procs :

A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

Mostlikely the server is closing the connections for some reason, possibly the client does not have permission to access some sqlserver resources, e.g. database, sp, xp. We might get more hint as to why if you could share out the sql server ERRORLOG.|||Here are my logs:
http://www.photopizzaz.biz/junk/logs.txt
aprint screens of various errors I have received on my remote SQL Server 2005 (Enterprise version):
http://www.photopizzaz.biz/junk/sqlserver_2005_errors_and_resolutions.doc|||I can't see your error log. Please also enable sql server traceflag -T4029 when you do the repro. Update the errorlog with latest repro.|||

issue resolved, reinstalled SQL Server 2005 completely

thanks for the inputs!

Microsoft SQL Server Management Studio Express

I am attempting to connect to a SQL Server 2005 database using a Visual
Studio.Net 2003 application.
When I use this connection string, I get a Keyword not supported: 'user
instance'. error.
<add key="SiteSqlServer" value="Data Source=.\SQLExpress;uid=sa;pwd=;User
Instance=True;AttachDBFilename=|DataDirectory|MyDB .mdf;Initial
Catalog=MyDB;" />
When I remove the "User Instance=True", I get a
Database 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MyDB.mdf'
already exists. Could not attach file '|DataDirectory|MyDB.mdf' as database
'MyDB'.
What kind of connection string do I use and why doesn't VS2003 recognize the
"User Instance=True"?
See if this helps:
http://msdn.microsoft.com/sql/defaul...xpuserinst.asp
Andrew J. Kelly SQL MVP
"Nick K" <nospam@.hotmail.com> wrote in message
news:eT0gKC7DGHA.1032@.TK2MSFTNGP11.phx.gbl...
>I am attempting to connect to a SQL Server 2005 database using a Visual
> Studio.Net 2003 application.
> When I use this connection string, I get a Keyword not supported: 'user
> instance'. error.
> <add key="SiteSqlServer" value="Data Source=.\SQLExpress;uid=sa;pwd=;User
> Instance=True;AttachDBFilename=|DataDirectory|MyDB .mdf;Initial
> Catalog=MyDB;" />
> When I remove the "User Instance=True", I get a
> Database 'c:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\MyDB.mdf'
> already exists. Could not attach file '|DataDirectory|MyDB.mdf' as
> database
> 'MyDB'.
> What kind of connection string do I use and why doesn't VS2003 recognize
> the
> "User Instance=True"?
>
|||I read the document. I don't see an explanation of the "User Instance=True",
keyword not recognized error I am seeing. Is this because my SQLClient is
the .Net Framework 1.1? I'm currently using VS 2003
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23XxRkh7DGHA.796@.TK2MSFTNGP10.phx.gbl...
> See if this helps:
>
http://msdn.microsoft.com/sql/defaul...xpuserinst.asp[vbcol=seagreen]
>
> --
> Andrew J. Kelly SQL MVP
>
> "Nick K" <nospam@.hotmail.com> wrote in message
> news:eT0gKC7DGHA.1032@.TK2MSFTNGP11.phx.gbl...
Source=.\SQLExpress;uid=sa;pwd=;User
>
|||I think you should re-read the document again and make sure you understand
exactly what a "User Instance" really is. If you really want to use a User
Instance you can not use SQL Logins as stated in the document. If you don't
really want a User instance you connect just like any other connection to
SQL Server but you do not need to attach the files. This assumes you have
already loaded SQL Server on that machine. I am not sure if when using a
User Instance if you need the 2.0 client or not but I suspect you might.
Andrew J. Kelly SQL MVP
"Nick K" <nospam@.hotmail.com> wrote in message
news:%23Tn$rO8DGHA.2708@.TK2MSFTNGP11.phx.gbl...
>I read the document. I don't see an explanation of the "User
>Instance=True",
> keyword not recognized error I am seeing. Is this because my SQLClient is
> the .Net Framework 1.1? I'm currently using VS 2003
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:%23XxRkh7DGHA.796@.TK2MSFTNGP10.phx.gbl...
> http://msdn.microsoft.com/sql/defaul...xpuserinst.asp
> Source=.\SQLExpress;uid=sa;pwd=;User
>
|||Hello Nick,
I'm afraid that you need VS2005/.net 2.0 and SqlClient native data provider
for SQL Server support is included.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Nick K" <nospam@.hotmail.com>
>References: <eT0gKC7DGHA.1032@.TK2MSFTNGP11.phx.gbl>
<#XxRkh7DGHA.796@.TK2MSFTNGP10.phx.gbl>
>Subject: Re: Microsoft SQL Server Management Studio Express
>Date: Mon, 2 Jan 2006 10:38:47 -0700
>Lines: 44
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
>Message-ID: <#Tn$rO8DGHA.2708@.TK2MSFTNGP11.phx.gbl>
>Newsgroups:
microsoft.public.vsnet.general,microsoft.public.sq lserver.connect,microsoft.
public.sqlserver.mseq
>NNTP-Posting-Host: 70-59-19-126.hlrn.qwest.net 70.59.19.126
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGP11.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.connect:46507
microsoft.public.sqlserver.mseq:7868 microsoft.public.vsnet.general:30200
>X-Tomcat-NG: microsoft.public.sqlserver.connect
>I read the document. I don't see an explanation of the "User
Instance=True",
>keyword not recognized error I am seeing. Is this because my SQLClient is
>the .Net Framework 1.1? I'm currently using VS 2003
>"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>news:%23XxRkh7DGHA.796@.TK2MSFTNGP10.phx.gbl...
>http://msdn.microsoft.com/sql/defaul...s/dnsse/html/s
qlexpuserinst.asp[vbcol=seagreen]
>Source=.\SQLExpress;uid=sa;pwd=;User
recognize
>
>

Microsoft SQL Server Management Studio Express

I am attempting to connect to a SQL Server 2005 database using a Visual
Studio.Net 2003 application.
When I use this connection string, I get a Keyword not supported: 'user
instance'. error.
<add key="SiteSqlServer" value="Data Source=.\SQLExpress;uid=sa;pwd=;User
Instance=True;AttachDBFilename=|DataDirectory|MyDB .mdf;Initial
Catalog=MyDB;" />
When I remove the "User Instance=True", I get a
Database 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MyDB.mdf'
already exists. Could not attach file '|DataDirectory|MyDB.mdf' as database
'MyDB'.
What kind of connection string do I use and why doesn't VS2003 recognize the
"User Instance=True"?
See if this helps:
http://msdn.microsoft.com/sql/defaul...xpuserinst.asp
Andrew J. Kelly SQL MVP
"Nick K" <nospam@.hotmail.com> wrote in message
news:eT0gKC7DGHA.1032@.TK2MSFTNGP11.phx.gbl...
>I am attempting to connect to a SQL Server 2005 database using a Visual
> Studio.Net 2003 application.
> When I use this connection string, I get a Keyword not supported: 'user
> instance'. error.
> <add key="SiteSqlServer" value="Data Source=.\SQLExpress;uid=sa;pwd=;User
> Instance=True;AttachDBFilename=|DataDirectory|MyDB .mdf;Initial
> Catalog=MyDB;" />
> When I remove the "User Instance=True", I get a
> Database 'c:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\MyDB.mdf'
> already exists. Could not attach file '|DataDirectory|MyDB.mdf' as
> database
> 'MyDB'.
> What kind of connection string do I use and why doesn't VS2003 recognize
> the
> "User Instance=True"?
>
|||I read the document. I don't see an explanation of the "User Instance=True",
keyword not recognized error I am seeing. Is this because my SQLClient is
the .Net Framework 1.1? I'm currently using VS 2003
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23XxRkh7DGHA.796@.TK2MSFTNGP10.phx.gbl...
> See if this helps:
>
http://msdn.microsoft.com/sql/defaul...xpuserinst.asp[vbcol=seagreen]
>
> --
> Andrew J. Kelly SQL MVP
>
> "Nick K" <nospam@.hotmail.com> wrote in message
> news:eT0gKC7DGHA.1032@.TK2MSFTNGP11.phx.gbl...
Source=.\SQLExpress;uid=sa;pwd=;User
>
|||I think you should re-read the document again and make sure you understand
exactly what a "User Instance" really is. If you really want to use a User
Instance you can not use SQL Logins as stated in the document. If you don't
really want a User instance you connect just like any other connection to
SQL Server but you do not need to attach the files. This assumes you have
already loaded SQL Server on that machine. I am not sure if when using a
User Instance if you need the 2.0 client or not but I suspect you might.
Andrew J. Kelly SQL MVP
"Nick K" <nospam@.hotmail.com> wrote in message
news:%23Tn$rO8DGHA.2708@.TK2MSFTNGP11.phx.gbl...
>I read the document. I don't see an explanation of the "User
>Instance=True",
> keyword not recognized error I am seeing. Is this because my SQLClient is
> the .Net Framework 1.1? I'm currently using VS 2003
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:%23XxRkh7DGHA.796@.TK2MSFTNGP10.phx.gbl...
> http://msdn.microsoft.com/sql/defaul...xpuserinst.asp
> Source=.\SQLExpress;uid=sa;pwd=;User
>

Microsoft SQL Server Login

I'm getting the following message trying to connect through ODBC:
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
I've been troubleshooting for about a month and haven't solve the problem.
Could anyone told me what to do in order to fix the problem?
Thanks in advance.Can you post the connection string you are using?
"Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
> I'm getting the following message trying to connect through ODBC:
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> I've been troubleshooting for about a month and haven't solve the problem.
> Could anyone told me what to do in order to fix the problem?
> Thanks in advance.|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
Someone already suggest me to remove:
OPEN=ODBC
and it didn't connect.
Hope you can help me.
Thanks in advance
"Adam David Moss" wrote:
> Can you post the connection string you are using?
>
> "Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
> news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
> > I'm getting the following message trying to connect through ODBC:
> >
> > "Connection failed:
> > SQLState: '01S00'
> > SQL Server Error: 0
> > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> > Connection failed:
> > SQLState: 'S1T00'
> > SQL server Error: 0
> > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> >
> > I've been troubleshooting for about a month and haven't solve the problem.
> >
> > Could anyone told me what to do in order to fix the problem?
> >
> > Thanks in advance.
>
>|||Try removing the database=... Your DSN already specifies this does it not?
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:175EC6DB-10AF-41B0-9DB2-A9AC10D1DCF3@.microsoft.com...
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> Someone already suggest me to remove:
> OPEN=ODBC
> and it didn't connect.
> Hope you can help me.
> Thanks in advance
>
> "Adam David Moss" wrote:
> > Can you post the connection string you are using?
> >
> >
> > "Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in
message
> > news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
> > > I'm getting the following message trying to connect through ODBC:
> > >
> > > "Connection failed:
> > > SQLState: '01S00'
> > > SQL Server Error: 0
> > > [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> > > Connection failed:
> > > SQLState: 'S1T00'
> > > SQL server Error: 0
> > > [Microsoft][ODBC SQL Server Driver]Timeout expired"
> > >
> > > I've been troubleshooting for about a month and haven't solve the
problem.
> > >
> > > Could anyone told me what to do in order to fix the problem?
> > >
> > > Thanks in advance.
> >
> >
> >|||Just out of curiosity:
If you test the connection using the ODBC admin applet does it successfully
connect?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||No, connection fail.
"Rand Boyd [MSFT]" wrote:
> Just out of curiosity:
> If you test the connection using the ODBC admin applet does it successfully
> connect?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Microsoft SQL Server Login

I'm getting the following message trying to connect through ODBC:
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribu
te
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
I've been troubleshooting for about a month and haven't solve the problem.
Could anyone told me what to do in order to fix the problem?
Thanks in advance.Can you post the connection string you are using?
"Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
> I'm getting the following message trying to connect through ODBC:
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attri
bute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> I've been troubleshooting for about a month and haven't solve the problem.
> Could anyone told me what to do in order to fix the problem?
> Thanks in advance.|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_
CALLISTO;
Someone already suggest me to remove:
OPEN=ODBC
and it didn't connect.
Hope you can help me.
Thanks in advance
"Adam David Moss" wrote:

> Can you post the connection string you are using?
>
> "Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
> news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
>
>|||Try removing the database=... Your DSN already specifies this does it not?
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:175EC6DB-10AF-41B0-9DB2-A9AC10D1DCF3@.microsoft.com...[vbcol=seagreen]
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_
CALLISTO;
> Someone already suggest me to remove:
> OPEN=ODBC
> and it didn't connect.
> Hope you can help me.
> Thanks in advance
>
> "Adam David Moss" wrote:
>
message[vbcol=seagreen]
problem.[vbcol=seagreen]|||Just out of curiosity:
If you test the connection using the ODBC admin applet does it successfully
connect?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||No, connection fail.
"Rand Boyd [MSFT]" wrote:

> Just out of curiosity:
> If you test the connection using the ODBC admin applet does it successfull
y
> connect?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Microsoft SQL Server Login

I'm getting the following message trying to connect through ODBC:
"Connection failed:
SQLState: '01S00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
Connection failed:
SQLState: 'S1T00'
SQL server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired"
I've been troubleshooting for about a month and haven't solve the problem.
Could anyone told me what to do in order to fix the problem?
Thanks in advance.
Can you post the connection string you are using?
"Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
> I'm getting the following message trying to connect through ODBC:
> "Connection failed:
> SQLState: '01S00'
> SQL Server Error: 0
> [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute
> Connection failed:
> SQLState: 'S1T00'
> SQL server Error: 0
> [Microsoft][ODBC SQL Server Driver]Timeout expired"
> I've been troubleshooting for about a month and haven't solve the problem.
> Could anyone told me what to do in order to fix the problem?
> Thanks in advance.
|||Here is the connection string:
OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
Someone already suggest me to remove:
OPEN=ODBC
and it didn't connect.
Hope you can help me.
Thanks in advance
"Adam David Moss" wrote:

> Can you post the connection string you are using?
>
> "Alexis Robles" <Alexis Robles@.discussions.microsoft.com> wrote in message
> news:42D09044-6BD9-43E9-9199-411FF3E49898@.microsoft.com...
>
>
|||Try removing the database=... Your DSN already specifies this does it not?
"Alexis Robles" <AlexisRobles@.discussions.microsoft.com> wrote in message
news:175EC6DB-10AF-41B0-9DB2-A9AC10D1DCF3@.microsoft.com...[vbcol=seagreen]
> Here is the connection string:
> OPEN=ODBC;DATABASE=AFM_CALLISTO;DSN=AFM_CALLISTO;
> Someone already suggest me to remove:
> OPEN=ODBC
> and it didn't connect.
> Hope you can help me.
> Thanks in advance
>
> "Adam David Moss" wrote:
message[vbcol=seagreen]
problem.[vbcol=seagreen]
|||Just out of curiosity:
If you test the connection using the ODBC admin applet does it successfully
connect?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||No, connection fail.
"Rand Boyd [MSFT]" wrote:

> Just out of curiosity:
> If you test the connection using the ODBC admin applet does it successfully
> connect?
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>