2005 features not working

I have both sql 2000 and sql2005 installed on a machine and with management
studio it seems to show the databases created in 2000 but does not seem to
have many of the new features of 2005. It seems as though it is not
operating against a SQL Server 2005 installation although 2005 is installed.
Just wondering if I would need to remove sql2000 for 2005 to operate with
full features?
thanks.
Paul G
Software engineer.
What new features are you referring to that you expect to see that you
don't? If you are talking about not being able to use some of the new
features make sure your db in 90 compatibility mode. If you upgrade a 2000
db it stays in 80 compat mode.
Andrew J. Kelly SQL MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:B5275E28-3080-4D05-ABBC-D575D11C43B8@.microsoft.com...
>I have both sql 2000 and sql2005 installed on a machine and with management
> studio it seems to show the databases created in 2000 but does not seem to
> have many of the new features of 2005. It seems as though it is not
> operating against a SQL Server 2005 installation although 2005 is
> installed.
> Just wondering if I would need to remove sql2000 for 2005 to operate with
> full features?
> thanks.
> --
> Paul G
> Software engineer.
|||for example in viewing databases I did not see a section for schema in the
object explorer so could not add one. Also in following the instructions to
create a cube, I could not because a cube folder was not present after a new
solution was created in the project explorer. Also I noticed on the status
bar it lists the computer name followed by (8.0 RTM), does this mean it is
not the full feature version running? Also how do you switch it to the 90
compatable mode?
thanks
Paul G
Software engineer.
"Andrew J. Kelly" wrote:

> What new features are you referring to that you expect to see that you
> don't? If you are talking about not being able to use some of the new
> features make sure your db in 90 compatibility mode. If you upgrade a 2000
> db it stays in 80 compat mode.
> --
> Andrew J. Kelly SQL MVP
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:B5275E28-3080-4D05-ABBC-D575D11C43B8@.microsoft.com...
>
>
|||Also note that you can have only one default (server name only) instance.
If your SQL 2000 instance is the default instance, then the installed SQL
2005 instance must be a named instance. You can connect to named instances
using '<server name>\<instance name>'.
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:57529330-1DD6-41F7-A6A1-6A38C416AFA1@.microsoft.com...[vbcol=seagreen]
> for example in viewing databases I did not see a section for schema in the
> object explorer so could not add one. Also in following the instructions
> to
> create a cube, I could not because a cube folder was not present after a
> new
> solution was created in the project explorer. Also I noticed on the
> status
> bar it lists the computer name followed by (8.0 RTM), does this mean it is
> not the full feature version running? Also how do you switch it to the 90
> compatable mode?
> thanks
> --
> Paul G
> Software engineer.
>
> "Andrew J. Kelly" wrote:
|||Thanks for the information, I looked at the programs installed it lists
Microsoft SQL 2005 so think I have it installed.
Paul G
Software engineer.
"Tibor Karaszi" wrote:

> It means that the server (instance) you have connected to is SQL Server 2000. Perhaps you only
> upgraded the client tools?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:57529330-1DD6-41F7-A6A1-6A38C416AFA1@.microsoft.com...
>
|||So do I need to create a new dbase out of management studio, so would this
work out of management studio query window,
using '<computer name>\<mssql 2005>'.
thanks.
Paul G
Software engineer.
"Dan Guzman" wrote:

> Also note that you can have only one default (server name only) instance.
> If your SQL 2000 instance is the default instance, then the installed SQL
> 2005 instance must be a named instance. You can connect to named instances
> using '<server name>\<instance name>'.
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:57529330-1DD6-41F7-A6A1-6A38C416AFA1@.microsoft.com...
>
|||> Thanks for the information, I looked at the programs installed it lists
> Microsoft SQL 2005 so think I have it installed.
That could still only be the client tools.
Look at the services that are running. Is "MSSQLSERVER" listed, or "SQL
Server", or both?
A
|||Hi here is what I have listed in the services section from the control panel,
SQL Server (SQLEXPRESS)-probably should remove this
SQL Server Active Directory Helper
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Browser
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server VSS Writer
MSSQLSERVER
SQLSERVERAGENT
I did not see a SQL Server by itself. Guess it does not specify the year
just from the service listing. Does this look like only the client may be
installed? Also I installed it off of the Visual Studio 2005 professional
addition, disk labeled SQL Server 2005 Developer edition. Thanks.
Paul G
Software engineer.
"Aaron Bertrand [SQL Server MVP]" wrote:

> That could still only be the client tools.
> Look at the services that are running. Is "MSSQLSERVER" listed, or "SQL
> Server", or both?
> A
>
>
|||Hi thanks for the additional information. Do you know if I can install the
2005 SQL Server agent without effecting the 2000 server agent as I have
several jobs scheduled? Also looks like I do not have the database engine
installed 2005 as you noted. Does this come with the SQL Server 2005
Developer edition (guessing it does) and can it be installed along with the
2000 database engine without effecting the 2000 instance? If so not sure why
it was not installed, guess I may have not selected the proper installation
option.
Paul G
Software engineer.
"Tibor Karaszi" wrote:

> The services with the long names are 2005 services. So, it seems you have a lot of 2005 stuff
> installed, *except* the database engine (and Agent). I.e., below are 2000 or 7.0 (based on the
> service name):
> MSSQLSERVER
> SQLSERVERAGENT
> (In 2005, a service has both a long name and a short name. However, the tools you use will present
> the long name.)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:D2E27CD8-2D39-4E97-B954-8D9C9B64488B@.microsoft.com...
>
>
|||Hi I installed the SQL Svr Developer Edtn 2005 disk and have the following
selections for installation/repair
SQL Server Database Services
Analysis Services
Reporting Services
Notification Services
Integration Services
Workstation Components, Books online and Development tools.
Anyhow I was expecting to see SQL Server components but did not, do you know
if the SQL Server Database Services should install the database engine?
thanks.
Paul G
Software engineer.
"Tibor Karaszi" wrote:

> Yes. Install another SQL Server Database Engine instance. Each Database Engine comes with Agent.
>
> Yep. As per above, just install a new database engine instance.
>
> That would be my guess as well.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:43AF09FA-ED81-45F2-98F4-E25C64C70927@.microsoft.com...
>
>