Showing posts with label similar. Show all posts
Showing posts with label similar. Show all posts

Thursday, March 8, 2012

BI Dev Studio - export the grid in Dimension Usage tab?

Is anyone aware of a simple way to export the grid (or similar contents) from the Dimension Usage tab in the cube designer?

I imagine it can be done by parsing the XML definition of the cube, but I'm not much of developer with that sort of thing, and I wondered if there's a simple way or a not-so-simple-but-already-written way to get this. I'm not picky about formatting (spreadsheet, text, whatever -- anything but a bitmap screenshot!).

Does anyone else think this would be a handy self documenting feature?

Thanks,

CJB

Keep an eye on http://www.codeplex.com/bidshelper as that feature should be posted within the next week or two. Basically it's going to spit out a print-friendly version of that dimension usage tab.|||I have an early release of this working on my machine at the moment. It prints out using nested groups rather than the matrix that you see in the report usage tab, but most of the info is in there. If you are interested in having a look at an early version contact me via my blog. Otherwise as Greg says, we should have a release out in the next week or two.|||

Thanks, I will keep an eye on that. I poked around on the codeplex projects that you and Mr. Gosbell are working on. I cringed at how much cooler it all is than anything I've put together.

I'm still climbing a .NET learning curve, which wasn't really necessary for me until recently -- as the use of SQL 2005 has begun to mature a bit, and the ease of integrating assemblies into SQL and SSAS has become so slick now, it's too valuable to ignore.

Thursday, February 16, 2012

Best way to maintain up to date SQL Jobs and SSIS on failover Serv

Hi,
on SQL 2005 we use log shipping to maintain our production server to an
alternate server. Now I would like to do something similar with our SQL
Agent jobs and SSIS. While those jobs are enabled on the production server,
I would like them to become disable on the alternate server, this process
would be scheduled once per day.
I'm sure there are many ways to achieve this, but I am wondering what would
be the most efficient.
any ideas ?
Thanks
Fred
ok, I just figured out how to transfer/disable jobs using the Transfer Job
task in SSIS, it's quite nice actually.
But, I am still in the dark on how to transfer SSIS from one server to
another.
BTW, a backup and restore of MSDB is out of the question.
Thanks
"FredDBA" wrote:

> Hi,
> on SQL 2005 we use log shipping to maintain our production server to an
> alternate server. Now I would like to do something similar with our SQL
> Agent jobs and SSIS. While those jobs are enabled on the production server,
> I would like them to become disable on the alternate server, this process
> would be scheduled once per day.
> I'm sure there are many ways to achieve this, but I am wondering what would
> be the most efficient.
> any ideas ?
> Thanks
> Fred

Best way to maintain up to date SQL Jobs and SSIS on failover Serv

Hi,
on SQL 2005 we use log shipping to maintain our production server to an
alternate server. Now I would like to do something similar with our SQL
Agent jobs and SSIS. While those jobs are enabled on the production server,
I would like them to become disable on the alternate server, this process
would be scheduled once per day.
I'm sure there are many ways to achieve this, but I am wondering what would
be the most efficient.
any ideas ?
Thanks
Fredok, I just figured out how to transfer/disable jobs using the Transfer Job
task in SSIS, it's quite nice actually.
But, I am still in the dark on how to transfer SSIS from one server to
another.
BTW, a backup and restore of MSDB is out of the question.
Thanks
"FredDBA" wrote:

> Hi,
> on SQL 2005 we use log shipping to maintain our production server to an
> alternate server. Now I would like to do something similar with our SQL
> Agent jobs and SSIS. While those jobs are enabled on the production serve
r,
> I would like them to become disable on the alternate server, this process
> would be scheduled once per day.
> I'm sure there are many ways to achieve this, but I am wondering what woul
d
> be the most efficient.
> any ideas ?
> Thanks
> Fred|||If its not too late, consider storing your SSIS packages in the
filesystem and just keep copies on your DR machines
Terry|||Anotther thing we do here (mostly for legacy dts packages) is to
restore the MSDB as another name. During DR, rename that database to
MSDB and all the objects will be there.
Terry

Best way to maintain up to date SQL Jobs and SSIS on failover Serv

Hi,
on SQL 2005 we use log shipping to maintain our production server to an
alternate server. Now I would like to do something similar with our SQL
Agent jobs and SSIS. While those jobs are enabled on the production server,
I would like them to become disable on the alternate server, this process
would be scheduled once per day.
I'm sure there are many ways to achieve this, but I am wondering what would
be the most efficient.
any ideas ?
Thanks
Fredok, I just figured out how to transfer/disable jobs using the Transfer Job
task in SSIS, it's quite nice actually.
But, I am still in the dark on how to transfer SSIS from one server to
another.
BTW, a backup and restore of MSDB is out of the question.
Thanks
"FredDBA" wrote:
> Hi,
> on SQL 2005 we use log shipping to maintain our production server to an
> alternate server. Now I would like to do something similar with our SQL
> Agent jobs and SSIS. While those jobs are enabled on the production server,
> I would like them to become disable on the alternate server, this process
> would be scheduled once per day.
> I'm sure there are many ways to achieve this, but I am wondering what would
> be the most efficient.
> any ideas ?
> Thanks
> Fred|||If its not too late, consider storing your SSIS packages in the
filesystem and just keep copies on your DR machines
Terry|||Anotther thing we do here (mostly for legacy dts packages) is to
restore the MSDB as another name. During DR, rename that database to
MSDB and all the objects will be there.
Terry