SQL 2000 Standard or Enterprise

[Tommy Nguyen]

What version of SQL 2000, Standard or Enterprise, am I required to have in
order to use enterprise features in Project Server? The reason why I am
asking is because I am having trouble connecting Project Pro to Project
Server. I understand that in order to connect Project Pro to Project Server
I must enable enterprise features in Project Server. I do have that
enabled. From what I could find on MS' websites, they do not clarify what
version of SQL is needed to do this. Any help is much appreciated.

http://support.microsoft.com/default.aspx?scid=kb;en-us;823433&Product=OffPr2003


Tommy Nguyen

 

[Rob Schneider]

AFAIK, both versions of SQL are ok. SQL Server Enterprise just provides
additional tools for setup and admininstration of the same basic
database engine. See
http://www.microsoft.com/sql/evaluation/features/choosing.asp for
differences between to products.

What is the exact error message you are seeing when you try to connect?

Hope this is useful to you. Let us know.

rms

 

[Tommy Nguyen]

The error I am getting is:

The Project Server database is unavailable.
You can't access the database for one of the following reasons:
There is a problem with the enterprise global template in the database.
You do not have sufficient permission to access the enterprise global
template.
Netwrok problems are preventing access.
Project Server does not have enterprise features enabled.
Try to connect to the Project Server again. If the problem persists,
contact your server administrator.

 

[Rob Schneider]

Tommy,

I can only hazard a guess that the problem lies with one of the stated
reasons? This is closer to the root cause than the version of SQL
server, I believe.

Perhaps you should post this error message on the group specialising in
the pro/server microsoft.public.project.pro_and_server and experts there
might know exactly what this symptom corresponds to.

Hope this is useful to you. Let us know.

rms

 

[Tommy Nguyen]

Thanks for the help.

Tommy,

I can only hazard a guess that the problem lies with one of the stated
reasons? This is closer to the root cause than the version of SQL
server, I believe.

Perhaps you should post this error message on the group specialising in
the pro/server microsoft.public.project.pro_and_server and experts there
might know exactly what this symptom corresponds to.

Hope this is useful to you. Let us know.

rms