Welcome to dbFreaks.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Can't See Database In SQL 2005 MSE

 
   Database Help (Home) -> General Discussions RSS
Next:  subdata & etc  
Author Message
Neil

External


Since: Dec 29, 2008
Posts: 20



(Msg. 1) Posted: Mon Dec 29, 2008 5:14 am
Post subject: Can't See Database In SQL 2005 MSE
Archived from groups: comp>databases>ms-sqlserver, others (more info?)

I just upgraded from SQL 7 to SQL 2005 (Express) on my development machine,
and am having some trouble seeing my database. The database is functioning,
and I'm able to access the data through my front end (MS Access). Also, if I
open my copy of EM from SQL 7, I can see the database listed there, and can
open tables and so forth. But when I open Management Studio Express, all I
see listed are System Databases.

When I installed 2005 I selected the option to allow multiple instances of
SQL Server (thus, my server is "D10\SQLEXPRESS" instead of just the machine
name "D10"). I really don't need that, and I should have just gone with the
default instance. I'm wondering if that has anything to do with not being
able to see my database.

So my questions are:

1) How can see my database in MSE?

2) Is there any harm to using EM from SQL 7?

3) Can I restore my setup to just use the default instance, instead of
allowing named instances (or is there a real advantage to allowing named
instances of the server)?

Thanks so much!

Neil

 >> Stay informed about: Can't See Database In SQL 2005 MSE 
Back to top
Login to vote
Andrea Montanari

External


Since: Sep 13, 2003
Posts: 498



(Msg. 2) Posted: Mon Dec 29, 2008 7:25 am
Post subject: Re: Can't See Database In SQL 2005 MSE [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

hi Neil,
Neil wrote:
> ...
> So my questions are:
> 1) How can see my database in MSE?

I can think you did not upgrade your SQL Server 7.0 instance to SQLExpress
2005.. you just installed a named instance of it.. thus, your SQL Server 7.0
database still is on it.. you can back it up and restore it on the
SQLExpress instance..

>
> 2) Is there any harm to using EM from SQL 7?
EM (both 7.0 and 2000) can not handle and can not connect to SQL Server
2005..

> 3) Can I restore my setup to just use the default instance, instead of
> allowing named instances (or is there a real advantage to allowing
> named instances of the server)?
to see wether you are entitled to just upgrade your SQL Server 7.0 instance
to a SQLExpress 2005 one you have to check the upgrade matrix as proposed in
http://msdn.microsoft.com/en-us/library/ms143393(SQL.90).aspx ..
but you can (if you like) for sure uninstall SQL Server 7.0 and install a
fresh default instance of SQLExpress 2005, removing then the named instance
you already installed..

> When I installed 2005 I selected the option to allow multiple
> instances of SQL Server (thus, my server is "D10\SQLEXPRESS" instead
> of just the machine name "D10"). I really don't need that, and I
> should have just gone with the default instance
it's not in these terms.. you do not have to install the "multipli instances
option" as there is not such an option.. up to SQL Server 2000 you can, if
you like, install many of them (usually up to 16 but this limit depends on
the edition and, of course, on your machine power).. so you just installed a
named instance and there's no problem with it..
regards and happy new year
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://www.hotelsole.com
DbaMgr2k ver 0.21.1 - DbaMgr ver 0.65.1 and further SQL Tools
--------- remove DMO to reply

 >> Stay informed about: Can't See Database In SQL 2005 MSE 
Back to top
Login to vote
Neil

External


Since: Dec 29, 2008
Posts: 20



(Msg. 3) Posted: Mon Dec 29, 2008 9:23 am
Post subject: Re: Can't See Database In SQL 2005 MSE [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

"Andrea Montanari" wrote in message

