May 22, 2003 at 9:19 am
I am trying to migrate msmdrep.mdb to SQL Server. I am planning to use Migration wizard provided by Analysis manager. My question is:
Do you typically create a seperate database for MSMDREP in SQLServer Or does it go into any of the existing system database in SQL Server. If you create a seperate database, what do you typically name it as? I understand you can name anything but is there a convention?
May 22, 2003 at 12:44 pm
SOMEONE REPLY PLEASE. I AM SURE MANY OF YOU HAVE DONE THIS.
May 22, 2003 at 1:22 pm
When in doubt, check Books Online. Quoting:
quote:
Before you start the Migrate Repository Wizard, create or identify the SQL Server database to which you want to migrate the Analysis Services repository.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/olapdmad/agregserver_23hv.asp
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
May 26, 2003 at 9:36 pm
I don't think there's a hard and fast rule on this question. Some store the repository in the msdb database and an argument could be made that this is reasonable given the nature of the meta-data being stored.
An equally reasonalbe argument could be made to create a seperate database for the repository. This offers the benefit of a clear naming convention & separate storage from business data and system tables.
From my prespective, I favor the second option. In this new database I store the repository and any control files I create for managing data loads (batchIDs, process dates, etc.)
I hope this helps,
Scot J Reagin
Scot J Reagin
sreagin@hitachiconsulting.com
June 2, 2003 at 2:23 am
The easiest thing to do is accept the default of migrating to MSDB. It's reasonable to store the repository here, since it will sit alongside the DTS packages and scheduled jobs that you will no doubt create to automate the administration of your database.
Steve
June 9, 2003 at 10:19 am
Hi Shaki,
Back in the days of SQL 7, we migrated it into a separate database and called it OLAP_Rep.
When the name change came with SQL 2000, some bright spark decided to rename everthing that began with OLAP to ANAL, so the database became ANAL_REP.
Needless to say, it has now been changed back - OLAP_Rep sounds a lot better!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply