BugNET

Open source issue tracking & project management
Welcome to BugNET Register | Login |

BugNET Forums

 
  Forum  Support  Installation pr...  SQL 2005 instead of SQL 2000
Previous Previous
 
Next Next
New Post 3/29/2007 12:31 PM
User is offline admin
645 posts
bugnetproject.com
1st Level Poster




Re: SQL 2005 instead of SQL 2000 
 ravensensei wrote
 Davin wrote
It might have installed as an instance  local\instancename.

Why not just use the sql 2005?


I don't have any way to administer SQL 2005.  Does it automatically install when you have Windows 2003?


If you using sql 2005 express you can get sql server management studio express (same as enterprise manager in 2000) free from microsoft and if you have the full version you should already have the management tool installed.

Davin Dubeau
BugNET - Core Developer

 
New Post 3/29/2007 2:18 PM
User is offline ravensensei
4 posts
No Ranking


Re: SQL 2005 instead of SQL 2000 

 Davin wrote
If you using sql 2005 express you can get sql server management studio express (same as enterprise manager in 2000) free from microsoft and if you have the full version you should already have the management tool installed.

If I wanted to point to sql 2000, what does the connection string look like as opposed to sql 2005?  The weird thing is, I uninstalled SQL 2005, and its still giving that error when I install.  It was an install that came with Sharepoint demo I was playing with.  Don't even get my started on how much of a pain that caused :)

Could you give me an example of what a conn string would look like for both?

This is what I have in the web.config - <add name="LocalSqlServer" connectionString="Data Source=server;Initial Catalog=BugNet;User Id=bugnet;Password=bugnet;" />

 
New Post 3/29/2007 11:24 PM
User is offline cgraefe
54 posts
No Ranking


Re: SQL 2005 instead of SQL 2000 
Hi,

1.) If you don't have any administration tool for your sql server 2000/2005, then just go ahead to MSSMSE and install the Management Studio.
2.) Just open a cmd.exe and type "net start", if your sql server is started you can see it in this list ---> example
    If there is a name like SQLExpress after the service name, the sql server is installed as an instance.
3.) Start the MSSMSE from point 1.) with lokal administrator rights and prepare your installation like described in the docs --> here
     - use windows authentication for administration
     - if you have an instance name you have to connect to  servername\instancename like localhost\SQLEXPRESS.

I hope this helps.

regards
Christian
 
Previous Previous
 
Next Next
  Forum  Support  Installation pr...  SQL 2005 instead of SQL 2000

Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.