network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 9 months |
| seen | Feb 5 at 20:27 | |
| stats | profile views | 4 |
|
May 14 |
awarded | Popular Question |
|
Jan 10 |
asked | SQL Server : Transactional Replication Filter By Computed Column |
|
Sep 4 |
accepted | SQL Server: Log Shipping Read Only |
|
Sep 4 |
comment |
SQL Server: Log Shipping Read Only Thanks for the info. I guess what this boils down to is the fact that log shipping is designed for backup purposes - not reporting. So (although it can be used to reduce the reporting load on the primary database) it is not truly designed for this. One of the big issues we are running into is the fact that the transaction indices and the reporting indices we require are very different and we do not want to add the reporting indices to the primary database (due to size,performance,etc). |
|
Aug 31 |
asked | SQL Server: Log Shipping Read Only |
|
Aug 21 |
awarded | Scholar |
|
Aug 21 |
accepted | SQL Server : Transactional Replication Computed Column |
|
Aug 20 |
awarded | Student |
|
Aug 20 |
asked | SQL Server : Transactional Replication Computed Column |
