Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Setup / March 2006

Tip: Looking for answers? Try searching our database.

Vs2005 and Sql2005 developer

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
H. Edgar - 22 Feb 2006 08:55 GMT
This is already handled in different threads. But I read different
conclusions in different threads.
In a development PC I have already sql2000 developer and VsNet2003. I want
to install now SQL2005 developer and VS2005 Team suite.

The Team Suite setup offers the option to install SQL2000 express but not
the option to install SQL2005 developer. Is it necesary to install SQL2005
Developer first? Alternativelly, can I clear the selection SQL2005 Express
and install SQL2005 Developer later?

I don't know, if the Team Suite need the SQL 2005 to install any
functionality. Is there a VS2005 setup with the SQL developer instead?.

Thanks, H.Edgar
H. Edgar - 23 Feb 2006 08:08 GMT
I installed now VS 2005 Team Suite with sql Express. As this is a named
instance, i want to intall sql 2005 developer later.

But now i do not see the SQL Servers and the SQLEXPRESS instance with the
Vs2005 Server Explorer. What would be wrong?

I can see the SQLEXPRESS instance with the VS2003 Server Explorer without
problem.

Edgar

> This is already handled in different threads. But I read different
> conclusions in different threads.
[quoted text clipped - 10 lines]
>
> Thanks, H.Edgar
alex - 17 Mar 2006 19:20 GMT
Hi Edgar.
I have the same problem.
I also anoticed that the VS2005 Server Explor is unable to read the
description of the Event Log entries.
Does it happen also to you? If yes please let me know. I think the two
problems are related ( by the fact that it seems that only the node Server
is unable to view the SQLServer instances and the log entries).
I tried to uninstall VS2005 and reinstall from a "clean" boot (managed
through msconfig), but the result is the same.

Best regards
Alex
[from Italy, hoping my english will work]

>I installed now VS 2005 Team Suite with sql Express. As this is a named
>instance, i want to intall sql 2005 developer later.
[quoted text clipped - 21 lines]
>>
>> Thanks, H.Edgar
H. Edgar - 26 Mar 2006 16:50 GMT
Hi Alex,

I do not know the issue about the Event log entries. But I think, the SQL
Servers nodes is not bein displayed by design in VS2005. In order to  see
any server a data connection fpr the server has to be created.

I dont know if this is a managed new group. I hoped Microsoft would answer
to this question.

Edgar

> Hi Edgar.
> I have the same problem.
[quoted text clipped - 35 lines]
>>>
>>> Thanks, H.Edgar
alex - 30 Mar 2006 17:55 GMT
Hi Edgar.

I found that the Event log entries issue was caused by another problem ( my
PC is multihosted and a missing DNS configuration of the domain interface
caused the problem).

Documentation says SQL Server node should be displayed under Server. I
really don't know (I suspect a permission related issue).
As soon as I've news about it I'll reply to this message.

Thanks for your response.

Alex

> Hi Alex,
>
[quoted text clipped - 46 lines]
>>>>
>>>> Thanks, H.Edgar

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.