I have 4 small small SQL 2000 databases that I need to consolidate to a
single machine.
The data is minimal maybe 100 GB total with an expection of some
moderate growth.
The box will be configured with a raid 5.
Question:
Should the O.S and each instance be on its own partition?
Or would it be better to have the instances on one partition and
dedicate a partition for the data and log files?
Any inforomation would be greatly appreciated.
Thanks,
Hulicat
I would investigate if the four database could reside in the same server.
(Perhaps because of security or other needs, that is not possible.)
If you have to have 'separate' servers, install multiple instances of SQL
Server on the same box. All instances will use the same OS -the only thing
being 'duplicated' is SQL Server instances (code, settings, etc.)
Drives.
Best choice: RAID 1 for OS and SQL installables (2 drives). RAID 10 for data
files (4 drives). RAID 10 for Logs files (4 drives). For optimal
performance, each instance 'should' have its own drives for data and logs.
I wouldn't recommend trying to make everything work with a single RAID 5.
That would be painful.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1162403869.339729.318940@.e64g2000cwd.googlegr oups.com...
>I have 4 small small SQL 2000 databases that I need to consolidate to a
> single machine.
> The data is minimal maybe 100 GB total with an expection of some
> moderate growth.
> The box will be configured with a raid 5.
> Question:
> Should the O.S and each instance be on its own partition?
> Or would it be better to have the instances on one partition and
> dedicate a partition for the data and log files?
> Any inforomation would be greatly appreciated.
> Thanks,
> Hulicat
>
|||~Thanks~
Arnie Rowland wrote:[vbcol=seagreen]
> I would investigate if the four database could reside in the same server.
> (Perhaps because of security or other needs, that is not possible.)
> If you have to have 'separate' servers, install multiple instances of SQL
> Server on the same box. All instances will use the same OS -the only thing
> being 'duplicated' is SQL Server instances (code, settings, etc.)
> Drives.
> Best choice: RAID 1 for OS and SQL installables (2 drives). RAID 10 for data
> files (4 drives). RAID 10 for Logs files (4 drives). For optimal
> performance, each instance 'should' have its own drives for data and logs.
> I wouldn't recommend trying to make everything work with a single RAID 5.
> That would be painful.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
> "Hulicat" <dennis_A_white@.yahoo.com> wrote in message
> news:1162403869.339729.318940@.e64g2000cwd.googlegr oups.com...
Showing posts with label databases. Show all posts
Showing posts with label databases. Show all posts
Friday, March 30, 2012
Installing Multiple Instances Design Question
I have 4 small small SQL 2000 databases that I need to consolidate to a
single machine.
The data is minimal maybe 100 GB total with an expection of some
moderate growth.
The box will be configured with a raid 5.
Question:
Should the O.S and each instance be on its own partition?
Or would it be better to have the instances on one partition and
dedicate a partition for the data and log files?
Any inforomation would be greatly appreciated.
Thanks,
HulicatI would investigate if the four database could reside in the same server.
(Perhaps because of security or other needs, that is not possible.)
If you have to have 'separate' servers, install multiple instances of SQL
Server on the same box. All instances will use the same OS -the only thing
being 'duplicated' is SQL Server instances (code, settings, etc.)
Drives.
Best choice: RAID 1 for OS and SQL installables (2 drives). RAID 10 for data
files (4 drives). RAID 10 for Logs files (4 drives). For optimal
performance, each instance 'should' have its own drives for data and logs.
I wouldn't recommend trying to make everything work with a single RAID 5.
That would be painful.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1162403869.339729.318940@.e64g2000cwd.googlegroups.com...
>I have 4 small small SQL 2000 databases that I need to consolidate to a
> single machine.
> The data is minimal maybe 100 GB total with an expection of some
> moderate growth.
> The box will be configured with a raid 5.
> Question:
> Should the O.S and each instance be on its own partition?
> Or would it be better to have the instances on one partition and
> dedicate a partition for the data and log files?
> Any inforomation would be greatly appreciated.
> Thanks,
> Hulicat
>|||~Thanks~
Arnie Rowland wrote:[vbcol=seagreen]
> I would investigate if the four database could reside in the same server.
> (Perhaps because of security or other needs, that is not possible.)
> If you have to have 'separate' servers, install multiple instances of SQL
> Server on the same box. All instances will use the same OS -the only thing
> being 'duplicated' is SQL Server instances (code, settings, etc.)
> Drives.
> Best choice: RAID 1 for OS and SQL installables (2 drives). RAID 10 for da
ta
> files (4 drives). RAID 10 for Logs files (4 drives). For optimal
> performance, each instance 'should' have its own drives for data and logs.
> I wouldn't recommend trying to make everything work with a single RAID 5.
> That would be painful.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to th
e
> top yourself.
> - H. Norman Schwarzkopf
>
> "Hulicat" <dennis_A_white@.yahoo.com> wrote in message
> news:1162403869.339729.318940@.e64g2000cwd.googlegroups.com...sql
single machine.
The data is minimal maybe 100 GB total with an expection of some
moderate growth.
The box will be configured with a raid 5.
Question:
Should the O.S and each instance be on its own partition?
Or would it be better to have the instances on one partition and
dedicate a partition for the data and log files?
Any inforomation would be greatly appreciated.
Thanks,
HulicatI would investigate if the four database could reside in the same server.
(Perhaps because of security or other needs, that is not possible.)
If you have to have 'separate' servers, install multiple instances of SQL
Server on the same box. All instances will use the same OS -the only thing
being 'duplicated' is SQL Server instances (code, settings, etc.)
Drives.
Best choice: RAID 1 for OS and SQL installables (2 drives). RAID 10 for data
files (4 drives). RAID 10 for Logs files (4 drives). For optimal
performance, each instance 'should' have its own drives for data and logs.
I wouldn't recommend trying to make everything work with a single RAID 5.
That would be painful.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1162403869.339729.318940@.e64g2000cwd.googlegroups.com...
>I have 4 small small SQL 2000 databases that I need to consolidate to a
> single machine.
> The data is minimal maybe 100 GB total with an expection of some
> moderate growth.
> The box will be configured with a raid 5.
> Question:
> Should the O.S and each instance be on its own partition?
> Or would it be better to have the instances on one partition and
> dedicate a partition for the data and log files?
> Any inforomation would be greatly appreciated.
> Thanks,
> Hulicat
>|||~Thanks~
Arnie Rowland wrote:[vbcol=seagreen]
> I would investigate if the four database could reside in the same server.
> (Perhaps because of security or other needs, that is not possible.)
> If you have to have 'separate' servers, install multiple instances of SQL
> Server on the same box. All instances will use the same OS -the only thing
> being 'duplicated' is SQL Server instances (code, settings, etc.)
> Drives.
> Best choice: RAID 1 for OS and SQL installables (2 drives). RAID 10 for da
ta
> files (4 drives). RAID 10 for Logs files (4 drives). For optimal
> performance, each instance 'should' have its own drives for data and logs.
> I wouldn't recommend trying to make everything work with a single RAID 5.
> That would be painful.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to th
e
> top yourself.
> - H. Norman Schwarzkopf
>
> "Hulicat" <dennis_A_white@.yahoo.com> wrote in message
> news:1162403869.339729.318940@.e64g2000cwd.googlegroups.com...sql
Installing Multiple Instances Design Question
I have 4 small small SQL 2000 databases that I need to consolidate to a
single machine.
The data is minimal maybe 100 GB total with an expection of some
moderate growth.
The box will be configured with a raid 5.
Question:
Should the O.S and each instance be on its own partition?
Or would it be better to have the instances on one partition and
dedicate a partition for the data and log files?
Any inforomation would be greatly appreciated.
Thanks,
HulicatI would investigate if the four database could reside in the same server.
(Perhaps because of security or other needs, that is not possible.)
If you have to have 'separate' servers, install multiple instances of SQL
Server on the same box. All instances will use the same OS -the only thing
being 'duplicated' is SQL Server instances (code, settings, etc.)
Drives.
Best choice: RAID 1 for OS and SQL installables (2 drives). RAID 10 for data
files (4 drives). RAID 10 for Logs files (4 drives). For optimal
performance, each instance 'should' have its own drives for data and logs.
I wouldn't recommend trying to make everything work with a single RAID 5.
That would be painful.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1162403869.339729.318940@.e64g2000cwd.googlegroups.com...
>I have 4 small small SQL 2000 databases that I need to consolidate to a
> single machine.
> The data is minimal maybe 100 GB total with an expection of some
> moderate growth.
> The box will be configured with a raid 5.
> Question:
> Should the O.S and each instance be on its own partition?
> Or would it be better to have the instances on one partition and
> dedicate a partition for the data and log files?
> Any inforomation would be greatly appreciated.
> Thanks,
> Hulicat
>|||~Thanks~
Arnie Rowland wrote:
> I would investigate if the four database could reside in the same server.
> (Perhaps because of security or other needs, that is not possible.)
> If you have to have 'separate' servers, install multiple instances of SQL
> Server on the same box. All instances will use the same OS -the only thing
> being 'duplicated' is SQL Server instances (code, settings, etc.)
> Drives.
> Best choice: RAID 1 for OS and SQL installables (2 drives). RAID 10 for data
> files (4 drives). RAID 10 for Logs files (4 drives). For optimal
> performance, each instance 'should' have its own drives for data and logs.
> I wouldn't recommend trying to make everything work with a single RAID 5.
> That would be painful.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
> "Hulicat" <dennis_A_white@.yahoo.com> wrote in message
> news:1162403869.339729.318940@.e64g2000cwd.googlegroups.com...
> >I have 4 small small SQL 2000 databases that I need to consolidate to a
> > single machine.
> > The data is minimal maybe 100 GB total with an expection of some
> > moderate growth.
> >
> > The box will be configured with a raid 5.
> >
> > Question:
> > Should the O.S and each instance be on its own partition?
> > Or would it be better to have the instances on one partition and
> > dedicate a partition for the data and log files?
> >
> > Any inforomation would be greatly appreciated.
> >
> > Thanks,
> > Hulicat
> >
single machine.
The data is minimal maybe 100 GB total with an expection of some
moderate growth.
The box will be configured with a raid 5.
Question:
Should the O.S and each instance be on its own partition?
Or would it be better to have the instances on one partition and
dedicate a partition for the data and log files?
Any inforomation would be greatly appreciated.
Thanks,
HulicatI would investigate if the four database could reside in the same server.
(Perhaps because of security or other needs, that is not possible.)
If you have to have 'separate' servers, install multiple instances of SQL
Server on the same box. All instances will use the same OS -the only thing
being 'duplicated' is SQL Server instances (code, settings, etc.)
Drives.
Best choice: RAID 1 for OS and SQL installables (2 drives). RAID 10 for data
files (4 drives). RAID 10 for Logs files (4 drives). For optimal
performance, each instance 'should' have its own drives for data and logs.
I wouldn't recommend trying to make everything work with a single RAID 5.
That would be painful.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1162403869.339729.318940@.e64g2000cwd.googlegroups.com...
>I have 4 small small SQL 2000 databases that I need to consolidate to a
> single machine.
> The data is minimal maybe 100 GB total with an expection of some
> moderate growth.
> The box will be configured with a raid 5.
> Question:
> Should the O.S and each instance be on its own partition?
> Or would it be better to have the instances on one partition and
> dedicate a partition for the data and log files?
> Any inforomation would be greatly appreciated.
> Thanks,
> Hulicat
>|||~Thanks~
Arnie Rowland wrote:
> I would investigate if the four database could reside in the same server.
> (Perhaps because of security or other needs, that is not possible.)
> If you have to have 'separate' servers, install multiple instances of SQL
> Server on the same box. All instances will use the same OS -the only thing
> being 'duplicated' is SQL Server instances (code, settings, etc.)
> Drives.
> Best choice: RAID 1 for OS and SQL installables (2 drives). RAID 10 for data
> files (4 drives). RAID 10 for Logs files (4 drives). For optimal
> performance, each instance 'should' have its own drives for data and logs.
> I wouldn't recommend trying to make everything work with a single RAID 5.
> That would be painful.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
> "Hulicat" <dennis_A_white@.yahoo.com> wrote in message
> news:1162403869.339729.318940@.e64g2000cwd.googlegroups.com...
> >I have 4 small small SQL 2000 databases that I need to consolidate to a
> > single machine.
> > The data is minimal maybe 100 GB total with an expection of some
> > moderate growth.
> >
> > The box will be configured with a raid 5.
> >
> > Question:
> > Should the O.S and each instance be on its own partition?
> > Or would it be better to have the instances on one partition and
> > dedicate a partition for the data and log files?
> >
> > Any inforomation would be greatly appreciated.
> >
> > Thanks,
> > Hulicat
> >
Wednesday, March 28, 2012
Installing Microsoft SQL server management studio express broke my asp.net databases
Morning, Cannot open user default database. Login failed.
I installed the managerment stuid on my machine and now none of my database connections seem to work any more. I keep getting the attached error. Before I installed the studio the system worked fine, I could connect to the database and everything was fine. Does the studio change any permission stuff? I cannot seem to get it to work again at all now, I added in aspnet as a login inside the studio and it still won't let me connect to the database. I cannot find *any* logs anywhere that might be helpful in what it is doing or see any way to debug the connection to find out what the problem is. When I look at the permissions inside of the studio it shows me that the connections should all be fine.
I checked and remote and local connections are setup, although it is only doing local connections anyway since this is a asp.net web server page.
Any idea what the problem is here? This is very frustrating and annoying :( Since I didn't change anything and now nothing I will do gets it to work. I even tried to uninstall the management tool and it still doesn't work.
Cannot open user default database. Login failed.
Login failed for user 'GREENANDFLUFFY\ASPNET'.
Description: An
unhandled exception occurred during the execution of the current web
request. Please review the stack trace for more information about the
error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Cannot open user default database. Login failed.
Login failed for user 'GREENANDFLUFFY\ASPNET'.
I have posted a solution (that works for me) here.
And there are other solutions in that older post.
|||Simply set the user dafault database for the user to a database which is existing and accessible to him, either with the procedure sp_defaultdb or via the management Studio.HTH, jens Suessmeyer.
http://www.sqlserver2005.de|||It was working just fine till I installed the management studio though. What could that possibly be doing to muck with the permissions?
I checked and the user has the default database as master and it definately has access to it. None of the other solutions on this page worked either.
I am really really really unimpressed with this current situation, it is a terrible user experience.|||Make also sure that the database mentioned in the connection string (depending on your provider you are using, for .NET it should be "Initial Catalog" is existing and accessible to the user. if you didn′t configure the user extensivly just drop anbd recreate him. i don′t know which administrative tasks you did prior to this problem, but this should "reset" the settings. make also sure that the user is not in a group which has access denied in the database you are redirecting to. These right will be inherited to the user as restrictive right will always overwrite granted rights.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Monday, March 26, 2012
Installing Enterprise version over Standard
We currently are running one instance of SQL Server 2000 Standard with a few databases. We need to upgrade to Enterprise version to use data cubes. Should we be able to install right over the top of our current instance of SQL Server or will we have to
create a new instance?
Thanks in advance for any help.
Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.
create a new instance?
Thanks in advance for any help.
Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.
Installing Enterprise version over Standard
We currently are running one instance of SQL Server 2000 Standard with a few
databases. We need to upgrade to Enterprise version to use data cubes. Sh
ould we be able to install right over the top of our current instance of SQL
Server or will we have to
create a new instance?
Thanks in advance for any help.Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.|||Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.
databases. We need to upgrade to Enterprise version to use data cubes. Sh
ould we be able to install right over the top of our current instance of SQL
Server or will we have to
create a new instance?
Thanks in advance for any help.Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.|||Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.
Installing Enterprise version over Standard
We currently are running one instance of SQL Server 2000 Standard with a few databases. We need to upgrade to Enterprise version to use data cubes. Should we be able to install right over the top of our current instance of SQL Server or will we have to create a new instance
Thanks in advance for any help.Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft® SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.sql
Thanks in advance for any help.Hi,
You can upgrade the SQL Server standard to SQL server enterprise edition
directly.
Steps from boks online:-
How to perform an edition upgrade within SQL Server 2000 (Setup)
To upgrade a SQL Server 2000 installation to a different edition of SQL
Server 2000
1.. Insert the Microsoft® SQL Server 2000T compact disc for the edition
you want to install into your CD-ROM drive. If the compact disc does not
autorun, double-click Autorun.exe in the root directory of the compact disc.
2.. Select SQL Server 2000 Components, select Install Database Server, and
then setup prepares the SQL Server Installation Wizard. At the Welcome
screen, click Next.
3.. In Computer Name dialog box, select Local Computer or Remote computer.
4.. In the Installation Selection dialog box, click Upgrade, Remove, or
Add Components to an existing instance of SQL Server, and then click Next.
5.. In the Instance Name dialog box, click Next.
6.. In the Existing Installation dialog box, click Upgrade your existing
installation, and then click Next.
7.. If Setup detects that you are doing an edition upgrade, the Upgrade
dialog box appears. Click Yes, Upgrade my <text specific to the upgrade> to
upgrade the feature set of your current installation, and click Next.
8.. After the upgrade is completed, you are prompted as to whether you
want to install additional components. If you click Yes, the Select
Components dialog box appears. Accept the defaults or select the additional
components you want to install, and then click Next.
You can select an item in the Components list, and then select items from
the related Sub-Components list. Click to select items you want to install;
clear the check box of the items you do not want to install.
9.. When you are finished specifying options, in the Start Copying Files
dialog box, click Next.
10.. In the Setup Complete dialog box, click Yes, I want to restart my
computer now, and then click Finish to complete the edition upgrade.
Thanks
Hari
MCDBA
"mt" <anonymous@.discussions.microsoft.com> wrote in message
news:104B9AD9-3BE2-4B86-84F4-7C22BCD28CAC@.microsoft.com...
> We currently are running one instance of SQL Server 2000 Standard with a
few databases. We need to upgrade to Enterprise version to use data cubes.
Should we be able to install right over the top of our current instance of
SQL Server or will we have to create a new instance?
> Thanks in advance for any help.sql
Installing databases to different hard drives.
Can't find anything on how to install to drives other than sys. I'm brand new to Servers and Databases in general and trying to learn. How do I get databases to install on drive partitions other than my main system drive?
Hi,
don′t know if you mean database or instance in your case. Databases can be installed (or created) on medias using the CREATE DATABASE statement using the file destination (more details in the BOL) or with the GUI placing the files whereever on your local disks or SAN you want.
The instance and therefore the server service files can be installed on every drive you want for SQL Server 2000, for SQL Server 2005, there has been (and probably there is even after SP1) the restrictions that the files can only be installed on the system partition.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
simply get the new books online, or reinstall the help files from the media. I had that once too,that the help files (or just the link) where corrupted.
http://www.microsoft.com/downloads/details.aspx?FamilyID=be6a2c5d-00df-4220-b133-29c1e0b6585f&DisplayLang=en
(it′s the new BOL form April 2006)
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||I uninstalled everything all the way back to IIS I think whatever it was may be OK now. I hope. Thanks.
Wednesday, March 21, 2012
Installed SQL Server 2005 but Enterprise Manager is missing and so are the databases like
Gurus,
Installed SQL 2005 for the first time. I noticed Enterprise Manager is
missing. So I went into Configuration Manager since it sounded similar and
low and behold I discovered that all the databases that get created in SQL
Server 2000 like Master, Model, Northwind, etc are missing. My question is
are they actually missing or do I need to install an add-on to see them?
Spin
> Installed SQL 2005 for the first time. I noticed Enterprise Manager is
> missing.
It is not Enterprise Manager anymore. EM & Query Analyzer have been
combined into a single GUI tool called Management Studio. It should be
under the program files folder for SQL Server 2005, and if not, perhaps you
didn't pay close attention during install. You need to specify that
Management Studio is to be installed by going into Workstation Components.
> low and behold I discovered that all the databases that get created in SQL
> Server 2000 like Master, Model, Northwind, etc are missing.
Well, master and model are certainly there. What does "missing" mean? I
think you need to get Management Studio up and running before you can make
any judgment calls on what's there and what's not.
Oh, and Northwind is no longer a database that ships with SQL Server (same
as pubs). You can install AdventureWorks which is found under Sample
Databases in setup.
|||> What is the name of the file that I click on to bring up the Management
> Studio tool?
The executable is sqlwb.exe. However, the full name should be in a shortcut
on your start menu.
|||I do not have this executable. So I put the CD back in and do what?
Why does Microsoft have to make this so hard?
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OY4FPGFfHHA.1244@.TK2MSFTNGP04.phx.gbl...
> The executable is sqlwb.exe. However, the full name should be in a
> shortcut on your start menu.
>
|||>I do not have this executable. So I put the CD back in and do what?
Since you already have the server installed, then open the CD, go to the
tools folder, run setup.exe, and when you get to the screen that asks which
components you want to install, slow down. First you'll go through these
steps:
(a) check "I accept the licensing terms and conditions"
(b) hit " Next > "
(c) wait for prerequisites to be installed (yes it will have to do this
every time)
(d) hit " Next > "
Now you will be at "Welcome to the Microsoft SQL Server Installation Wizard.
(a) hit " Next > "
(b) as long as you don't have any errors on the config check, hit " Next > "
(c) enter your name and company (or leave blank if desired)
(d) hit " Next > "
(e) on the feature selection page, expand Client Components
(f) I would select Connectivity Components and Management Tools (you may
choose others if you wish)
(to select a component, you click on the down arrow next to a component,
and choose "Will be installed on local hard drive")
(g) if you want sample database and/or Books Online, expand the
Documentation, Samples... node
(h) hit " Next > " ... I assume you'll be okay without assistance from here?
> Why does Microsoft have to make this so hard?
I don't think they made it as hard as you make it out to be. And be honest,
did you read "ReadmeSQL2005.htm" and setup instructions, and pay attention
to all screens while you were installing the product?
|||Thank you!
To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all, I
simply expect the products to have the same tools in the same places as the
previous versions. We're all too busy in this life to have company software
throw us curveballs. I think MS should recognize that everyone is busy and
have products be intuitive enough to the point where you don't have to RTM.
Well, maybe RTM is a good thing b/c it keep us IT people in a job! Well,
it's off to the manual and this thing now.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ucElrmKfHHA.2376@.TK2MSFTNGP04.phx.gbl...
> Since you already have the server installed, then open the CD, go to the
> tools folder, run setup.exe, and when you get to the screen that asks
> which components you want to install, slow down. First you'll go through
> these steps:
> (a) check "I accept the licensing terms and conditions"
> (b) hit " Next > "
> (c) wait for prerequisites to be installed (yes it will have to do this
> every time)
> (d) hit " Next > "
> Now you will be at "Welcome to the Microsoft SQL Server Installation
> Wizard.
> (a) hit " Next > "
> (b) as long as you don't have any errors on the config check, hit " Next >
> "
> (c) enter your name and company (or leave blank if desired)
> (d) hit " Next > "
> (e) on the feature selection page, expand Client Components
> (f) I would select Connectivity Components and Management Tools (you may
> choose others if you wish)
> (to select a component, you click on the down arrow next to a
> component, and choose "Will be installed on local hard drive")
> (g) if you want sample database and/or Books Online, expand the
> Documentation, Samples... node
> (h) hit " Next > " ... I assume you'll be okay without assistance from
> here?
>
> I don't think they made it as hard as you make it out to be. And be
> honest, did you read "ReadmeSQL2005.htm" and setup instructions, and pay
> attention to all screens while you were installing the product?
>
|||> To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all, I
> simply expect the products to have the same tools in the same places as
> the previous versions.
I don't think this expectation is very realistic. If a product does not
evolve, then don't bother upgrading beyond v1.0.
A
|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OD8dnuPfHHA.1216@.TK2MSFTNGP03.phx.gbl...
> I don't think this expectation is very realistic. If a product does not
> evolve, then don't bother upgrading beyond v1.0.
> A
You're right, I was just b%tching and moaning, trying to get my voice heard
by Microsoft. Thanks for listening.
|||Aaron, that tip worked btw! Nice job!
"Spin" <Spin@.spin.com> wrote in message
news:586md5F2ftkduU1@.mid.individual.net...
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in
> message news:OD8dnuPfHHA.1216@.TK2MSFTNGP03.phx.gbl...
> You're right, I was just b%tching and moaning, trying to get my voice
> heard by Microsoft. Thanks for listening.
Installed SQL 2005 for the first time. I noticed Enterprise Manager is
missing. So I went into Configuration Manager since it sounded similar and
low and behold I discovered that all the databases that get created in SQL
Server 2000 like Master, Model, Northwind, etc are missing. My question is
are they actually missing or do I need to install an add-on to see them?
Spin
> Installed SQL 2005 for the first time. I noticed Enterprise Manager is
> missing.
It is not Enterprise Manager anymore. EM & Query Analyzer have been
combined into a single GUI tool called Management Studio. It should be
under the program files folder for SQL Server 2005, and if not, perhaps you
didn't pay close attention during install. You need to specify that
Management Studio is to be installed by going into Workstation Components.
> low and behold I discovered that all the databases that get created in SQL
> Server 2000 like Master, Model, Northwind, etc are missing.
Well, master and model are certainly there. What does "missing" mean? I
think you need to get Management Studio up and running before you can make
any judgment calls on what's there and what's not.
Oh, and Northwind is no longer a database that ships with SQL Server (same
as pubs). You can install AdventureWorks which is found under Sample
Databases in setup.
|||> What is the name of the file that I click on to bring up the Management
> Studio tool?
The executable is sqlwb.exe. However, the full name should be in a shortcut
on your start menu.
|||I do not have this executable. So I put the CD back in and do what?
Why does Microsoft have to make this so hard?
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OY4FPGFfHHA.1244@.TK2MSFTNGP04.phx.gbl...
> The executable is sqlwb.exe. However, the full name should be in a
> shortcut on your start menu.
>
|||>I do not have this executable. So I put the CD back in and do what?
Since you already have the server installed, then open the CD, go to the
tools folder, run setup.exe, and when you get to the screen that asks which
components you want to install, slow down. First you'll go through these
steps:
(a) check "I accept the licensing terms and conditions"
(b) hit " Next > "
(c) wait for prerequisites to be installed (yes it will have to do this
every time)
(d) hit " Next > "
Now you will be at "Welcome to the Microsoft SQL Server Installation Wizard.
(a) hit " Next > "
(b) as long as you don't have any errors on the config check, hit " Next > "
(c) enter your name and company (or leave blank if desired)
(d) hit " Next > "
(e) on the feature selection page, expand Client Components
(f) I would select Connectivity Components and Management Tools (you may
choose others if you wish)
(to select a component, you click on the down arrow next to a component,
and choose "Will be installed on local hard drive")
(g) if you want sample database and/or Books Online, expand the
Documentation, Samples... node
(h) hit " Next > " ... I assume you'll be okay without assistance from here?
> Why does Microsoft have to make this so hard?
I don't think they made it as hard as you make it out to be. And be honest,
did you read "ReadmeSQL2005.htm" and setup instructions, and pay attention
to all screens while you were installing the product?
|||Thank you!
To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all, I
simply expect the products to have the same tools in the same places as the
previous versions. We're all too busy in this life to have company software
throw us curveballs. I think MS should recognize that everyone is busy and
have products be intuitive enough to the point where you don't have to RTM.
Well, maybe RTM is a good thing b/c it keep us IT people in a job! Well,
it's off to the manual and this thing now.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ucElrmKfHHA.2376@.TK2MSFTNGP04.phx.gbl...
> Since you already have the server installed, then open the CD, go to the
> tools folder, run setup.exe, and when you get to the screen that asks
> which components you want to install, slow down. First you'll go through
> these steps:
> (a) check "I accept the licensing terms and conditions"
> (b) hit " Next > "
> (c) wait for prerequisites to be installed (yes it will have to do this
> every time)
> (d) hit " Next > "
> Now you will be at "Welcome to the Microsoft SQL Server Installation
> Wizard.
> (a) hit " Next > "
> (b) as long as you don't have any errors on the config check, hit " Next >
> "
> (c) enter your name and company (or leave blank if desired)
> (d) hit " Next > "
> (e) on the feature selection page, expand Client Components
> (f) I would select Connectivity Components and Management Tools (you may
> choose others if you wish)
> (to select a component, you click on the down arrow next to a
> component, and choose "Will be installed on local hard drive")
> (g) if you want sample database and/or Books Online, expand the
> Documentation, Samples... node
> (h) hit " Next > " ... I assume you'll be okay without assistance from
> here?
>
> I don't think they made it as hard as you make it out to be. And be
> honest, did you read "ReadmeSQL2005.htm" and setup instructions, and pay
> attention to all screens while you were installing the product?
>
|||> To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all, I
> simply expect the products to have the same tools in the same places as
> the previous versions.
I don't think this expectation is very realistic. If a product does not
evolve, then don't bother upgrading beyond v1.0.
A
|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OD8dnuPfHHA.1216@.TK2MSFTNGP03.phx.gbl...
> I don't think this expectation is very realistic. If a product does not
> evolve, then don't bother upgrading beyond v1.0.
> A
You're right, I was just b%tching and moaning, trying to get my voice heard
by Microsoft. Thanks for listening.
|||Aaron, that tip worked btw! Nice job!
"Spin" <Spin@.spin.com> wrote in message
news:586md5F2ftkduU1@.mid.individual.net...
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in
> message news:OD8dnuPfHHA.1216@.TK2MSFTNGP03.phx.gbl...
> You're right, I was just b%tching and moaning, trying to get my voice
> heard by Microsoft. Thanks for listening.
Installed SQL Server 2005 but Enterprise Manager is missing and so are the databases like
Gurus,
Installed SQL 2005 for the first time. I noticed Enterprise Manager is
missing. So I went into Configuration Manager since it sounded similar and
low and behold I discovered that all the databases that get created in SQL
Server 2000 like Master, Model, Northwind, etc are missing. My question is
are they actually missing or do I need to install an add-on to see them?
--
Spin> Installed SQL 2005 for the first time. I noticed Enterprise Manager is
> missing.
It is not Enterprise Manager anymore. EM & Query Analyzer have been
combined into a single GUI tool called Management Studio. It should be
under the program files folder for SQL Server 2005, and if not, perhaps you
didn't pay close attention during install. You need to specify that
Management Studio is to be installed by going into Workstation Components.
> low and behold I discovered that all the databases that get created in SQL
> Server 2000 like Master, Model, Northwind, etc are missing.
Well, master and model are certainly there. What does "missing" mean? I
think you need to get Management Studio up and running before you can make
any judgment calls on what's there and what's not.
Oh, and Northwind is no longer a database that ships with SQL Server (same
as pubs). You can install AdventureWorks which is found under Sample
Databases in setup.|||What is the name of the file that I click on to bring up the Management
Studio tool?
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:uGwi7MEfHHA.1220@.TK2MSFTNGP03.phx.gbl...
>> Installed SQL 2005 for the first time. I noticed Enterprise Manager is
>> missing.
> It is not Enterprise Manager anymore. EM & Query Analyzer have been
> combined into a single GUI tool called Management Studio. It should be
> under the program files folder for SQL Server 2005, and if not, perhaps
> you didn't pay close attention during install. You need to specify that
> Management Studio is to be installed by going into Workstation Components.
>> low and behold I discovered that all the databases that get created in
>> SQL Server 2000 like Master, Model, Northwind, etc are missing.
> Well, master and model are certainly there. What does "missing" mean? I
> think you need to get Management Studio up and running before you can make
> any judgment calls on what's there and what's not.
> Oh, and Northwind is no longer a database that ships with SQL Server (same
> as pubs). You can install AdventureWorks which is found under Sample
> Databases in setup.
>|||> What is the name of the file that I click on to bring up the Management
> Studio tool?
The executable is sqlwb.exe. However, the full name should be in a shortcut
on your start menu.|||I do not have this executable. So I put the CD back in and do what?
Why does Microsoft have to make this so hard?
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OY4FPGFfHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> What is the name of the file that I click on to bring up the Management
>> Studio tool?
> The executable is sqlwb.exe. However, the full name should be in a
> shortcut on your start menu.
>|||>I do not have this executable. So I put the CD back in and do what?
Since you already have the server installed, then open the CD, go to the
tools folder, run setup.exe, and when you get to the screen that asks which
components you want to install, slow down. First you'll go through these
steps:
(a) check "I accept the licensing terms and conditions"
(b) hit " Next > "
(c) wait for prerequisites to be installed (yes it will have to do this
every time)
(d) hit " Next > "
Now you will be at "Welcome to the Microsoft SQL Server Installation Wizard.
(a) hit " Next > "
(b) as long as you don't have any errors on the config check, hit " Next > "
(c) enter your name and company (or leave blank if desired)
(d) hit " Next > "
(e) on the feature selection page, expand Client Components
(f) I would select Connectivity Components and Management Tools (you may
choose others if you wish)
(to select a component, you click on the down arrow next to a component,
and choose "Will be installed on local hard drive")
(g) if you want sample database and/or Books Online, expand the
Documentation, Samples... node
(h) hit " Next > " ... I assume you'll be okay without assistance from here?
> Why does Microsoft have to make this so hard?
I don't think they made it as hard as you make it out to be. And be honest,
did you read "ReadmeSQL2005.htm" and setup instructions, and pay attention
to all screens while you were installing the product?|||Thank you!
To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all, I
simply expect the products to have the same tools in the same places as the
previous versions. We're all too busy in this life to have company software
throw us curveballs. I think MS should recognize that everyone is busy and
have products be intuitive enough to the point where you don't have to RTM.
Well, maybe RTM is a good thing b/c it keep us IT people in a job! Well,
it's off to the manual and this thing now. :)
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ucElrmKfHHA.2376@.TK2MSFTNGP04.phx.gbl...
> >I do not have this executable. So I put the CD back in and do what?
> Since you already have the server installed, then open the CD, go to the
> tools folder, run setup.exe, and when you get to the screen that asks
> which components you want to install, slow down. First you'll go through
> these steps:
> (a) check "I accept the licensing terms and conditions"
> (b) hit " Next > "
> (c) wait for prerequisites to be installed (yes it will have to do this
> every time)
> (d) hit " Next > "
> Now you will be at "Welcome to the Microsoft SQL Server Installation
> Wizard.
> (a) hit " Next > "
> (b) as long as you don't have any errors on the config check, hit " Next >
> "
> (c) enter your name and company (or leave blank if desired)
> (d) hit " Next > "
> (e) on the feature selection page, expand Client Components
> (f) I would select Connectivity Components and Management Tools (you may
> choose others if you wish)
> (to select a component, you click on the down arrow next to a
> component, and choose "Will be installed on local hard drive")
> (g) if you want sample database and/or Books Online, expand the
> Documentation, Samples... node
> (h) hit " Next > " ... I assume you'll be okay without assistance from
> here?
>> Why does Microsoft have to make this so hard?
> I don't think they made it as hard as you make it out to be. And be
> honest, did you read "ReadmeSQL2005.htm" and setup instructions, and pay
> attention to all screens while you were installing the product?
>|||> To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all, I
> simply expect the products to have the same tools in the same places as
> the previous versions.
I don't think this expectation is very realistic. If a product does not
evolve, then don't bother upgrading beyond v1.0.
A|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OD8dnuPfHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all, I
>> simply expect the products to have the same tools in the same places as
>> the previous versions.
> I don't think this expectation is very realistic. If a product does not
> evolve, then don't bother upgrading beyond v1.0.
> A
You're right, I was just b%tching and moaning, trying to get my voice heard
by Microsoft. Thanks for listening.|||Aaron, that tip worked btw! Nice job!
"Spin" <Spin@.spin.com> wrote in message
news:586md5F2ftkduU1@.mid.individual.net...
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in
> message news:OD8dnuPfHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all,
>> I simply expect the products to have the same tools in the same places
>> as the previous versions.
>> I don't think this expectation is very realistic. If a product does not
>> evolve, then don't bother upgrading beyond v1.0.
>> A
> You're right, I was just b%tching and moaning, trying to get my voice
> heard by Microsoft. Thanks for listening.sql
Installed SQL 2005 for the first time. I noticed Enterprise Manager is
missing. So I went into Configuration Manager since it sounded similar and
low and behold I discovered that all the databases that get created in SQL
Server 2000 like Master, Model, Northwind, etc are missing. My question is
are they actually missing or do I need to install an add-on to see them?
--
Spin> Installed SQL 2005 for the first time. I noticed Enterprise Manager is
> missing.
It is not Enterprise Manager anymore. EM & Query Analyzer have been
combined into a single GUI tool called Management Studio. It should be
under the program files folder for SQL Server 2005, and if not, perhaps you
didn't pay close attention during install. You need to specify that
Management Studio is to be installed by going into Workstation Components.
> low and behold I discovered that all the databases that get created in SQL
> Server 2000 like Master, Model, Northwind, etc are missing.
Well, master and model are certainly there. What does "missing" mean? I
think you need to get Management Studio up and running before you can make
any judgment calls on what's there and what's not.
Oh, and Northwind is no longer a database that ships with SQL Server (same
as pubs). You can install AdventureWorks which is found under Sample
Databases in setup.|||What is the name of the file that I click on to bring up the Management
Studio tool?
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:uGwi7MEfHHA.1220@.TK2MSFTNGP03.phx.gbl...
>> Installed SQL 2005 for the first time. I noticed Enterprise Manager is
>> missing.
> It is not Enterprise Manager anymore. EM & Query Analyzer have been
> combined into a single GUI tool called Management Studio. It should be
> under the program files folder for SQL Server 2005, and if not, perhaps
> you didn't pay close attention during install. You need to specify that
> Management Studio is to be installed by going into Workstation Components.
>> low and behold I discovered that all the databases that get created in
>> SQL Server 2000 like Master, Model, Northwind, etc are missing.
> Well, master and model are certainly there. What does "missing" mean? I
> think you need to get Management Studio up and running before you can make
> any judgment calls on what's there and what's not.
> Oh, and Northwind is no longer a database that ships with SQL Server (same
> as pubs). You can install AdventureWorks which is found under Sample
> Databases in setup.
>|||> What is the name of the file that I click on to bring up the Management
> Studio tool?
The executable is sqlwb.exe. However, the full name should be in a shortcut
on your start menu.|||I do not have this executable. So I put the CD back in and do what?
Why does Microsoft have to make this so hard?
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OY4FPGFfHHA.1244@.TK2MSFTNGP04.phx.gbl...
>> What is the name of the file that I click on to bring up the Management
>> Studio tool?
> The executable is sqlwb.exe. However, the full name should be in a
> shortcut on your start menu.
>|||>I do not have this executable. So I put the CD back in and do what?
Since you already have the server installed, then open the CD, go to the
tools folder, run setup.exe, and when you get to the screen that asks which
components you want to install, slow down. First you'll go through these
steps:
(a) check "I accept the licensing terms and conditions"
(b) hit " Next > "
(c) wait for prerequisites to be installed (yes it will have to do this
every time)
(d) hit " Next > "
Now you will be at "Welcome to the Microsoft SQL Server Installation Wizard.
(a) hit " Next > "
(b) as long as you don't have any errors on the config check, hit " Next > "
(c) enter your name and company (or leave blank if desired)
(d) hit " Next > "
(e) on the feature selection page, expand Client Components
(f) I would select Connectivity Components and Management Tools (you may
choose others if you wish)
(to select a component, you click on the down arrow next to a component,
and choose "Will be installed on local hard drive")
(g) if you want sample database and/or Books Online, expand the
Documentation, Samples... node
(h) hit " Next > " ... I assume you'll be okay without assistance from here?
> Why does Microsoft have to make this so hard?
I don't think they made it as hard as you make it out to be. And be honest,
did you read "ReadmeSQL2005.htm" and setup instructions, and pay attention
to all screens while you were installing the product?|||Thank you!
To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all, I
simply expect the products to have the same tools in the same places as the
previous versions. We're all too busy in this life to have company software
throw us curveballs. I think MS should recognize that everyone is busy and
have products be intuitive enough to the point where you don't have to RTM.
Well, maybe RTM is a good thing b/c it keep us IT people in a job! Well,
it's off to the manual and this thing now. :)
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ucElrmKfHHA.2376@.TK2MSFTNGP04.phx.gbl...
> >I do not have this executable. So I put the CD back in and do what?
> Since you already have the server installed, then open the CD, go to the
> tools folder, run setup.exe, and when you get to the screen that asks
> which components you want to install, slow down. First you'll go through
> these steps:
> (a) check "I accept the licensing terms and conditions"
> (b) hit " Next > "
> (c) wait for prerequisites to be installed (yes it will have to do this
> every time)
> (d) hit " Next > "
> Now you will be at "Welcome to the Microsoft SQL Server Installation
> Wizard.
> (a) hit " Next > "
> (b) as long as you don't have any errors on the config check, hit " Next >
> "
> (c) enter your name and company (or leave blank if desired)
> (d) hit " Next > "
> (e) on the feature selection page, expand Client Components
> (f) I would select Connectivity Components and Management Tools (you may
> choose others if you wish)
> (to select a component, you click on the down arrow next to a
> component, and choose "Will be installed on local hard drive")
> (g) if you want sample database and/or Books Online, expand the
> Documentation, Samples... node
> (h) hit " Next > " ... I assume you'll be okay without assistance from
> here?
>> Why does Microsoft have to make this so hard?
> I don't think they made it as hard as you make it out to be. And be
> honest, did you read "ReadmeSQL2005.htm" and setup instructions, and pay
> attention to all screens while you were installing the product?
>|||> To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all, I
> simply expect the products to have the same tools in the same places as
> the previous versions.
I don't think this expectation is very realistic. If a product does not
evolve, then don't bother upgrading beyond v1.0.
A|||"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:OD8dnuPfHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all, I
>> simply expect the products to have the same tools in the same places as
>> the previous versions.
> I don't think this expectation is very realistic. If a product does not
> evolve, then don't bother upgrading beyond v1.0.
> A
You're right, I was just b%tching and moaning, trying to get my voice heard
by Microsoft. Thanks for listening.|||Aaron, that tip worked btw! Nice job!
"Spin" <Spin@.spin.com> wrote in message
news:586md5F2ftkduU1@.mid.individual.net...
> "Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in
> message news:OD8dnuPfHHA.1216@.TK2MSFTNGP03.phx.gbl...
>> To be honest back, I never read ReadmeSQL2005.htm. I never RTM at all,
>> I simply expect the products to have the same tools in the same places
>> as the previous versions.
>> I don't think this expectation is very realistic. If a product does not
>> evolve, then don't bother upgrading beyond v1.0.
>> A
> You're right, I was just b%tching and moaning, trying to get my voice
> heard by Microsoft. Thanks for listening.sql
Subscribe to:
Posts (Atom)