Migrating From Development to Production Environment in MSAS 2005

Hi,

I have built a project in Ananlysis Services 2005 and would like to migrate the contents of the Project ( Dimensions, Measures, Cubes Etc) to a New server having analysis Services 2005 , what is the best approach. Does microsoft provide any best practices document. I searched the forum and the topics on migration seem to be from Analysis Services 2000 to Analysis Services 2005, can some one guide me on migration between Analysis Services 2005 and 2005.

Thansks

A backup and restore (like in AS2000) is certainly possible. This is the only method if you need to get the data cube moved in a processed state (with data). Except you could use the new synchronization feature, but that would probably be using this feature for something it was not quite intended.

The recommended method would be using the new AS Deployment Wizard. Make a "build" in BI Development Studio of your database and fire up the AS Deployment Wizard. This will allow you to specify different settings for your cube database when it is deployed to the production server. For more info on how to use the Deployment Wizard, see http://msdn2.microsoft.com/en-US/library/ms176121.aspx

migrating db

I have an ms sql 2000 db which I am migrating from one shared environment to another. How specifcally can I do this?

I have a copy of enterprise but not a full version of SQL on my local desktop.
The hosting company from which I am moving has placed the db as a zip file on the root of my site via ftp. I have unzipped it and it appears as a backup copy (.bak).

I appreciate any detail steps, I assume via enterprise, that anyone can give me. Thank you.Create a database on your server, and then restore the backup to it.
For detailed steps, see Books Online.

Migrated Historical Snapshot

