How to deploy project changes without wiping out cube data?

I have several cubes deployed with several years worth of historical data. Every time that I add a measure item or make any minor change to the cube or project from BI Dev Studio and then deploy it to the server, it wipes out all of my cube data causing me to reprocess all of the cube partitions again. Is there a way to avoid having to do this or a better way to deploy metadata changes to the cubes?

Thanks!

Hello!

I do not understand the difference or any change in behaviour since OLAP Services(7). Since then, every time you make a major structural change to a cube, like adding a new measure, you have been forced to full process the cube and all related dimensions.

Nothing have changed in SSAS2005.

Regards

Thomas Ivarsson

|||Set the properties for your SSAS solution so that the Deployment Mode is "Deploy Changes Only" (This should be the default) and the Processing Option is "Default". If the changes are "minor", a full rebuild will not be required. Adding a new measure will require a complete rebuild of the measure group though.

How to deploy large sets of data.

How can a large set of data be deployed and implemented by a local DBA.
Large set of data for example over 1 Gigabyte.
For example consisting of 1000 rows of data.
For example for text data ?
Or for binairy data ?
Large set of data, for example over 3 Gigabyte and consisting of
many rows ? (Milions of rows).
The implementation has to be as simple as possible for the local DBA,
thanks for your attention,
ben brugman
1 way would be :-
Copy the data out of SQL Server to a text file via (DTS, BCP)
The local DBA then runs a BULK INSERT script to import
HTH. Ryan
"ben brugman" <ben@.niethier.nl> wrote in message
news:%23Y4af8qGGHA.740@.TK2MSFTNGP12.phx.gbl...
> How can a large set of data be deployed and implemented by a local DBA.
> Large set of data for example over 1 Gigabyte.
> For example consisting of 1000 rows of data.
> For example for text data ?
> Or for binairy data ?
> Large set of data, for example over 3 Gigabyte and consisting of
> many rows ? (Milions of rows).
> The implementation has to be as simple as possible for the local DBA,
> thanks for your attention,
> ben brugman
>
|||"ben brugman" <ben@.niethier.nl> wrote in message
news:%23Y4af8qGGHA.740@.TK2MSFTNGP12.phx.gbl...
> How can a large set of data be deployed and implemented by a local DBA.
> Large set of data for example over 1 Gigabyte.
> For example consisting of 1000 rows of data.
> For example for text data ?
> Or for binairy data ?
> Large set of data, for example over 3 Gigabyte and consisting of
> many rows ? (Milions of rows).
> The implementation has to be as simple as possible for the local DBA,
> thanks for your attention,
> ben brugman
>
There are several approaces that you can take...
Use multiple files for your data and use sp_detach_db and sp_attach_db.
(Script any SQL authenticated logins if moving to a new machine in a new
environment)
Simply use Backup and Restore.
(Script any SQL authenticated logins if moving to a new machine in a new
environment)
If there are size issues. For example a 3GB backup file is too big to FTP,
or put on a CD etc. You could do a multi-file backup, Zip each file and
then move them. Unzip and restore.
Those are probably the easiest for a dba to perform.
Rick Sawtell
MCT, MCSD, MCDBA

How to deploy large sets of data.

How can a large set of data be deployed and implemented by a local DBA.
Large set of data for example over 1 Gigabyte.
For example consisting of 1000 rows of data.
For example for text data ?
Or for binairy data ?
Large set of data, for example over 3 Gigabyte and consisting of
many rows ? (Milions of rows).
The implementation has to be as simple as possible for the local DBA,
thanks for your attention,
ben brugman1 way would be :-
Copy the data out of SQL Server to a text file via (DTS, BCP)
The local DBA then runs a BULK INSERT script to import
HTH. Ryan
"ben brugman" <ben@.niethier.nl> wrote in message
news:%23Y4af8qGGHA.740@.TK2MSFTNGP12.phx.gbl...
> How can a large set of data be deployed and implemented by a local DBA.
> Large set of data for example over 1 Gigabyte.
> For example consisting of 1000 rows of data.
> For example for text data ?
> Or for binairy data ?
> Large set of data, for example over 3 Gigabyte and consisting of
> many rows ? (Milions of rows).
> The implementation has to be as simple as possible for the local DBA,
> thanks for your attention,
> ben brugman
>|||"ben brugman" <ben@.niethier.nl> wrote in message
news:%23Y4af8qGGHA.740@.TK2MSFTNGP12.phx.gbl...
> How can a large set of data be deployed and implemented by a local DBA.
> Large set of data for example over 1 Gigabyte.
> For example consisting of 1000 rows of data.
> For example for text data ?
> Or for binairy data ?
> Large set of data, for example over 3 Gigabyte and consisting of
> many rows ? (Milions of rows).
> The implementation has to be as simple as possible for the local DBA,
> thanks for your attention,
> ben brugman
>
There are several approaces that you can take...
Use multiple files for your data and use sp_detach_db and sp_attach_db.
(Script any SQL authenticated logins if moving to a new machine in a new
environment)
Simply use Backup and Restore.
(Script any SQL authenticated logins if moving to a new machine in a new
environment)
If there are size issues. For example a 3GB backup file is too big to FTP,
or put on a CD etc. You could do a multi-file backup, Zip each file and
then move them. Unzip and restore.
Those are probably the easiest for a dba to perform.
Rick Sawtell
MCT, MCSD, MCDBA

How to deploy large sets of data.

How can a large set of data be deployed and implemented by a local DBA.
Large set of data for example over 1 Gigabyte.
For example consisting of 1000 rows of data.
For example for text data ?
Or for binairy data ?
Large set of data, for example over 3 Gigabyte and consisting of
many rows ? (Milions of rows).
The implementation has to be as simple as possible for the local DBA,
thanks for your attention,
ben brugman1 way would be :-
Copy the data out of SQL Server to a text file via (DTS, BCP)
The local DBA then runs a BULK INSERT script to import
--
HTH. Ryan
"ben brugman" <ben@.niethier.nl> wrote in message
news:%23Y4af8qGGHA.740@.TK2MSFTNGP12.phx.gbl...
> How can a large set of data be deployed and implemented by a local DBA.
> Large set of data for example over 1 Gigabyte.
> For example consisting of 1000 rows of data.
> For example for text data ?
> Or for binairy data ?
> Large set of data, for example over 3 Gigabyte and consisting of
> many rows ? (Milions of rows).
> The implementation has to be as simple as possible for the local DBA,
> thanks for your attention,
> ben brugman
>|||"ben brugman" <ben@.niethier.nl> wrote in message
news:%23Y4af8qGGHA.740@.TK2MSFTNGP12.phx.gbl...
> How can a large set of data be deployed and implemented by a local DBA.
> Large set of data for example over 1 Gigabyte.
> For example consisting of 1000 rows of data.
> For example for text data ?
> Or for binairy data ?
> Large set of data, for example over 3 Gigabyte and consisting of
> many rows ? (Milions of rows).
> The implementation has to be as simple as possible for the local DBA,
> thanks for your attention,
> ben brugman
>
There are several approaces that you can take...
Use multiple files for your data and use sp_detach_db and sp_attach_db.
(Script any SQL authenticated logins if moving to a new machine in a new
environment)
Simply use Backup and Restore.
(Script any SQL authenticated logins if moving to a new machine in a new
environment)
If there are size issues. For example a 3GB backup file is too big to FTP,
or put on a CD etc. You could do a multi-file backup, Zip each file and
then move them. Unzip and restore.
Those are probably the easiest for a dba to perform.
Rick Sawtell
MCT, MCSD, MCDBA

How to deploy a single package of a multiple package solution

Hi,

I have a multiple package solution that I've deployed using the manifest file produced with the development environment. If I need to make a change to a single package, how do I then deploy this package? Is it a case of rebuilding the entire solution and re-running the manifest file, or is there a simpler way?

