Z
Zyxt
(Sorry about the crosspost... wasn't sure where to put it. Seems like
people from both Project Server and SQL Server camps could answer this
one.)
We are currently running Project Server and using MS SQL 2000 as its db
server. The problem is that the SQL server is installed on a grossly
underpowered machine which it never should've been installed on. So, now
we finally have a good server-level machine available onto which I want
to move the SQL server. My only problem is that I'm just not sure how to
manage the move.
I can easily take a backup from the current SQL server and restore it
onto the new SQL server. However, this does not restore the db user
accounts nor the custom user roles that Project Server created on the SQL
server. How can I manage this? I found articles 314546 and 246133 on
MS's support site which include general instructions that allow you to
export users/passwords via the Data Transformation Services. However,
does this also export any custom role sets?
Another apparent hang up is that this new server has substantially more
disk space and thus a different partition layout. For example, assume
the current machine only has a C: partition on a very small drive, while
the new machine has C: and D: and E: partitions on multiple RAID sets.
Seems like this prevents me from restoring the 'master' db from the
current machine onto the new machine, as the new partition layout breaks
it. (I've done a trial-and-error test with the new machine, to no
avail.)
Basically, I just need to figure out how to get the current SQL server
moved over to this new, more powerful machine. Something I can do at
night while people are gone, of course, so they can come in the next day
and never notice that anything changed.
Any ideas? I'm not a SQL Server expert, so I'm having a tough time
figuring out quite how to handle this.
-j
people from both Project Server and SQL Server camps could answer this
one.)
We are currently running Project Server and using MS SQL 2000 as its db
server. The problem is that the SQL server is installed on a grossly
underpowered machine which it never should've been installed on. So, now
we finally have a good server-level machine available onto which I want
to move the SQL server. My only problem is that I'm just not sure how to
manage the move.
I can easily take a backup from the current SQL server and restore it
onto the new SQL server. However, this does not restore the db user
accounts nor the custom user roles that Project Server created on the SQL
server. How can I manage this? I found articles 314546 and 246133 on
MS's support site which include general instructions that allow you to
export users/passwords via the Data Transformation Services. However,
does this also export any custom role sets?
Another apparent hang up is that this new server has substantially more
disk space and thus a different partition layout. For example, assume
the current machine only has a C: partition on a very small drive, while
the new machine has C: and D: and E: partitions on multiple RAID sets.
Seems like this prevents me from restoring the 'master' db from the
current machine onto the new machine, as the new partition layout breaks
it. (I've done a trial-and-error test with the new machine, to no
avail.)
Basically, I just need to figure out how to get the current SQL server
moved over to this new, more powerful machine. Something I can do at
night while people are gone, of course, so they can come in the next day
and never notice that anything changed.
Any ideas? I'm not a SQL Server expert, so I'm having a tough time
figuring out quite how to handle this.
-j