Wrox Programmer Forums

Need to download code?

View our list of code downloads.

| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Beginning ASP.NET 2.0 BOOK VB ISBN: 978-0-7645-8850-1; C# ISBN: 978-0-470-04258-8
This is the forum to discuss the Wrox book Beginning ASP.NET 2.0 by Chris Hart, John Kauffman, David Sussman, Chris Ullman; ISBN: 9780764588501
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Beginning ASP.NET 2.0 BOOK VB ISBN: 978-0-7645-8850-1; C# ISBN: 978-0-470-04258-8 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
 
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old February 1st, 2006, 11:41 AM
Authorized User
 
Join Date: Feb 2006
Location: Houston, Texas, USA.
Posts: 10
Thanks: 0
Thanked 0 Times in 0 Posts
Default SQL Server conflicts?

Hello - will installing SQL Server 2005 Express conflict with my existing SQL Server 2000 installation?

Thanks

Mark

  #2 (permalink)  
Old February 1st, 2006, 11:51 AM
Authorized User
 
Join Date: Dec 2003
Location: , , United Kingdom.
Posts: 46
Thanks: 0
Thanked 1 Time in 1 Post
Default

Nope, they run side-by-side fine (I have SQL 2005, 2005 and express on my machine). This is handled by each having a separate instance. The first server you isntall is generally the default instance (although you can give it an explicit name), and subsequent ones have to have explicit names. The full name of a server is machine\instance, so mine are TIGGER, TIGGER\SQL2005, TIGGER\SQLEXPRESS (all of my machines are named after Winne the Pooh characters). When .NET 2.0 is installed, the SQL Express instance is explicitly name SQLEXPRESS.

This explains why, when you look at connection strings, you see things like .\SQLEXPRESS or localhost\SQLEXPRESS. Both . and localhost refer to the current server, allowing you to have a named SQL instance without worrying about the actual name of the machine.

Dave

  #3 (permalink)  
Old February 1st, 2006, 12:25 PM
Authorized User
 
Join Date: Feb 2006
Location: Houston, Texas, USA.
Posts: 10
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Great!

Thanks, Dave

 


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Conflict in SQL Server 2000 and SQL Server 2005 ayan.mukherjee SQL Language 0 June 30th, 2008 03:34 AM
SQL Server Reg. SQL Server does not exist error Arsi SQL Server 2000 1 June 11th, 2008 11:20 AM
migrating from sql server 2000 to sql server 2005 abinashpatra SQL Server 2005 2 December 1st, 2006 03:45 PM
Browser conflicts I suppose . . . Ross McVinnie Intro Programming 0 July 10th, 2006 05:32 PM
Sql Character Conflicts tbi_cp SQL Language 2 August 19th, 2004 05:08 PM



All times are GMT -4. The time now is 03:23 PM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.