We have recently migrated (into a test environment) our RS2000 DB per the
microsoft migration instructions into RS2005.
When a history snapshot record is requested (Via ReportManager), we get an
internal RS Exception...
w3wp!library!1!11/13/2006-11:35:39:: i INFO: Call to
GetPermissions:<Roger!REPORTPATH>
w3wp!library!1!11/13/2006-11:35:39:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., Error compressing;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details.
w3wp!library!1!11/13/2006-11:35:40:: i INFO: Exception dumped to: C:\Program
Files\Microsoft SQL Server\MSSQL.5\Reporting Services\LogFiles flags=
ReferencedMemory, AllThreads, SendToWatson
w3wp!chunks!1!11/13/2006-11:35:40:: e ERROR: ###
SnapshotConverter(cb8c0d49-39e1-4775-ae6f-f73ac0fc68c4, True),
Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details.
at Microsoft.ReportingServices.Diagnostics.CompressUt il.checkErr(Int32 err)
at Microsoft.ReportingServices.Diagnostics.CompressUt il.UnCompress(Byte[]
input, Int32 outputBufferLength, Byte[]& output)
at
Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.UncompressNative(Byte[]
compressedBuffer, Int32 uncompressedBufferLength, Byte[]& uncompressedBuffer)
at
Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.Uncompress(Byte[]
compressedBuffer, Int32 uncompressedBufferLength, Byte[]& uncompressedBuffer)
at
Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.ReadAndUncompressBuffer()
at
Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.FillBuffer()
at
Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream..ctor(Stream
store, Int16 version)
at
Microsoft.ReportingServices.Library.SnapshotChunkS treamFactory.CreateReadStream(Guid
snapshotDataID, Boolean isPermanentSnapshot, String chunkName, Int32
chunkType, Boolean rawStreamRequested, ConnectionManager connectionManager,
String& mimeType)
at
Microsoft.ReportingServices.Library.SnapshotChunkS treamFactory.GetCompressedReadStream(Guid
snapshotDataID, Boolean isPermanentSnapshot, String chunkName, Int32
chunkType, ConnectionManager connectionManager, String& mimeType)
at
Microsoft.ReportingServices.Library.SnapshotConver ter.ConvertFromV1(ReportSnapshot snapshot, Boolean isSnapshotProcessing)
Has anyone sucessfully migrated history from RS2000 to RS2005?
- Roger
Could you post this in the reporting services newsgroup? I think it belongs
there.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tx Whytboy" <TxWhytboy@.discussions.microsoft.com> wrote in message
news:18002B03-FAED-4825-A6E7-ED56B8668B77@.microsoft.com...
> We have recently migrated (into a test environment) our RS2000 DB per the
> microsoft migration instructions into RS2005.
> When a history snapshot record is requested (Via ReportManager), we get an
> internal RS Exception...
> w3wp!library!1!11/13/2006-11:35:39:: i INFO: Call to
> GetPermissions:<Roger!REPORTPATH>
> w3wp!library!1!11/13/2006-11:35:39:: e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more
> details., Error compressing;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more
> details.
> w3wp!library!1!11/13/2006-11:35:40:: i INFO: Exception dumped to:
> C:\Program
> Files\Microsoft SQL Server\MSSQL.5\Reporting Services\LogFiles flags=
> ReferencedMemory, AllThreads, SendToWatson
> w3wp!chunks!1!11/13/2006-11:35:40:: e ERROR: ###
> SnapshotConverter(cb8c0d49-39e1-4775-ae6f-f73ac0fc68c4, True),
> Microsoft.ReportingServices.Diagnostics.Utilities. InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more
> details.
> at Microsoft.ReportingServices.Diagnostics.CompressUt il.checkErr(Int32
> err)
> at
> Microsoft.ReportingServices.Diagnostics.CompressUt il.UnCompress(Byte[]
> input, Int32 outputBufferLength, Byte[]& output)
> at
> Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.UncompressNative(Byte[]
> compressedBuffer, Int32 uncompressedBufferLength, Byte[]&
> uncompressedBuffer)
> at
> Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.Uncompress(Byte[]
> compressedBuffer, Int32 uncompressedBufferLength, Byte[]&
> uncompressedBuffer)
> at
> Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.ReadAndUncompressBuffer()
> at
> Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream.FillBuffer()
> at
> Microsoft.ReportingServices.Library.BufferedCompre ssedReadStream..ctor(Stream
> store, Int16 version)
> at
> Microsoft.ReportingServices.Library.SnapshotChunkS treamFactory.CreateReadStream(Guid
> snapshotDataID, Boolean isPermanentSnapshot, String chunkName, Int32
> chunkType, Boolean rawStreamRequested, ConnectionManager
> connectionManager,
> String& mimeType)
> at
> Microsoft.ReportingServices.Library.SnapshotChunkS treamFactory.GetCompressedReadStream(Guid
> snapshotDataID, Boolean isPermanentSnapshot, String chunkName, Int32
> chunkType, ConnectionManager connectionManager, String& mimeType)
> at
> Microsoft.ReportingServices.Library.SnapshotConver ter.ConvertFromV1(ReportSnapshot
> snapshot, Boolean isSnapshotProcessing)
>
> Has anyone sucessfully migrated history from RS2000 to RS2005?
> - Roger
|||Yeah.. Missed it by one.. and I didnt realize that...
Sorry!
"Hilary Cotter" wrote:

> Could you post this in the reporting services newsgroup? I think it belongs
> there.
> --
> Hilary Cotter
sql

Migrate SSRS 2005 Reports

Hi,

I need to move few folders from our DEV SSRS 2005 environment to another
server. Folders will be moved to new parent folders.
Is there any tool that I can use fot this purpose?
I used RSScripter from SQLdbatips.com. Although the tool works great but it
can't script multiple folder reports. I have to script one by one and it is
a big problem.

Thanks
AlexIt cannot? I have version 2.0.0.6 and I can select multiple folders.

migrate SQL server 2000 DB on hosted environment to SQL 2k5 express

I have web application and sql server 2k database in hosted environment. How can migrate my database to another server where I have SQL Server Express 2005.
I cant take backup or I cant stop the server as it is hosted environment sharing many databases. Note that I dont want to loose single transaction in this process..Is there any way to do this.

Thanks in advance

I suspect you're going to have to accept some window of downtime to accomplish the upgrade. You might post a question to the database engine forum about ways to minimize the downtime, as this is a common sort of request.

migrate SQL server 2000 DB on hosted environment to SQL 2k5 express

I have web application and sql server 2k database in hosted environment. How can migrate my database to another server where I have SQL Server Express 2005.
I cant take backup or I cant stop the server as it is hosted environment sharing many databases. Note that I dont want to loose single transaction in this process..Is there any way to do this.

