SQL 2005 backend

M

Mr. Mohr

I have a quick question which one of you may know... I fell into a support
position for our Project Server 2003 deployment right after our SQL server
was upgraded to 2005 without any consideration how this would impact Project
Server.

What I want to know is can you run the script SetupDB.cmd against a database
containing valid data without it compromising this data in any way?

I know that my questions may be simple or not the most intelligent but I
would appreciate some type of response! I really *do* need your help!

Thanks!

Bill
 
B

Ben Howard

Hi Bill,
setupdb.cmd is there to create a new database, rather than be run against an
existing one. If your IT group have upgraded SQL2000 to SQL2005 then you
shouldn't have to do anything else, except to get OLAP working. Of course,
you should make sure that SQL2005 is at SP1 at least. The get OLAP working,
you'll need to reference kb92116.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

2007 OLAP Cube building against SQL 2005 Cluster 2
MPS 2003 Sample Database - SQL 2005 version????? 2
Project Server MUI with SQL 2005 backend 1
Upgrade Backend Database from version 2000 to version 2005 0
Olap data views 3
Project server 2007 installation and Migration 2
Project Server 2007 SQL Server 2005 requirements 1
Support for PS 2003 with SQL 2005? 1

Top