![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
How do you copy and paste an SSAS 2005 cube from one database to another. Copy and paste is a great SSAS 2000 functionality that allows us to quickly make copies and test changes. Can we do the same in 2005? if so how? if not why the heck not? N.B I'm using the microsoft freebie "SQL Server 2005 - personal edition". |
#3
| |||
| |||
|
|
you can create the XML/A commands to create the new database. (right click on the original then go to the right submenu) "HWUK" <HWUK (AT) discussions (DOT) microsoft.com> wrote in message news:BF2678A6-6B87-4809-9F2B-C5D901C69607 (AT) microsoft (DOT) com... How do you copy and paste an SSAS 2005 cube from one database to another. Copy and paste is a great SSAS 2000 functionality that allows us to quickly make copies and test changes. Can we do the same in 2005? if so how? if not why the heck not? N.B I'm using the microsoft freebie "SQL Server 2005 - personal edition". |
#4
| |||
| |||
|
|
I've tried that but it dosn't copy the dimensions or datasourse. I want to be able to copy a cube paste it in a different database and process, I dont want to have to script out every object individually and then script it back in. Is this a huge oversight by microsoft of developers needs? "Jéjé" wrote: you can create the XML/A commands to create the new database. (right click on the original then go to the right submenu) "HWUK" <HWUK (AT) discussions (DOT) microsoft.com> wrote in message news:BF2678A6-6B87-4809-9F2B-C5D901C69607 (AT) microsoft (DOT) com... How do you copy and paste an SSAS 2005 cube from one database to another. Copy and paste is a great SSAS 2000 functionality that allows us to quickly make copies and test changes. Can we do the same in 2005? if so how? if not why the heck not? N.B I'm using the microsoft freebie "SQL Server 2005 - personal edition". |
#5
| |||
| |||
|
|
If you want cubes, data sources and diemnsions, then script out the database. Jéjé is absolutely right -- you use scripting to implement the same functionality as cut-paste. Getting similar functional to Analysis Manager was not possible since there is no similar technique with SQL Server RDBMS. This is one of the areas where the merging of the AS and RDBMS tools (such as SSMS, Profiler) hurt us -- but there are lots of areas where the merging helped us, e.g. the entire scripting subsystem, being able to administer AS right next to its RDBMS data source, SQL Profiler support, MDX color coding in SSMS, etc. |
#6
| |||
| |||
|
|
If you want cubes, data sources and diemnsions, then script out the database. Jéjé is absolutely right -- you use scripting to implement the same functionality as cut-paste. Getting similar functional to Analysis Manager was not possible since there is no similar technique with SQL Server RDBMS. This is one of the areas where the merging of the AS and RDBMS tools (such as SSMS, Profiler) hurt us -- but there are lots of areas where the merging helped us, e.g. the entire scripting subsystem, being able to administer AS right next to its RDBMS data source, SQL Profiler support, MDX color coding in SSMS, etc. -- Dave Wickert [MSFT] dwickert (AT) online (DOT) microsoft.com Program Manager BI Systems Team SQL BI Product Unit (Analysis Services) -- This posting is provided "AS IS" with no warranties, and confers no rights. "HWUK" <HWUK (AT) discussions (DOT) microsoft.com> wrote in message news:3050E2BD-A311-4DF2-8507-E35031DB6269 (AT) microsoft (DOT) com... I've tried that but it dosn't copy the dimensions or datasourse. I want to be able to copy a cube paste it in a different database and process, I dont want to have to script out every object individually and then script it back in. Is this a huge oversight by microsoft of developers needs? "Jéjé" wrote: you can create the XML/A commands to create the new database. (right click on the original then go to the right submenu) "HWUK" <HWUK (AT) discussions (DOT) microsoft.com> wrote in message news:BF2678A6-6B87-4809-9F2B-C5D901C69607 (AT) microsoft (DOT) com... How do you copy and paste an SSAS 2005 cube from one database to another. Copy and paste is a great SSAS 2000 functionality that allows us to quickly make copies and test changes. Can we do the same in 2005? if so how? if not why the heck not? N.B I'm using the microsoft freebie "SQL Server 2005 - personal edition". |
#7
| |||
| |||
|
|
If you are developing using a solution/project in BIDS you can also go into the properties of the solution and change the deployment target database and/or server/instance. You could either make a copy of your solution before making changes, or if you have a source code control system you could use that to maintain the various "releases" of the database. -- Regards Darren Gosbell [MCSD] Blog: http://www.geekswithblogs.net/darrengosbell In article <O0K0wFmLGHA.532 (AT) TK2MSFTNGP15 (DOT) phx.gbl>, dwickert (AT) online (DOT) microsoft.com says... If you want cubes, data sources and diemnsions, then script out the database. Jéjé is absolutely right -- you use scripting to implement the same functionality as cut-paste. Getting similar functional to Analysis Manager was not possible since there is no similar technique with SQL Server RDBMS. This is one of the areas where the merging of the AS and RDBMS tools (such as SSMS, Profiler) hurt us -- but there are lots of areas where the merging helped us, e.g. the entire scripting subsystem, being able to administer AS right next to its RDBMS data source, SQL Profiler support, MDX color coding in SSMS, etc. |
#8
| |||
| |||
|
|
Thanks for that Darren, I'll give it a try going forward. At the moment the cubes I have are migrated from AS 2000 and arn't part of any solution or project, so I've been looking at ways to do it in Management Studio. "Darren Gosbell" wrote: If you are developing using a solution/project in BIDS you can also go into the properties of the solution and change the deployment target database and/or server/instance. You could either make a copy of your solution before making changes, or if you have a source code control system you could use that to maintain the various "releases" of the database. -- Regards Darren Gosbell [MCSD] Blog: http://www.geekswithblogs.net/darrengosbell In article <O0K0wFmLGHA.532 (AT) TK2MSFTNGP15 (DOT) phx.gbl>, dwickert (AT) online (DOT) microsoft.com says... If you want cubes, data sources and diemnsions, then script out the database. Jéjé is absolutely right -- you use scripting to implement the same functionality as cut-paste. Getting similar functional to Analysis Manager was not possible since there is no similar technique with SQL Server RDBMS. This is one of the areas where the merging of the AS and RDBMS tools (such as SSMS, Profiler) hurt us -- but there are lots of areas where the merging helped us, e.g. the entire scripting subsystem, being able to administer AS right next to its RDBMS data source, SQL Profiler support, MDX color coding in SSMS, etc. |
![]() |
| Thread Tools | |
| Display Modes | |
| |