> hi Neil,
> Neil wrote:
>> ...
>> So my questions are:
>> 1) How can see my database in MSE?
>
> I can think you did not upgrade your SQL Server 7.0 instance to SQLExpress
> 2005.. you just installed a named instance of it.. thus, your SQL Server
> 7.0 database still is on it.. you can back it up and restore it on the
> SQLExpress instance..
>
>>
>> 2) Is there any harm to using EM from SQL 7?
> EM (both 7.0 and 2000) can not handle and can not connect to SQL Server
> 2005..
>
>> 3) Can I restore my setup to just use the default instance, instead of
>> allowing named instances (or is there a real advantage to allowing
>> named instances of the server)?
> to see wether you are entitled to just upgrade your SQL Server 7.0
> instance to a SQLExpress 2005 one you have to check the upgrade matrix as
> proposed in http://msdn.microsoft.com/en-us/library/ms143393(SQL.90).aspx
> ..
> but you can (if you like) for sure uninstall SQL Server 7.0 and install a
> fresh default instance of SQLExpress 2005, removing then the named
> instance you already installed..
>
>> When I installed 2005 I selected the option to allow multiple
>> instances of SQL Server (thus, my server is "D10\SQLEXPRESS" instead
>> of just the machine name "D10"). I really don't need that, and I
>> should have just gone with the default instance
> it's not in these terms.. you do not have to install the "multipli
> instances option" as there is not such an option.. up to SQL Server 2000
> you can, if you like, install many of them (usually up to 16 but this
> limit depends on the edition and, of course, on your machine power).. so
> you just installed a named instance and there's no problem with it..
> regards and happy new year
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://www.hotelsole.com
> DbaMgr2k ver 0.21.1 - DbaMgr ver 0.65.1 and further SQL Tools
> --------- remove DMO to reply

Thanks, Andrea. I was a little unclear in my last message. When I said SQL
7, I meant SQL 7 MSDE. So the upgrade is to the same version.

I'm a little unclear of something. Are you saying that I currently have two
versions of SQL Server running -- my original SQL 7 MSDE and the new SQL
2005 Express, which is why I can see the database using SQL 7 EM, but not
SQL 2005 Express?

And, if so, then if I back up the database in SQL 7 and restore it in SQL
2005, then would I have two instances of the database running -- one in 7
and one in 2005?

I must be missing something here.

Thanks,

Neil
 >> Stay informed about: Can't See Database In SQL 2005 MSE 
Back to top
Login to vote
Neil

External


Since: Dec 29, 2008
Posts: 20



(Msg. 4) Posted: Mon Dec 29, 2008 9:44 am
Post subject: Re: Can't See Database In SQL 2005 MSE [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

"Andrea Montanari" wrote in message

> hi Neil,
> Neil wrote:
>> ...
>> So my questions are:
>> 1) How can see my database in MSE?
>
> I can think you did not upgrade your SQL Server 7.0 instance to SQLExpress
> 2005.. you just installed a named instance of it.. thus, your SQL Server
> 7.0 database still is on it.. you can back it up and restore it on the
> SQLExpress instance..
>
>>
>> 2) Is there any harm to using EM from SQL 7?
> EM (both 7.0 and 2000) can not handle and can not connect to SQL Server
> 2005..
>
>> 3) Can I restore my setup to just use the default instance, instead of
>> allowing named instances (or is there a real advantage to allowing
>> named instances of the server)?
> to see wether you are entitled to just upgrade your SQL Server 7.0
> instance to a SQLExpress 2005 one you have to check the upgrade matrix as
> proposed in http://msdn.microsoft.com/en-us/library/ms143393(SQL.90).aspx
> ..
> but you can (if you like) for sure uninstall SQL Server 7.0 and install a
> fresh default instance of SQLExpress 2005, removing then the named
> instance you already installed..
>
>> When I installed 2005 I selected the option to allow multiple
>> instances of SQL Server (thus, my server is "D10\SQLEXPRESS" instead
>> of just the machine name "D10"). I really don't need that, and I
>> should have just gone with the default instance
> it's not in these terms.. you do not have to install the "multipli
> instances option" as there is not such an option.. up to SQL Server 2000
> you can, if you like, install many of them (usually up to 16 but this
> limit depends on the edition and, of course, on your machine power).. so
> you just installed a named instance and there's no problem with it..
> regards and happy new year
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://www.hotelsole.com
> DbaMgr2k ver 0.21.1 - DbaMgr ver 0.65.1 and further SQL Tools
> --------- remove DMO to reply

OK, never mind the previous message. I think I got it. Because I did a named
instance of 2005, it didn't upgrade 7; just added another instance. And my
db was still running in 7. It can't run in both versions of SQL
simultaneously; but it can run in one or the other.

I attached the MDF to SQL 2005, and it's in there now; but SQL7 EM can't
access it. So that's good.

However, because my DSN is set to look for the data in D10, not
D10/SQLExpress, it fails. So I can either change the DSN, or remove the
named instance. So if I reinstall SQL 2005 with the default instance, it
should upgrade SQL 7, and I should be set, no?

Thanks,

Neil
 >> Stay informed about: Can't See Database In SQL 2005 MSE 
Back to top
Login to vote
Ekrem_Önsoy

External


Since: Jan 11, 2008
Posts: 267



