Which version of SQL server to use.

[moondaddy]

I'm new to MS Project and Project Server. I'm setting up my first test
setup which we will test in an intranet environment. I already have SQL
Server 2000 standard installed on a machine and available for use. however,
I'm reading in some of the documentation and it says SQL Serer Ent. is
required for HTTP Internet Support. Here's a snippet from the docs:

<<
Both SQL Server 2000 Standard and SQL Server 2000 Enterprise support the
enterprise functionality of Project Server 2003, but only SQL Server 2000
Enterprise will support advanced deployment features like failover or HTTP
Internet Support. SQL Server 2000 must be installed before you can install
Project Server 2003 or configure Windows SharePoint Services for Project
Server 2003.
Does this mean that in order to use Web Access we need to have SQL Ent
edition? I'm wanting to have client access via outlook or the browser to a
remotely hosted project server. Exactly what is the scope of HTTP Internet
Support include and what can I do with out it?

Additionally, all documentation refers to sql server 2k. I can also run the
2005 version. Would SQL Server 2005 standard edition be able to satisfy the
requirements needed for HTTP Internet Support?

Thanks.

 

[.]

Define "remotely hosted". If the PWA user and the Project Server and the SQL
server are all behind the same firewall, SQL 2000 Std is fine.

If you're trying to use some functionality across the Internet, some of the
SQL Std. stuff runs on a different port that will be blocked (should be
blocked) by a firewall. I think it's the Portfolio Analyzer stuff mainly. In
Ent., it runs across port 80. In either case, it's unencrypted and should
not be exposed on the Internet anyway.

SQL 2005 is not officially supported. Some people have cobbled together
workarounds, but I certainly wouldn't go there in a production system yet.

Ray

 

[moondaddy]

When I say remotely hosted, I mean that SQL Server and Project Server will
be on dedicated servers hosted at an ISP. SQL server will be on its own
machine behind its own firewall and not available to the internet. Project
Server will be on another machine and will act as a web server where the
client machines will have access to it. At this point I don't think we need
the analysis services as this is a small scale situation and are not looking
for complex reports. I want to know if client machines will have web access
to project server even though we are using SQL Standard edition on the
backend. I assume Web Access means outlook clients communicating via http
and also browsers will be able to talk to project server. Is this correct?

Thanks.

--
(e-mail address removed)

Define "remotely hosted". If the PWA user and the Project Server and the
SQL server are all behind the same firewall, SQL 2000 Std is fine.

If you're trying to use some functionality across the Internet, some of
the SQL Std. stuff runs on a different port that will be blocked (should
be blocked) by a firewall. I think it's the Portfolio Analyzer stuff
mainly. In Ent., it runs across port 80. In either case, it's unencrypted
and should not be exposed on the Internet anyway.

SQL 2005 is not officially supported. Some people have cobbled together
workarounds, but I certainly wouldn't go there in a production system yet.

Ray

 

[.]

Yeah, you're OK as long as you don't try to use the Portfolio Analyzer
function. I had Project Web Access clients connecting as team members just
over HTTPS and it worked OK. SQL 2000 Standard was the backend.

Web Access means IE talking to the Project Server. Outlook can either have a
plug-in or a browser view.

How is Project Professional going to talk to Project Server and the SQL
Server at the ISP? It needs to do that to work.

Ray

When I say remotely hosted, I mean that SQL Server and Project Server will
be on dedicated servers hosted at an ISP. SQL server will be on its own
machine behind its own firewall and not available to the internet.
Project Server will be on another machine and will act as a web server
where the client machines will have access to it. At this point I don't
think we need the analysis services as this is a small scale situation and
are not looking for complex reports. I want to know if client machines
will have web access to project server even though we are using SQL
Standard edition on the backend. I assume Web Access means outlook
clients communicating via http and also browsers will be able to talk to
project server. Is this correct?

Thanks.

 

[moondaddy]

How is Project Professional going to talk to Project Server and the SQL

Server at the ISP? It needs to do that to work.

Well this is a good question. I'm new to project all together and assumed
that the project clients (Project Pro) will talk to project server and
project server talks to sql server (as in how ntier apps are supposed to
run. client apps should never talk to sql server). If its a must that the
Project Pro talk to SQL Server then this may be a bit of a problem. For now
we are working in a small test scenario so I can probably deal with it, but
I really am against client apps talking to the SQL Server machine.

Comments?

 

[Gary L. Chefetz [MVP]]

Moondaddy:

The Project Client **must** talk to SQL. Don't blame you for being against
this. The solution is Terminal Services or Citrix. You'll want this anyway,
as the performance will be unacceptable trying to use Project across the
Internet.

 

[moondaddy]

Thanks. This is rather discuraging. Also the licesning requirements are
rather messy too as each client needs to have a client license to Project
server, sql server and windows server. I wish they would redo this when
Vista rolls out and just give us a smart client that logs into IIS via WS
and then has project server and sql server behind IIS. Now that would work
good!

by the way, I really need help on a post with a subject of:

"Error logging into Project Server via the 'Configure Microsoft Office
Project Server' menu"

I'm really stuck and am no longer getting any posts to this thread. Could
you kindly take a look at this for me?

Thanks!

--
(e-mail address removed)

Moondaddy:

The Project Client **must** talk to SQL. Don't blame you for being against
this. The solution is Terminal Services or Citrix. You'll want this
anyway, as the performance will be unacceptable trying to use Project
across the Internet.

 

[Gary L. Chefetz [MVP]]

Moondaddy:

You got the correct answer to your problem in the referenced thread. You
didn't run the sql script, or incorrectly applied it to the wrong database.

 

[moondaddy]

Thanks but, No, I dissagree. Please look at my response to that one. SP4
has been correctly installed (Product Version: 8.00.2039 (SP4)) and I
have ONLY one ProjectServer db in the one and only SQL Server instance, and
Project Server is referenceing that specific DB. I really don't see where
or how it could get confused.

Any other ideas?

 

[Gary L. Chefetz [MVP]]

Well, why don't you post the steps you took to apply the SP, each one
exactly as you did it. The playback feature on my crystal ball is on the
fritz.<g>

 

[Bob]

Hi,

From what I can see in your recernt posting of

questions that you creating an EPM system based on
the Project server 2003 environment.

My company recently got the whole environment setup by
a third party. I am now administring the backend.. To
quicken my lerning time, I am trying to create a very
similar environment at home. Please could you help? Do
you have a set of step by step setup instructions to
install a verious software packges (SQL, Project
server, IIS etc)

Thank you in advance for your help.

Regards

Bob