Thanks in advance

I suspect you're going to have to accept some window of downtime to accomplish the upgrade. You might post a question to the database engine forum about ways to minimize the downtime, as this is a common sort of request.

sql

Migrate SQL 2000 to New SQL 2005 Installation.

Hi all, in my current environment, I have a single server SQL 2000 setup that's being replaced. I'm in the process of installing a new SQL 2005 cluster with the thought of taking advantage of 2005 mirroring and clustering, but have a few questions.

1. My thinking is that I can migrate my 2000 databases to 2005, but leave the databases in 8.0 (2000) mode. Are there any issues with this? I know they won't take advantage of the 2005 performance boost

2. Some of the apps don't support 2005 yet so I need to leave them in 2000 mode until they do. Is SQL 2005 fully backwards compatible with a SQL 2000 database?

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode?

Thanks for any assistance with this!

Start by running the SQL Server 2005 upgrade advisor against your SQL 2000 installation. This will give you good information on problems that you might need to address. Also, if your applications are purchased, check with the vendors for advice on compatibility. But the bottom line is that every application is unique and the only way you'll know for sure is by carefully testing.

Sorry, I don't know the answer to your question on mirroring.

Paul

|||Thanks for the response Paul, Doesn't the upgrade advisor only tell me info in regards to actually upgrading the database? I'm looking at keeping them at 8.0 compatibility on SQL 2005. Basically, I'm looking at keeping the databases at the SQL2000 level on a SQL2005 box. I guess my real question is: Are databases that are running in SQL2000 compatibility mode on a SQL2005 box fully backwards compatible?|||

Most applications will upgrade with no problems but there are a small number of breaking changes in 9.0, even if you stay in 8.0 compat mode. Look up "compatibility" and "sp_dbcmptlevel" in BOL for details.

|||

hi Tynman

Yes u can always keep SQL2000 database compatibility level i.e. 80 in sql 2005 by specifying compatibility level in system stored procedure "sp_dbcmptlevel" and give compatibility level as 80 with database name.

Ur command will be: sp_dbcmplevel dbname, 80

|||

BUMP!

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode (compatibility level 80)?

Do anyone have an answer to this question?

|||I am trying to restore a SQL 2005 DB into SQL 2000 and it errors out "too many objects on 64 allowed......blah..blah..blah.." something to that effect.

Migrate SQL 2000 to New SQL 2005 Installation.

Hi all, in my current environment, I have a single server SQL 2000 setup that's being replaced. I'm in the process of installing a new SQL 2005 cluster with the thought of taking advantage of 2005 mirroring and clustering, but have a few questions.

1. My thinking is that I can migrate my 2000 databases to 2005, but leave the databases in 8.0 (2000) mode. Are there any issues with this? I know they won't take advantage of the 2005 performance boost

2. Some of the apps don't support 2005 yet so I need to leave them in 2000 mode until they do. Is SQL 2005 fully backwards compatible with a SQL 2000 database?

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode?

Thanks for any assistance with this!

Start by running the SQL Server 2005 upgrade advisor against your SQL 2000 installation. This will give you good information on problems that you might need to address. Also, if your applications are purchased, check with the vendors for advice on compatibility. But the bottom line is that every application is unique and the only way you'll know for sure is by carefully testing.

Sorry, I don't know the answer to your question on mirroring.

Paul

|||Thanks for the response Paul, Doesn't the upgrade advisor only tell me info in regards to actually upgrading the database? I'm looking at keeping them at 8.0 compatibility on SQL 2005. Basically, I'm looking at keeping the databases at the SQL2000 level on a SQL2005 box. I guess my real question is: Are databases that are running in SQL2000 compatibility mode on a SQL2005 box fully backwards compatible?|||

Most applications will upgrade with no problems but there are a small number of breaking changes in 9.0, even if you stay in 8.0 compat mode. Look up "compatibility" and "sp_dbcmptlevel" in BOL for details.

|||

hi Tynman

Yes u can always keep SQL2000 database compatibility level i.e. 80 in sql 2005 by specifying compatibility level in system stored procedure "sp_dbcmptlevel" and give compatibility level as 80 with database name.