(Msg. 5) Posted: Mon Dec 29, 2008 11:26 am
Post subject: Re: Can't See Database In SQL 2005 MSE [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Why don't you just uninstall your old 7.0 instance and install a new SQL
Server 2005 Express Edition instance as a Default Instance and then detach
your database from your new 2005 Named instance and attach it to your new
2005 Default Instance?

Don't forget to configure TCP/IP or Named Pipes protocols so that your
network users is able to connect to your new SQL Server 2005 instance if you
have any.

--
Ekrem Önsoy




"Neil" wrote in message

>
> "Andrea Montanari" wrote in message
>
>> hi Neil,
>> Neil wrote:
>>> ...
>>> So my questions are:
>>> 1) How can see my database in MSE?
>>
>> I can think you did not upgrade your SQL Server 7.0 instance to
>> SQLExpress 2005.. you just installed a named instance of it.. thus, your
>> SQL Server 7.0 database still is on it.. you can back it up and restore
>> it on the SQLExpress instance..
>>
>>>
>>> 2) Is there any harm to using EM from SQL 7?
>> EM (both 7.0 and 2000) can not handle and can not connect to SQL Server
>> 2005..
>>
>>> 3) Can I restore my setup to just use the default instance, instead of
>>> allowing named instances (or is there a real advantage to allowing
>>> named instances of the server)?
>> to see wether you are entitled to just upgrade your SQL Server 7.0
>> instance to a SQLExpress 2005 one you have to check the upgrade matrix as
>> proposed in http://msdn.microsoft.com/en-us/library/ms143393(SQL.90).aspx
>> ..
>> but you can (if you like) for sure uninstall SQL Server 7.0 and install a
>> fresh default instance of SQLExpress 2005, removing then the named
>> instance you already installed..
>>
>>> When I installed 2005 I selected the option to allow multiple
>>> instances of SQL Server (thus, my server is "D10\SQLEXPRESS" instead
>>> of just the machine name "D10"). I really don't need that, and I
>>> should have just gone with the default instance
>> it's not in these terms.. you do not have to install the "multipli
>> instances option" as there is not such an option.. up to SQL Server 2000
>> you can, if you like, install many of them (usually up to 16 but this
>> limit depends on the edition and, of course, on your machine power).. so
>> you just installed a named instance and there's no problem with it..
>> regards and happy new year
>> --
>> Andrea Montanari (Microsoft MVP - SQL Server)
>> http://www.asql.biz http://www.hotelsole.com
>> DbaMgr2k ver 0.21.1 - DbaMgr ver 0.65.1 and further SQL Tools
>> --------- remove DMO to reply
>
> OK, never mind the previous message. I think I got it. Because I did a
> named instance of 2005, it didn't upgrade 7; just added another instance.
> And my db was still running in 7. It can't run in both versions of SQL
> simultaneously; but it can run in one or the other.
>
> I attached the MDF to SQL 2005, and it's in there now; but SQL7 EM can't
> access it. So that's good.
>
> However, because my DSN is set to look for the data in D10, not
> D10/SQLExpress, it fails. So I can either change the DSN, or remove the
> named instance. So if I reinstall SQL 2005 with the default instance, it
> should upgrade SQL 7, and I should be set, no?
>
> Thanks,
>
> Neil
>
 >> Stay informed about: Can't See Database In SQL 2005 MSE 
Back to top
Login to vote
Fabio M. ROSSETTI

External


Since: Jan 01, 2009
Posts: 1



(Msg. 6) Posted: Thu Jan 01, 2009 6:25 am
Post subject: Re: Can't See Database In SQL 2005 MSE [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Neil wrote:

> So my questions are:
>
> 1) How can see my database in MSE?

You can't.. If I remember correctly Query Analyzer still works, but no
MSE. Install Sql Server Management Studio Express (free download,
requires .NET 2.0), it roughly comprises the basic functionality of
MSE+QA. Also, use the Server Surface Area Configuration tool to enable
local AND remote connection via tcp/ip, if necessary.
 >> Stay informed about: Can't See Database In SQL 2005 MSE 
Back to top
Login to vote
Neil

External


Since: Dec 29, 2008
Posts: 20



(Msg. 7) Posted: Thu Jan 01, 2009 10:52 am
Post subject: Re: Can't See Database In SQL 2005 MSE [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Yeah, I ended up having to uninstall SQL 7. The install program wouldn't
upgrade SQL 7 to a default instance, saying everything's already installed.
Once I uninstalled SQL 7, I was able to install the default instance.


"Ekrem Önsoy" wrote in message

