Error 913: Could not find database ID119. Database may not be acti

Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.
When and where you are getting that error?
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.

Error 913: Could not find database ID119. Database may not be acti

Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
--
Marcin S.When and where you are getting that error?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.|||I get this error all the time if i try to list tables or when i try to view
propperties, just anywhere when i try to do some thind with this databas.
I can see the database in DB list, it is in the SYSDATABASES but it is
inaccessible
BUT!
When i run : DBCC CHECKDB ('someDB') i then get
Server: Msg 911, Level 16, State 1, Line 1
Could not locate entry in sysdatabases for database 'MSSQL100011'. No entry
found with that name. Make sure that the name is entered correctly.
but a selects in SYSDATABASES says that it exists... strange
And as i wrote i can restore any database that I backup on the serbver but
when moving this from an other Working SQL server. The Restore process is
done successfull without any error.
--
Marcin S.
"Narayana Vyas Kondreddi" wrote:
> When and where you are getting that error?
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
> news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
> Hi,
> After restore i get this error in MSSQL server 2000 (SP4)
> Error 913: Could not find database ID119. Database may not be activated or
> may be in transitionw
> I can not find out wath could be wrong the only thing that is diffrent in
> SYSDatabases i that the version column is NULL all other databases have a
> version number 539 the status is 1077936153.
> We did not get any error during restore the .bak fil is from an other SQL
> server SP4 and the database works there. We have moved databases before
> without any problem.
>
> --
> Marcin S.
>
>sql

Error 913: Could not find database ID119. Database may not be acti

Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.When and where you are getting that error?
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Marcin S." <MarcinS@.discussions.microsoft.com> wrote in message
news:C8A32931-5D30-4B37-9EF9-68280A564AAC@.microsoft.com...
Hi,
After restore i get this error in MSSQL server 2000 (SP4)
Error 913: Could not find database ID119. Database may not be activated or
may be in transitionw
I can not find out wath could be wrong the only thing that is diffrent in
SYSDatabases i that the version column is NULL all other databases have a
version number 539 the status is 1077936153.
We did not get any error during restore the .bak fil is from an other SQL
server SP4 and the database works there. We have moved databases before
without any problem.
Marcin S.

Error 823: SQL service won't start!

