Database Failover

Our reports are connecting to a database snapshot for their data. Periodically this snapshot loads, which means for a minute or two the reports go down. There is however another snapshot available, and between the two one will always be up. Is there a way with Reporting Services to dynamically switch between the two, depending on which one is up? These snapshots are on a constant schedule, so it would also acceptible (but not as nice), to have the database connection automatically switch at certain times of the day.

These snapshots are on the same server, or I would try using a failover partner in the connection string. To the best of my knowledge, this only switches servers, not the database instances.

No, there's no such feature. You could do this with a linked report, each which uses a snapshot which is generated on a different schedule. -- Then, your app could decide which one should be served based on when a user requests it. You'll always have one which is "ready" that way.

Database dump and load script

Hi,
Is anyone using a custom script, or anything else that helps allow software
developer's do their own database dump and loads rather than having to ask a
DBA every time? What are people using to allow this functionality?
We are looking to move this task from a DBA responsibility to allow for the
users to do their own database dumps and loads in the test and development
environments. The one problem we have is that the databases were not all
standardized to have the exact file path names when they are created. For
example, F:\MSSQL\data\<filename>.mdf. Some of them might be
F:\MSSQL\default\data\<filename>.mdf, etc.
Does anyone have this capability automated for what I am looking for?
Thanks for any feedback.
CynthiaWe wrote some scripts that perform these operations. Essentially, a control
table is created and populated for each DB. When a restore need to be
performed, a row is inserted into a table where a recurring job picks it up
and looks into the control tables for the necessary information. The job
generates on OSQL script and prevents the need for the developers to have
those sorts of rights necessesary to perform restores(may not be an issue for
you)
Jeff
"Cynthia" wrote:
> Hi,
> Is anyone using a custom script, or anything else that helps allow software
> developer's do their own database dump and loads rather than having to ask a
> DBA every time? What are people using to allow this functionality?
> We are looking to move this task from a DBA responsibility to allow for the
> users to do their own database dumps and loads in the test and development
> environments. The one problem we have is that the databases were not all
> standardized to have the exact file path names when they are created. For
> example, F:\MSSQL\data\<filename>.mdf. Some of them might be
> F:\MSSQL\default\data\<filename>.mdf, etc.
> Does anyone have this capability automated for what I am looking for?
> Thanks for any feedback.
> Cynthia

Database dump and load script

Hi,
Is anyone using a custom script, or anything else that helps allow software
developer's do their own database dump and loads rather than having to ask a
DBA every time? What are people using to allow this functionality?
We are looking to move this task from a DBA responsibility to allow for the
users to do their own database dumps and loads in the test and development
environments. The one problem we have is that the databases were not all
standardized to have the exact file path names when they are created. For
example, F:\MSSQL\data\<filename>.mdf. Some of them might be
F:\MSSQL\default\data\<filename>.mdf, etc.
Does anyone have this capability automated for what I am looking for?
Thanks for any feedback.
Cynthia
We wrote some scripts that perform these operations. Essentially, a control
table is created and populated for each DB. When a restore need to be
performed, a row is inserted into a table where a recurring job picks it up
and looks into the control tables for the necessary information. The job
generates on OSQL script and prevents the need for the developers to have
those sorts of rights necessesary to perform restores(may not be an issue for
you)
Jeff
"Cynthia" wrote:

> Hi,
> Is anyone using a custom script, or anything else that helps allow software
> developer's do their own database dump and loads rather than having to ask a
> DBA every time? What are people using to allow this functionality?
> We are looking to move this task from a DBA responsibility to allow for the
> users to do their own database dumps and loads in the test and development
> environments. The one problem we have is that the databases were not all
> standardized to have the exact file path names when they are created. For
> example, F:\MSSQL\data\<filename>.mdf. Some of them might be
> F:\MSSQL\default\data\<filename>.mdf, etc.
> Does anyone have this capability automated for what I am looking for?
> Thanks for any feedback.
> Cynthia

Database dump and load script

Hi,
Is anyone using a custom script, or anything else that helps allow software
developer's do their own database dump and loads rather than having to ask a
DBA every time? What are people using to allow this functionality?
We are looking to move this task from a DBA responsibility to allow for the
users to do their own database dumps and loads in the test and development
environments. The one problem we have is that the databases were not all
standardized to have the exact file path names when they are created. For
example, F:\MSSQL\data\<filename>.mdf. Some of them might be
F:\MSSQL\default\data\<filename>.mdf, etc.
Does anyone have this capability automated for what I am looking for?
Thanks for any feedback.
CynthiaWe wrote some scripts that perform these operations. Essentially, a control
table is created and populated for each DB. When a restore need to be
performed, a row is inserted into a table where a recurring job picks it up
and looks into the control tables for the necessary information. The job
generates on OSQL script and prevents the need for the developers to have
those sorts of rights necessesary to perform restores(may not be an issue fo
r
you)
Jeff
"Cynthia" wrote:

> Hi,
> Is anyone using a custom script, or anything else that helps allow softwar
e
> developer's do their own database dump and loads rather than having to ask
a
> DBA every time? What are people using to allow this functionality?
> We are looking to move this task from a DBA responsibility to allow for th
e
> users to do their own database dumps and loads in the test and development
> environments. The one problem we have is that the databases were not all
> standardized to have the exact file path names when they are created. For
> example, F:\MSSQL\data\<filename>.mdf. Some of them might be
> F:\MSSQL\default\data\<filename>.mdf, etc.
> Does anyone have this capability automated for what I am looking for?
> Thanks for any feedback.
> Cynthia