![]() | |
![]() |
| | Thread Tools | Display Modes |
#21
| |||
| |||
|
|
I have not done mirroing on the Reporting Databases; but you should be able to change the recovery mode to full on the temp. The Report Services doesn't care about recovery mode as far as I know. It is just set that way so it doesn't grow out of control; but with Mirroring you have to montior that the log size anyway contionusly. So that shouldn't be an issue for you. As you pointed out the key-mangement issue; I am not sure how you will deal with that for Mirroring. Mohit K. Gupta B.Sc. CS, Minor Japanese MCTS: SQL Server 2005 http://sqllearnings.blogspot.com/ "Steven" wrote: Hello, We would like to use SQL Mirroring as a high availability option for our production environment. Our user databases are not a problem. It seems like SRS might be though. When using mirroring, the principal database needs to have it's recovery mode set to "full" and from what I understand if mirroring SRS, we need to mirror the ReportServerDB and the ReportServerTempDB. The later DB runs in simple mode (since it's tempdb). When doing SRS as part of H/A I understand that both DBs have to sync together. Is this doable and if so, can anyone point me in the right direction? I also am aware of the RSConfig and RSKeyMgmt issues. We are running SQL 2005 with SRS 2000 (will upgrade to SRS 2005 next year). Thanks so much, Steve |
#22
| |||
| |||
|
|
I have not done mirroing on the Reporting Databases; but you should be able to change the recovery mode to full on the temp. The Report Services doesn't care about recovery mode as far as I know. It is just set that way so it doesn't grow out of control; but with Mirroring you have to montior that the log size anyway contionusly. So that shouldn't be an issue for you. As you pointed out the key-mangement issue; I am not sure how you will deal with that for Mirroring. Mohit K. Gupta B.Sc. CS, Minor Japanese MCTS: SQL Server 2005 http://sqllearnings.blogspot.com/ "Steven" wrote: Hello, We would like to use SQL Mirroring as a high availability option for our production environment. Our user databases are not a problem. It seems like SRS might be though. When using mirroring, the principal database needs to have it's recovery mode set to "full" and from what I understand if mirroring SRS, we need to mirror the ReportServerDB and the ReportServerTempDB. The later DB runs in simple mode (since it's tempdb). When doing SRS as part of H/A I understand that both DBs have to sync together. Is this doable and if so, can anyone point me in the right direction? I also am aware of the RSConfig and RSKeyMgmt issues. We are running SQL 2005 with SRS 2000 (will upgrade to SRS 2005 next year). Thanks so much, Steve |
#23
| |||
| |||
|
|
I have not done mirroing on the Reporting Databases; but you should be able to change the recovery mode to full on the temp. The Report Services doesn't care about recovery mode as far as I know. It is just set that way so it doesn't grow out of control; but with Mirroring you have to montior that the log size anyway contionusly. So that shouldn't be an issue for you. As you pointed out the key-mangement issue; I am not sure how you will deal with that for Mirroring. Mohit K. Gupta B.Sc. CS, Minor Japanese MCTS: SQL Server 2005 http://sqllearnings.blogspot.com/ "Steven" wrote: Hello, We would like to use SQL Mirroring as a high availability option for our production environment. Our user databases are not a problem. It seems like SRS might be though. When using mirroring, the principal database needs to have it's recovery mode set to "full" and from what I understand if mirroring SRS, we need to mirror the ReportServerDB and the ReportServerTempDB. The later DB runs in simple mode (since it's tempdb). When doing SRS as part of H/A I understand that both DBs have to sync together. Is this doable and if so, can anyone point me in the right direction? I also am aware of the RSConfig and RSKeyMgmt issues. We are running SQL 2005 with SRS 2000 (will upgrade to SRS 2005 next year). Thanks so much, Steve |
#24
| |||
| |||
|
|
I have not done mirroing on the Reporting Databases; but you should be able to change the recovery mode to full on the temp. The Report Services doesn't care about recovery mode as far as I know. It is just set that way so it doesn't grow out of control; but with Mirroring you have to montior that the log size anyway contionusly. So that shouldn't be an issue for you. As you pointed out the key-mangement issue; I am not sure how you will deal with that for Mirroring. Mohit K. Gupta B.Sc. CS, Minor Japanese MCTS: SQL Server 2005 http://sqllearnings.blogspot.com/ "Steven" wrote: Hello, We would like to use SQL Mirroring as a high availability option for our production environment. Our user databases are not a problem. It seems like SRS might be though. When using mirroring, the principal database needs to have it's recovery mode set to "full" and from what I understand if mirroring SRS, we need to mirror the ReportServerDB and the ReportServerTempDB. The later DB runs in simple mode (since it's tempdb). When doing SRS as part of H/A I understand that both DBs have to sync together. Is this doable and if so, can anyone point me in the right direction? I also am aware of the RSConfig and RSKeyMgmt issues. We are running SQL 2005 with SRS 2000 (will upgrade to SRS 2005 next year). Thanks so much, Steve |
#25
| |||
| |||
|
|
I have not done mirroing on the Reporting Databases; but you should be able to change the recovery mode to full on the temp. The Report Services doesn't care about recovery mode as far as I know. It is just set that way so it doesn't grow out of control; but with Mirroring you have to montior that the log size anyway contionusly. So that shouldn't be an issue for you. As you pointed out the key-mangement issue; I am not sure how you will deal with that for Mirroring. Mohit K. Gupta B.Sc. CS, Minor Japanese MCTS: SQL Server 2005 http://sqllearnings.blogspot.com/ "Steven" wrote: Hello, We would like to use SQL Mirroring as a high availability option for our production environment. Our user databases are not a problem. It seems like SRS might be though. When using mirroring, the principal database needs to have it's recovery mode set to "full" and from what I understand if mirroring SRS, we need to mirror the ReportServerDB and the ReportServerTempDB. The later DB runs in simple mode (since it's tempdb). When doing SRS as part of H/A I understand that both DBs have to sync together. Is this doable and if so, can anyone point me in the right direction? I also am aware of the RSConfig and RSKeyMgmt issues. We are running SQL 2005 with SRS 2000 (will upgrade to SRS 2005 next year). Thanks so much, Steve |
#26
| |||
| |||
|
|
I have not done mirroing on the Reporting Databases; but you should be able to change the recovery mode to full on the temp. The Report Services doesn't care about recovery mode as far as I know. It is just set that way so it doesn't grow out of control; but with Mirroring you have to montior that the log size anyway contionusly. So that shouldn't be an issue for you. As you pointed out the key-mangement issue; I am not sure how you will deal with that for Mirroring. Mohit K. Gupta B.Sc. CS, Minor Japanese MCTS: SQL Server 2005 http://sqllearnings.blogspot.com/ "Steven" wrote: Hello, We would like to use SQL Mirroring as a high availability option for our production environment. Our user databases are not a problem. It seems like SRS might be though. When using mirroring, the principal database needs to have it's recovery mode set to "full" and from what I understand if mirroring SRS, we need to mirror the ReportServerDB and the ReportServerTempDB. The later DB runs in simple mode (since it's tempdb). When doing SRS as part of H/A I understand that both DBs have to sync together. Is this doable and if so, can anyone point me in the right direction? I also am aware of the RSConfig and RSKeyMgmt issues. We are running SQL 2005 with SRS 2000 (will upgrade to SRS 2005 next year). Thanks so much, Steve |
#27
| |||
| |||
|
|
I have not done mirroing on the Reporting Databases; but you should be able to change the recovery mode to full on the temp. The Report Services doesn't care about recovery mode as far as I know. It is just set that way so it doesn't grow out of control; but with Mirroring you have to montior that the log size anyway contionusly. So that shouldn't be an issue for you. As you pointed out the key-mangement issue; I am not sure how you will deal with that for Mirroring. Mohit K. Gupta B.Sc. CS, Minor Japanese MCTS: SQL Server 2005 http://sqllearnings.blogspot.com/ "Steven" wrote: Hello, We would like to use SQL Mirroring as a high availability option for our production environment. Our user databases are not a problem. It seems like SRS might be though. When using mirroring, the principal database needs to have it's recovery mode set to "full" and from what I understand if mirroring SRS, we need to mirror the ReportServerDB and the ReportServerTempDB. The later DB runs in simple mode (since it's tempdb). When doing SRS as part of H/A I understand that both DBs have to sync together. Is this doable and if so, can anyone point me in the right direction? I also am aware of the RSConfig and RSKeyMgmt issues. We are running SQL 2005 with SRS 2000 (will upgrade to SRS 2005 next year). Thanks so much, Steve |
#28
| |||
| |||
|
|
I have not done mirroing on the Reporting Databases; but you should be able to change the recovery mode to full on the temp. The Report Services doesn't care about recovery mode as far as I know. It is just set that way so it doesn't grow out of control; but with Mirroring you have to montior that the log size anyway contionusly. So that shouldn't be an issue for you. As you pointed out the key-mangement issue; I am not sure how you will deal with that for Mirroring. Mohit K. Gupta B.Sc. CS, Minor Japanese MCTS: SQL Server 2005 http://sqllearnings.blogspot.com/ "Steven" wrote: Hello, We would like to use SQL Mirroring as a high availability option for our production environment. Our user databases are not a problem. It seems like SRS might be though. When using mirroring, the principal database needs to have it's recovery mode set to "full" and from what I understand if mirroring SRS, we need to mirror the ReportServerDB and the ReportServerTempDB. The later DB runs in simple mode (since it's tempdb). When doing SRS as part of H/A I understand that both DBs have to sync together. Is this doable and if so, can anyone point me in the right direction? I also am aware of the RSConfig and RSKeyMgmt issues. We are running SQL 2005 with SRS 2000 (will upgrade to SRS 2005 next year). Thanks so much, Steve |
![]() |
| Thread Tools | |
| Display Modes | |
| |