Any help would be much appreciated, cheers.

Can't you just go into the bin folder of your solution and select the appropriate package then copy this to your desired location?|||

I've experienced some strange behaviour doing this in the past that was solved by redeploying the entire solution using the deployment wizard. So I wasn't sure if there was something going on with the registry that I wasn't appreciating.

Are you confident that simply copying a modified package to the SSIS package store location will work consistently?

|||

To be perfectly honest, I've never used the manifest or deployment utility. All I ever do is copy the package from the bin folder to my release folder. I then use the SQL package store and import from my release folder (although you can do this from your development directory, I like to keep one additional layer of last good build that I can reimport to the sql package store if worst comes to worst).

I do not believe that there is anything modified in the registry at any point in time during package deployment. I could very well be wrong, but from what I have read that is not the case. (NOTE: there is the possibility that you are using registry configurations, which you will need to set up in your new location)

-- From Microsoft SQL Server 2005 Integration Services by Kirk Haselden

"Integration Services provides a utility for moving packages, butfor a moment, let's take a step back and think about the deployment problem. What is it you're trying to accomplish? Is there something in the package, some setting or variable that can't be moved by simply copying the package to another machine? Not really. However, problems arise when you move a package that references external resources that are available on one machine that aren't available on another. For example, no amount of configuration magic is going to help if you attempt to run a package that references a custom task that isn't installed on the destination machine."

|||

Ah, maybe that is the answer, simply use the Import option to load modified packages to the SSIS package store. Thanks for taking the time to reply, much appreciated.

HOW TO DEPLOY A PROJECT TO REMOTE SERVER(starve for)

hi ,i want to deploy an project(BI) which is been deployed successful on my computer to remote server,the server name is boco-ace.i do not kown how to do?could you give me an solution?if you give an example,i cannot bear to appreciate.

Several ways:

First.
Right click on your project name in the BI Dev Studio select "Properties". Click on "Deployment" node on the left and you will see the name of the server you deploying to. By default it is "localhost" , change it to boco-ace

Second.
Open SQL Management Studio. Right Click on your database name->Script database to->Create ...
Send resulting script to your new server. Make sure you process your database after creating it.

Third.
Run MigrationWizard application and point it to the project files. At some point it will ask you which server you'd like to deploy it to.

I am sure I can come up with some more.. Like Sync , Backup/Restore, ...

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||the first way i did ,but it dap an error "systerm error:no mapping is completed between account and security id",why?|||

i think maybe because i built roles,so i delete the role.but it daps another error"login failed for user"NT AUTHORITY\ANONYMOUS LOGON"",i do not know how to correct it?

thanks.

database's login mode is SQL's security

|||

You should use windows integrated security when connecting to Analysis Server.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

HOW TO DEPLOY A PROJECT TO REMOTE SERVER

hi ,i want to deploy an project(BI) which is been deployed successful on my computer to remote server,the server name is boco-ace.i do not kown how to do?could you give me an solution?if you give an example,i cannot bear to appreciate.

Several ways:

First.
Right click on your project name in the BI Dev Studio select "Properties". Click on "Deployment" node on the left and you will see the name of the server you deploying to. By default it is "localhost" , change it to boco-ace

Second.
Open SQL Management Studio. Right Click on your database name->Script database to->Create ...
Send resulting script to your new server. Make sure you process your database after creating it.

Third.
Run MigrationWizard application and point it to the project files. At some point it will ask you which server you'd like to deploy it to.

I am sure I can come up with some more.. Like Sync , Backup/Restore, ...

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||the first way i did ,but it dap an error "systerm error:no mapping is completed between account and security id",why?|||

i think maybe because i built roles,so i delete the role.but it daps another error"login failed for user"NT AUTHORITY\ANONYMOUS LOGON"",i do not know how to correct it?

thanks.

database's login mode is SQL's security

|||

You should use windows integrated security when connecting to Analysis Server.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.