Hello all,
Our database server went down due to a power outage but everything came back
fine except the MSSQL serverice won't start. I get the following error
listed below when trying to start the service. I tried starting the service
with the -f switch, which didn't work. I also tried the rebuildm.exe which
also failed. Would installing SQL to different drive be worth the effort?
Thank you for any advice!
Troy
spid5 Clearing tempdb database.
spid5 Encountered an unexpected error while checking the sector size for
file 'C:\Program Files\Microsoft SQL Server\MSSQL\DATA\TEMPDB.MDF'. Check
the SQL Server error log for more information.
spid5 CREATE DATABASE failed. Some file names listed could not be created.
Check previous errors.
spid5 Error: 823, Severity: 24, State: 6
spid5 I/O error 38(Reached the end of the file.) detected during read at
offset 0000000000000000 in file 'C:\Program Files\Microsoft SQL
Server\MSSQL\DATA\TEMPDB.MDF'.
spid5 WARNING: problem activating all tempdb files. See previous errors.
Restart server with -f to correct the situation.Your disk has a fatal error and you will not be able to start the server as
the disk is where it's trying to create the TEMPDB database, which is
required for the server to startup. You should contact PSS who will be able
to help you (http://support.microsoft.com)
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Travis" <Tkasch@.neb.rr.com> wrote in message
news:xzL%b.15820$QP.6929@.twister.rdc-kc.rr.com...
> Hello all,
> Our database server went down due to a power outage but everything came
back
> fine except the MSSQL serverice won't start. I get the following error
> listed below when trying to start the service. I tried starting the
service
> with the -f switch, which didn't work. I also tried the rebuildm.exe
which
> also failed. Would installing SQL to different drive be worth the effort?
> Thank you for any advice!
> Troy
> spid5 Clearing tempdb database.
> spid5 Encountered an unexpected error while checking the sector size for
> file 'C:\Program Files\Microsoft SQL Server\MSSQL\DATA\TEMPDB.MDF'. Check
> the SQL Server error log for more information.
> spid5 CREATE DATABASE failed. Some file names listed could not be created.
> Check previous errors.
> spid5 Error: 823, Severity: 24, State: 6
> spid5 I/O error 38(Reached the end of the file.) detected during read at
> offset 0000000000000000 in file 'C:\Program Files\Microsoft SQL
> Server\MSSQL\DATA\TEMPDB.MDF'.
> spid5 WARNING: problem activating all tempdb files. See previous errors.
> Restart server with -f to correct the situation.
>

Error 823: SQL service won't start!

Hello all,
Our database server went down due to a power outage but everything came back
fine except the MSSQL serverice won't start. I get the following error
listed below when trying to start the service. I tried starting the service
with the -f switch, which didn't work. I also tried the rebuildm.exe which
also failed. Would installing SQL to different drive be worth the effort?
Thank you for any advice!
Troy
spid5 Clearing tempdb database.
spid5 Encountered an unexpected error while checking the sector size for
file 'C:\Program Files\Microsoft SQL Server\MSSQL\DATA\TEMPDB.MDF'. Check
the SQL Server error log for more information.
spid5 CREATE DATABASE failed. Some file names listed could not be created.
Check previous errors.
spid5 Error: 823, Severity: 24, State: 6
spid5 I/O error 38(Reached the end of the file.) detected during read at
offset 0000000000000000 in file 'C:\Program Files\Microsoft SQL
Server\MSSQL\DATA\TEMPDB.MDF'.
spid5 WARNING: problem activating all tempdb files. See previous errors.
Restart server with -f to correct the situation.Your disk has a fatal error and you will not be able to start the server as
the disk is where it's trying to create the TEMPDB database, which is
required for the server to startup. You should contact PSS who will be able
to help you (http://support.microsoft.com)
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Travis" <Tkasch@.neb.rr.com> wrote in message
news:xzL%b.15820$QP.6929@.twister.rdc-kc.rr.com...
> Hello all,
> Our database server went down due to a power outage but everything came
back
> fine except the MSSQL serverice won't start. I get the following error
> listed below when trying to start the service. I tried starting the
service
> with the -f switch, which didn't work. I also tried the rebuildm.exe
which
> also failed. Would installing SQL to different drive be worth the effort?
> Thank you for any advice!
> Troy
> spid5 Clearing tempdb database.
> spid5 Encountered an unexpected error while checking the sector size for
> file 'C:\Program Files\Microsoft SQL Server\MSSQL\DATA\TEMPDB.MDF'. Check
> the SQL Server error log for more information.
> spid5 CREATE DATABASE failed. Some file names listed could not be created.
> Check previous errors.
> spid5 Error: 823, Severity: 24, State: 6
> spid5 I/O error 38(Reached the end of the file.) detected during read at
> offset 0000000000000000 in file 'C:\Program Files\Microsoft SQL
> Server\MSSQL\DATA\TEMPDB.MDF'.
> spid5 WARNING: problem activating all tempdb files. See previous errors.
> Restart server with -f to correct the situation.
>

Error 8120 when selecting MAX(...)

Hi Folks,

I have a very strange problem with the MSSQL JDBC drivers (SP1).
I am calling executeQuery() on a very simple query:

SELECT MAX(fulltext_id) FROM contractor

I am getting an error 8120 (column is not contained in an aggregate-- see stack trace below). It thinks that 'id' is part of the column list, yet it is not.

Now, the strange thing is, when I run SQL Profiler, I see this line:

exec sp_cursoropen @.P1 output, N'SELECT MAX(fulltext_id) , * FROM contractor', @.P2 output, @.P3 output, @.P4 output

It seems that someone (the driver?) added a comma and a "*" after the MAX(fulltext_id) clause! What gives?

Thanks much,
Steve

===

java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Column 'contractor.id' is invalid in the select list because it is not contained in an aggregate function and there is no GROUP BY clause.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.pro cessReplyToken(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReply(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest. openCursor(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplStatemen t.execute(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecut e(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.executeQuery Internal(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.executeQuery (Unknown Source)I don't know why the Java is throwing that * in there, but that is definitely what is causing the problem. That is not a valid SQL statement.

blindman|||Originally posted by blindman
I don't know why the Java is throwing that * in there, but that is definitely what is causing the problem. That is not a valid SQL statement.

blindman

Actually I found what was wrong. It appears I was opening the ResultSet as an updatable cursor. The SQL Server driver apparently tacks on a "*" to make the query select all rows (so any row in the query can be updated?)

I am still kinda confused, but opening the cursor as read-only fixed the problem... :?|||Originally posted by sehugg
Actually I found what was wrong. It appears I was opening the ResultSet as an updatable cursor. The SQL Server driver apparently tacks on a "*" to make the query select all rows (so any row in the query can be updated?)

I am still kinda confused, but opening the cursor as read-only fixed the problem... :?

Obviously a bug in the JDBC driver.

Error 8102: Cannot Update Identity Column

Hi,

I'd set up Transactional Replication btw 2 servers running on MSSQL 2000.

However, from time to time, I encounter Error 8102. I try to reinitialise the subscription but failed. After I delete the current subscription and PUSH a new one, it will works fine again.

I'm curious why this is happening as I'd already set all the tables (articles) in the subscriber to "YES, not_for_replication".

Any idea?

Thanks.Originally posted by da_i256
Hi,

I'd set up Transactional Replication btw 2 servers running on MSSQL 2000.

However, from time to time, I encounter Error 8102. I try to reinitialise the subscription but failed. After I delete the current subscription and PUSH a new one, it will works fine again.

I'm curious why this is happening as I'd already set all the tables (articles) in the subscriber to "YES, not_for_replication".

Any idea?

Thanks.

check this thread:
http://dbforums.com/arch/7/2003/5/779346|||thanks, harshal_in...

then link did provide some insights into the matter.

anyone else got any idea?

thanks.|||Have you gone thru the MSDN link (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro01/html/sql01d4.asp) referred in the above post, it must have resolved with the workaround mentioned.|||Thanks guys...

the problem solved... :>sql

Error 40: could not open a connection to Mssql server

Hi,

I'm using sql server 2005 express edition. I have created a database using sql server management studio express edition. Now I'm trying to connect it in visual studio 2005. It show following error.

An error has occurred while establishing a connection to the server. When connections to SQL 5erver 2005, this failure may be caused by the fact under the server's default settings SQL Server does not allow remote connections, (provider: Named Pipes Provider, error: 40- Could not open a connection to SQL Server)

I have enables named pipes from Sql services configuration manager.

Hi,

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Is just a basic connectivity error meaning the client could not connect to the target SQL Server. So just follow the basic connectivity troubleshooting guidelines on our SQL Protocols blog, see:

SQL Server 2005 Connectivity Issue Troubleshoot - Part I

http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx

and

SQL Server 2005 Connectivity Issue Troubleshoot - Part II

http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx

This should help you debug the problem.

Error 3621

For some reason I'm getting the following error on my MS2000 MSSQl
server. THe message is being written into my logs on the server.
MSSQL Error Msg 3621 The statement has been terminated
THis is then followed by the information message
Connected to DB
THis continues in a over and over again. My DB was working
fine and I could use the query analyzer, now however I cannot
query anything in the DB.
Any help would be great. I really dont want to reinstall this
as a solution.
TIA
dogdog
This message is usually preceded by another message indicating the cause the
error. Are these messages in the SQL Server error log or in a log generated
by your application?
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.15.15.20.194339@.noemail.com...
> For some reason I'm getting the following error on my MS2000 MSSQl
> server. THe message is being written into my logs on the server.
> MSSQL Error Msg 3621 The statement has been terminated
> THis is then followed by the information message
> Connected to DB
> THis continues in a over and over again. My DB was working
> fine and I could use the query analyzer, now however I cannot
> query anything in the DB.
> Any help would be great. I really dont want to reinstall this
> as a solution.
> TIA
> dogdog
|||On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:

> This message is usually preceded by another message indicating the cause the
> error. Are these messages in the SQL Server error log or in a log generated
> by your application?
The next message after the error 3621 is Statement has been terminated
and is then followed by an information message
stating "connected to db" This sequence just keeps going and going
over and over.
Hope that helps. Because it means absolutely nothing to me.
tks
dogdog
|||So these messages are in a log generated by your application? In that case,
it appears your application is reporting only the 3621 warning message and
not the preceding error that caused the statement to be terminated.
For example, below are the messages that are displayed by Query Analyzer
when I get a primary key violation:
Server: Msg 2627, Level 14, State 1, Line 1
Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key
in object 'Table1'.
The statement has been terminated.
If you have no control over the application logging behavior, I suggest you
run a Profiler trace to capture error events. This should help you identify
the problem SQL statements.
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.20.57.13.800017@.noemail.com...
> On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:
>
> The next message after the error 3621 is Statement has been terminated
> and is then followed by an information message
> stating "connected to db" This sequence just keeps going and going
> over and over.
> Hope that helps. Because it means absolutely nothing to me.
> tks
> dogdog
|||On Sun, 26 Mar 2006 06:27:38 +0000, Dan Guzman wrote:
First off thanks for taking your time on this and explaining things to
me a novice with mssql.

> So these messages are in a log generated by your application? In that case,
> it appears your application is reporting only the 3621 warning message and
> not the preceding error that caused the statement to be terminated.
>
Yes they are being written to the system log by the mssql server. I
guess that was the best idea for this setup rather than having numerous
logs.

> For example, below are the messages that are displayed by Query Analyzer
> when I get a primary key violation:
> Server: Msg 2627, Level 14, State 1, Line 1
> Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key
> in object 'Table1'.
> The statement has been terminated.
> If you have no control over the application logging behavior, I suggest you
> run a Profiler trace to capture error events. This should help you identify
> the problem SQL statements.
It seems as if the last query ran is "stuck" for lack of a better
understanding and just keeps querying. So it runs (without user
interaction for some reason) then reports the Error 3621 Statement
has been terminated. Then waits and reconnects to the server and
does it again. Seems crazy but I didnt make this stuff and it
makes it really hard to figure out when you inherit something like
this. Unfortunately there are no other logs to help in troubleshooting
and I want to avoid reinstalling the entire database. Luckily it
just came online and we just started testing it (i.e. sending
queries on test data) so if it does come down to reloading there
will be nothing lost. I just want to avoid that.
Thanks again for your help. If you have any other ideas I'll be glad
to try them out. I'm going to give the Profiler trace idea a shot.
Hopefully it will lead to something.

Error 3621

For some reason I'm getting the following error on my MS2000 MSSQl
server. THe message is being written into my logs on the server.
MSSQL Error Msg 3621 The statement has been terminated
THis is then followed by the information message
Connected to DB
THis continues in a over and over again. My DB was working
fine and I could use the query analyzer, now however I cannot
query anything in the DB.
Any help would be great. I really dont want to reinstall this
as a solution.
TIA
dogdogThis message is usually preceded by another message indicating the cause the
error. Are these messages in the SQL Server error log or in a log generated
by your application?
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.15.15.20.194339@.noemail.com...
> For some reason I'm getting the following error on my MS2000 MSSQl
> server. THe message is being written into my logs on the server.
> MSSQL Error Msg 3621 The statement has been terminated
> THis is then followed by the information message
> Connected to DB
> THis continues in a over and over again. My DB was working
> fine and I could use the query analyzer, now however I cannot
> query anything in the DB.
> Any help would be great. I really dont want to reinstall this
> as a solution.
> TIA
> dogdog|||On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:

> This message is usually preceded by another message indicating the cause t
he
> error. Are these messages in the SQL Server error log or in a log generat
ed
> by your application?
The next message after the error 3621 is Statement has been terminated
and is then followed by an information message
stating "connected to db" This sequence just keeps going and going
over and over.
Hope that helps. Because it means absolutely nothing to me.
tks
dogdog|||So these messages are in a log generated by your application? In that case,
it appears your application is reporting only the 3621 warning message and
not the preceding error that caused the statement to be terminated.
For example, below are the messages that are displayed by Query Analyzer
when I get a primary key violation:
Server: Msg 2627, Level 14, State 1, Line 1
Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate key
in object 'Table1'.
The statement has been terminated.
If you have no control over the application logging behavior, I suggest you
run a Profiler trace to capture error events. This should help you identify
the problem SQL statements.
Hope this helps.
Dan Guzman
SQL Server MVP
<dogdog@.noemail.com> wrote in message
news:pan.2006.03.25.20.57.13.800017@.noemail.com...
> On Sat, 25 Mar 2006 09:32:12 +0000, Dan Guzman wrote:
>
> The next message after the error 3621 is Statement has been terminated
> and is then followed by an information message
> stating "connected to db" This sequence just keeps going and going
> over and over.
> Hope that helps. Because it means absolutely nothing to me.
> tks
> dogdog|||On Sun, 26 Mar 2006 06:27:38 +0000, Dan Guzman wrote:
First off thanks for taking your time on this and explaining things to
me a novice with mssql.

> So these messages are in a log generated by your application? In that cas
e,
> it appears your application is reporting only the 3621 warning message and
> not the preceding error that caused the statement to be terminated.
>
Yes they are being written to the system log by the mssql server. I
guess that was the best idea for this setup rather than having numerous
logs.

> For example, below are the messages that are displayed by Query Analyzer
> when I get a primary key violation:
> Server: Msg 2627, Level 14, State 1, Line 1
> Violation of PRIMARY KEY constraint 'PK_Table1'. Cannot insert duplicate k
ey
> in object 'Table1'.
> The statement has been terminated.
> If you have no control over the application logging behavior, I suggest yo
u
> run a Profiler trace to capture error events. This should help you identi
fy
> the problem SQL statements.
It seems as if the last query ran is "stuck" for lack of a better
understanding and just keeps querying. So it runs (without user
interaction for some reason) then reports the Error 3621 Statement
has been terminated. Then waits and reconnects to the server and
does it again. Seems crazy but I didnt make this stuff and it
makes it really hard to figure out when you inherit something like
this. Unfortunately there are no other logs to help in troubleshooting
and I want to avoid reinstalling the entire database. Luckily it
just came online and we just started testing it (i.e. sending
queries on test data) so if it does come down to reloading there
will be nothing lost. I just want to avoid that.
Thanks again for your help. If you have any other ideas I'll be glad
to try them out. I'm going to give the Profiler trace idea a shot.
Hopefully it will lead to something.

Error 25 invalid connection string

here is the string:
Data Source=.\MSSQLSERVER;AttachDbFilename="C:\Program Files\Microsoft
SQL Server\MSSQL.1\MSSQL\Data\AdventureWorks_Data.mdf" ;Integrated
Security=True;Connect Timeout=30;User Instance=True
i am trying to connect visuyal c# express with sql server 2005 develop
edition
Can someone point what is wrong with my connection string
Try adding the "Initial Catalog=AdventureWorks" key-value pair. What's the
exception message?
See Chapter 9.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"pierre" <pf@.arobas.net> wrote in message
news:uEARym9THHA.4928@.TK2MSFTNGP03.phx.gbl...
> here is the string:
> Data Source=.\MSSQLSERVER;AttachDbFilename="C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\AdventureWorks_Data.mdf" ;Integrated
> Security=True;Connect Timeout=30;User Instance=True
> i am trying to connect visuyal c# express with sql server 2005 develop
> edition
> Can someone point what is wrong with my connection string