MSSQL 2000 DB Migration to Microsoft SQL 2005

Hi,
We're building new machine Windows 2003 with MSSQL 2005 server.
We have current machine running Windows 2000 with MSSQL 2000.
How do we migrate the MSSQL2000 database to MSSQL 2005 server?
A) My way: inplace upgrade (i know this one will 99% work!)[vbcol=seagreen]
w/MSSQL2000[vbcol=seagreen]
B) Another way: backup the MSSQL DB from Windows2000 and restore to
Windows2005 with MSSQL2005? work?
C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
work?
Any other way which will guarantee work best?
Thanks for any input!!
J.H
"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
> w/MSSQL2000
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
This will work.
I would do this.
That way if something "goes wrong" you still have your original 2000 DB and
a backup.
However, no matter WHAT choice you make, make sure to to test your
application thoroughly.
There shouldn't be any gotchas, but you never know.

> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com
|||I did attach/dettach for all my database. Now working wothout any problems.
Don't forget to change compatibility level to 9 after attaching database.
Ramunas
"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
> w/MSSQL2000
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>
sql

MSSQL 2000 DB Migration to Microsoft SQL 2005

Hi,
We're building new machine Windows 2003 with MSSQL 2005 server.
We have current machine running Windows 2000 with MSSQL 2000.
How do we migrate the MSSQL2000 database to MSSQL 2005 server?
A) My way: inplace upgrade (i know this one will 99% work!)
>> installing new Windows 2003R2 with MSSQL2000 w/SP4
>> restore the MSSQL2000 database file to the new machine Windows2003R2
w/MSSQL2000
>> doing inplace upgrade on Windows2003R2 w/MSSQL2000 /wSP4 >> MSSQL2005
B) Another way: backup the MSSQL DB from Windows2000 and restore to
Windows2005 with MSSQL2005? work?
C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
work?
Any other way which will guarantee work best?
Thanks for any input!!
J.H"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
>> installing new Windows 2003R2 with MSSQL2000 w/SP4
>> restore the MSSQL2000 database file to the new machine Windows2003R2
> w/MSSQL2000
>> doing inplace upgrade on Windows2003R2 w/MSSQL2000 /wSP4 >> MSSQL2005
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
This will work.
I would do this.
That way if something "goes wrong" you still have your original 2000 DB and
a backup.
However, no matter WHAT choice you make, make sure to to test your
application thoroughly.
There shouldn't be any gotchas, but you never know.
> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com|||I did attach/dettach for all my database. Now working wothout any problems.
Don't forget to change compatibility level to 9 after attaching database.
Ramunas
"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
> >> installing new Windows 2003R2 with MSSQL2000 w/SP4
> >> restore the MSSQL2000 database file to the new machine Windows2003R2
> w/MSSQL2000
> >> doing inplace upgrade on Windows2003R2 w/MSSQL2000 /wSP4 >> MSSQL2005
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>

MSSQL 2000 DB Migration to Microsoft SQL 2005

Hi,
We're building new machine Windows 2003 with MSSQL 2005 server.
We have current machine running Windows 2000 with MSSQL 2000.
How do we migrate the MSSQL2000 database to MSSQL 2005 server?
A) My way: inplace upgrade (i know this one will 99% work!)[vbcol=seagreen]
w/MSSQL2000[vbcol=seagreen]
B) Another way: backup the MSSQL DB from Windows2000 and restore to
Windows2005 with MSSQL2005? work?
C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
work?
Any other way which will guarantee work best?
Thanks for any input!!
J.H"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
> w/MSSQL2000
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
This will work.
I would do this.
That way if something "goes wrong" you still have your original 2000 DB and
a backup.
However, no matter WHAT choice you make, make sure to to test your
application thoroughly.
There shouldn't be any gotchas, but you never know.

> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>
Greg Moore
SQL Server DBA Consulting
Email: sql (at) greenms.com http://www.greenms.com|||I did attach/dettach for all my database. Now working wothout any problems.
Don't forget to change compatibility level to 9 after attaching database.
Ramunas
"J.H" <jpthsd@.hotmail.com> wrote in message
news:%239XXAO1aHHA.4616@.TK2MSFTNGP03.phx.gbl...
> Hi,
> We're building new machine Windows 2003 with MSSQL 2005 server.
> We have current machine running Windows 2000 with MSSQL 2000.
> How do we migrate the MSSQL2000 database to MSSQL 2005 server?
> A) My way: inplace upgrade (i know this one will 99% work!)
> w/MSSQL2000
> B) Another way: backup the MSSQL DB from Windows2000 and restore to
> Windows2005 with MSSQL2005? work?
> C) Detach and attach the database from MSSQL2000 and attach to MSSQL2005 ?
> work?
>
> Any other way which will guarantee work best?
> Thanks for any input!!
> J.H
>

MSP_CUBE tables not updating with current data

Hi there,

I have recently been put into a role working with Project Server Web Access and OLAP cubes. Am experiencing trouble displaying current data in the Portfolio Analyzer in Web Access.

After adding and deleting data, inlcuding projects and resources, the updates are not reflecting when analysing the cube data. I have successfully reprocessed the cube from the Analysis Manager but still does not show current data.

When looking at the MSP_CUBE_* tables in SQL Manager, these tables directly reflect the data displayed in the cube. ie. The non-current data.

Is there a specific way to update these tables with the current data from the ProjectServer tables ?

Thanks in advance,

Ben

Updating this source data is really a Project Server issue rather than an Analysis Services one. There might be some people here that use both, but you would be better off asking in a Project/ProjectServer focused forum or newsgroup.sql

MsDtsSrvr.exe memory leak?

In our current environment, we are running about 10,000 packages per day on a given 64 bit SSIS server.

The MSDtsSrvr.exe (SSIS service) process' memory working set size continues to grow until it consumes the memory on the machine.

Some of the packages do use a custom component. Could this be responsible for leaking memory in the MSDtsSrvr.exe process? Has a memory leak been confirmed in this process for the "first-party" components anyway?

More information about the possible memory leak.

The packages are run in in a CLR process with calls Package.Execute(), rather than being executed via dtexec or dtexecui or the designer. The reason for this approach is the ability to write a custom event handler with access to the package pointer, which other log handlers cannot do. The process runs Package.Execute() and exits, so there are 10,000 short-lived processes, each of which call Package.Execute() once.

To be slightly more specific about what the packages are doing, each of the 10,000 packages generally correlates to 1 source file, loading in dummy (aka inferred) dimension records, and then populating a fact table via a surrogate key pipeline.