Ur command will be: sp_dbcmplevel dbname, 80

|||

BUMP!

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode (compatibility level 80)?

Do anyone have an answer to this question?

|||I am trying to restore a SQL 2005 DB into SQL 2000 and it errors out "too many objects on 64 allowed......blah..blah..blah.." something to that effect.sql

Migrate SQL 2000 to New SQL 2005 Installation.

Hi all, in my current environment, I have a single server SQL 2000 setup that's being replaced. I'm in the process of installing a new SQL 2005 cluster with the thought of taking advantage of 2005 mirroring and clustering, but have a few questions.

1. My thinking is that I can migrate my 2000 databases to 2005, but leave the databases in 8.0 (2000) mode. Are there any issues with this? I know they won't take advantage of the 2005 performance boost

2. Some of the apps don't support 2005 yet so I need to leave them in 2000 mode until they do. Is SQL 2005 fully backwards compatible with a SQL 2000 database?

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode?

Thanks for any assistance with this!

Start by running the SQL Server 2005 upgrade advisor against your SQL 2000 installation. This will give you good information on problems that you might need to address. Also, if your applications are purchased, check with the vendors for advice on compatibility. But the bottom line is that every application is unique and the only way you'll know for sure is by carefully testing.

Sorry, I don't know the answer to your question on mirroring.

Paul

|||Thanks for the response Paul, Doesn't the upgrade advisor only tell me info in regards to actually upgrading the database? I'm looking at keeping them at 8.0 compatibility on SQL 2005. Basically, I'm looking at keeping the databases at the SQL2000 level on a SQL2005 box. I guess my real question is: Are databases that are running in SQL2000 compatibility mode on a SQL2005 box fully backwards compatible?|||

Most applications will upgrade with no problems but there are a small number of breaking changes in 9.0, even if you stay in 8.0 compat mode. Look up "compatibility" and "sp_dbcmptlevel" in BOL for details.

|||

hi Tynman

Yes u can always keep SQL2000 database compatibility level i.e. 80 in sql 2005 by specifying compatibility level in system stored procedure "sp_dbcmptlevel" and give compatibility level as 80 with database name.

Ur command will be: sp_dbcmplevel dbname, 80

|||

BUMP!

3. Will mirroring work on SQL 2005 with a database that is still in 2000 mode (compatibility level 80)?

Do anyone have an answer to this question?

|||I am trying to restore a SQL 2005 DB into SQL 2000 and it errors out "too many objects on 64 allowed......blah..blah..blah.." something to that effect.

migrate from Oracle to sql server expresse

I want to find out if .net + java + sql server etc is a replacement for my present development environment.

However, I cannot migrate an Oracle database to SQL server express. SSMA does not work. Is there another way to migrate my Oraclke database to SQL server express?

If you are doing development then buy a copy of Dev Edition its $50 from Amazon, its a dev/test use only copy of Enterprise Edition. You can still deploy to express but I recomend using Dev for dev/test

Microsoft.SQLServer.ManagedDTS.dll reference error in VB.Net 2002

I am using VB.NET 2002 and we have set up a test environment running SQL Server 2005.

I am trying to add a reference to Microsoft.SQLServer.ManagedDTS.dll which is required to run a DTS/SSIS package from VB.NET.

However the dll does not show in my add reference listing so when I select BROWSE and select the actual DLL I get a rather long error message telling me that only 'dll' and COM components can be referenced.

The exact message is:

A reference to 'C:\Programs Files\Microsoft SQL Server\90\SDK\Assemblies\Microsoft.SQLServer.ManagedDTS.dll' could not be added. This is not a valid assembly or COM component. Only assemblies with extension 'dll' and COM components can be referenced. Please make sure that the file is accessible, and that it is a valid assembly or COM component.

Any suggestions?

thanks

AFAIK, you never will be able to add such assembly from Framework 1.0/1.1

|||

enric vives wrote:

AFAIK, you never will be able to add such assembly from Framework 1.0/1.1

Correct. He would need to use Visual Basic 2005 (which implements .NET 2.0) instead.|||

Thank you. I thought that may be the case. I will load up VS 2005 and go from there.

Thanks again!