> Why don't you just uninstall your old 7.0 instance and install a new SQL
> Server 2005 Express Edition instance as a Default Instance and then detach
> your database from your new 2005 Named instance and attach it to your new
> 2005 Default Instance?
>
> Don't forget to configure TCP/IP or Named Pipes protocols so that your
> network users is able to connect to your new SQL Server 2005 instance if
> you have any.
>
> --
> Ekrem Önsoy
>
>
>
>
> "Neil" wrote in message
>
>>
>> "Andrea Montanari" wrote in message
>>
>>> hi Neil,
>>> Neil wrote:
>>>> ...
>>>> So my questions are:
>>>> 1) How can see my database in MSE?
>>>
>>> I can think you did not upgrade your SQL Server 7.0 instance to
>>> SQLExpress 2005.. you just installed a named instance of it.. thus, your
>>> SQL Server 7.0 database still is on it.. you can back it up and restore
>>> it on the SQLExpress instance..
>>>
>>>>
>>>> 2) Is there any harm to using EM from SQL 7?
>>> EM (both 7.0 and 2000) can not handle and can not connect to SQL Server
>>> 2005..
>>>
>>>> 3) Can I restore my setup to just use the default instance, instead of
>>>> allowing named instances (or is there a real advantage to allowing
>>>> named instances of the server)?
>>> to see wether you are entitled to just upgrade your SQL Server 7.0
>>> instance to a SQLExpress 2005 one you have to check the upgrade matrix
>>> as proposed in
>>> http://msdn.microsoft.com/en-us/library/ms143393(SQL.90).aspx ..
>>> but you can (if you like) for sure uninstall SQL Server 7.0 and install
>>> a fresh default instance of SQLExpress 2005, removing then the named
>>> instance you already installed..
>>>
>>>> When I installed 2005 I selected the option to allow multiple
>>>> instances of SQL Server (thus, my server is "D10\SQLEXPRESS" instead
>>>> of just the machine name "D10"). I really don't need that, and I
>>>> should have just gone with the default instance
>>> it's not in these terms.. you do not have to install the "multipli
>>> instances option" as there is not such an option.. up to SQL Server 2000
>>> you can, if you like, install many of them (usually up to 16 but this
>>> limit depends on the edition and, of course, on your machine power).. so
>>> you just installed a named instance and there's no problem with it..
>>> regards and happy new year
>>> --
>>> Andrea Montanari (Microsoft MVP - SQL Server)
>>> http://www.asql.biz http://www.hotelsole.com
>>> DbaMgr2k ver 0.21.1 - DbaMgr ver 0.65.1 and further SQL Tools
>>> --------- remove DMO to reply
>>
>> OK, never mind the previous message. I think I got it. Because I did a
>> named instance of 2005, it didn't upgrade 7; just added another instance.
>> And my db was still running in 7. It can't run in both versions of SQL
>> simultaneously; but it can run in one or the other.
>>
>> I attached the MDF to SQL 2005, and it's in there now; but SQL7 EM can't
>> access it. So that's good.
>>
>> However, because my DSN is set to look for the data in D10, not
>> D10/SQLExpress, it fails. So I can either change the DSN, or remove the
>> named instance. So if I reinstall SQL 2005 with the default instance, it
>> should upgrade SQL 7, and I should be set, no?
>>
>> Thanks,
>>
>> Neil
>>
>
 >> Stay informed about: Can't See Database In SQL 2005 MSE 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
How to deploy a database on SQL Server Express 2005 - Hello Hopefully a really simple question. We have just finsihed a SQL 2005 database and vb.net app. We have been using SQL server 2005 Management Studio during design. We now want to copy the database across to a machine that has only got SQL server..

SQL Server 2005 with VB.net 2005 - Hi every body, Im using VB 2005 to create a program that open SQL Data base The problem that i want to detect the tables of a database so how can i know a data base tables instantly Thank you omar.abid@hotmail.com omar.abid2006@gmail.com Omar abid

Database Compare,Data Compare tool,sort sync scipts with d.. - DBC (Database Compare) is a fast, comprehensive database structure and data comparison tool.Sort sync scipts with database dependencies. www.d-softs.com

Constipated publisher (SQL 2005) - We have a 2005 Publisher that is publishing to one 2005 subscriber and two 2000 subscribers. It's been fine, but yesterday I had to import some data into one of the tables that is being published. The data isn't huge in terms of number of rows (less tha...

SQL 2005 XML Searching - hi i have a table with an XML column this XML data looks like this <details><attribute id="1" value="x"/><attribute id="2" value="y"/ ><attribute id="3" value="z"/><...
   Database Help (Home) -> General Discussions All times are: Pacific Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]