 | |
Replication/archiving of database content to archive db instance?
comp.databases.sybase comp.databases.sybase
 |
| | Thread Tools | Display Modes |
#11
 
| |||
| |||
|
Re: Replication/archiving of database content to archive db instance? -
10-23-2008
, 10:24 PM
|
Dear subscribers I’m looking for a solution to archive the content of some tables in a product that uses Sybase as the database engine. The problem is that some of the table contain records in such large numbers that it affects the performance of the application thus we like to move content older than e.g. a year to an archive instance of the database on a regular basis. This archive instance will basically have the same table setup as the original version but will contain the old data. We have looked at Sybase’s Replication Server but I like to see if there are any other options available. My biggest worry is fault tolerance i.e. if anything goes wrong we mustn’t loose any data, i.e. that a row is deleted from the main database without being written properly to the archive database. If Sybase supports cross-database transactions maybe this task can be solved with a simple scheduled script? Any suggestions are most welcome. |
purpose. You can create an archival database, write stored procs /
scripts to archive the data periodically. Write scripts to retrieve
data. Archive periodically and retrieve whenever needed
-HTH
Manish Negandhi
[TeamSybase]
#12
| |||
| |||
|
|
Dear subscribers I’m looking for a solution to archive the content of some tables in a product that uses Sybase as the database engine. The problem is that some of the table contain records in such large numbers that it affects the performance of the application thus we like to move content older than e.g. a year to an archive instance of the database on a regular basis. This archive instance will basically have the same table setup as the original version but will contain the old data. We have looked at Sybase’s Replication Server but I like to see if there are any other options available. My biggest worry is fault tolerance i.e. if anything goes wrong we mustn’t loose any data, i.e. that a row is deleted from the main database without being written properly to the archive database. If Sybase supports cross-database transactions maybe this task can be solved with a simple scheduled script? Any suggestions are most welcome. |
purpose. You can create an archival database, write stored procs /
scripts to archive the data periodically. Write scripts to retrieve
data. Archive periodically and retrieve whenever needed
-HTH
Manish Negandhi
[TeamSybase]
#13
| |||
| |||
|
|
Dear subscribers I’m looking for a solution to archive the content of some tables in a product that uses Sybase as the database engine. The problem is that some of the table contain records in such large numbers that it affects the performance of the application thus we like to move content older than e.g. a year to an archive instance of the database on a regular basis. This archive instance will basically have the same table setup as the original version but will contain the old data. We have looked at Sybase’s Replication Server but I like to see if there are any other options available. My biggest worry is fault tolerance i.e. if anything goes wrong we mustn’t loose any data, i.e. that a row is deleted from the main database without being written properly to the archive database. If Sybase supports cross-database transactions maybe this task can be solved with a simple scheduled script? Any suggestions are most welcome. |
purpose. You can create an archival database, write stored procs /
scripts to archive the data periodically. Write scripts to retrieve
data. Archive periodically and retrieve whenever needed
-HTH
Manish Negandhi
[TeamSybase]
#14
| |||
| |||
|
|
Dear subscribers I’m looking for a solution to archive the content of some tables in a product that uses Sybase as the database engine. The problem is that some of the table contain records in such large numbers that it affects the performance of the application thus we like to move content older than e.g. a year to an archive instance of the database on a regular basis. This archive instance will basically have the same table setup as the original version but will contain the old data. We have looked at Sybase’s Replication Server but I like to see if there are any other options available. My biggest worry is fault tolerance i.e. if anything goes wrong we mustn’t loose any data, i.e. that a row is deleted from the main database without being written properly to the archive database. If Sybase supports cross-database transactions maybe this task can be solved with a simple scheduled script? Any suggestions are most welcome. |
purpose. You can create an archival database, write stored procs /
scripts to archive the data periodically. Write scripts to retrieve
data. Archive periodically and retrieve whenever needed
-HTH
Manish Negandhi
[TeamSybase]
#15
| |||
| |||
|
|
Dear subscribers I’m looking for a solution to archive the content of some tables in a product that uses Sybase as the database engine. The problem is that some of the table contain records in such large numbers that it affects the performance of the application thus we like to move content older than e.g. a year to an archive instance of the database on a regular basis. This archive instance will basically have the same table setup as the original version but will contain the old data. We have looked at Sybase’s Replication Server but I like to see if there are any other options available. My biggest worry is fault tolerance i.e. if anything goes wrong we mustn’t loose any data, i.e. that a row is deleted from the main database without being written properly to the archive database. If Sybase supports cross-database transactions maybe this task can be solved with a simple scheduled script? Any suggestions are most welcome. |
purpose. You can create an archival database, write stored procs /
scripts to archive the data periodically. Write scripts to retrieve
data. Archive periodically and retrieve whenever needed
-HTH
Manish Negandhi
[TeamSybase]
#16
| |||
| |||
|
|
Dear subscribers I’m looking for a solution to archive the content of some tables in a product that uses Sybase as the database engine. The problem is that some of the table contain records in such large numbers that it affects the performance of the application thus we like to move content older than e.g. a year to an archive instance of the database on a regular basis. This archive instance will basically have the same table setup as the original version but will contain the old data. We have looked at Sybase’s Replication Server but I like to see if there are any other options available. My biggest worry is fault tolerance i.e. if anything goes wrong we mustn’t loose any data, i.e. that a row is deleted from the main database without being written properly to the archive database. If Sybase supports cross-database transactions maybe this task can be solved with a simple scheduled script? Any suggestions are most welcome. |
purpose. You can create an archival database, write stored procs /
scripts to archive the data periodically. Write scripts to retrieve
data. Archive periodically and retrieve whenever needed
-HTH
Manish Negandhi
[TeamSybase]
#17
| |||
| |||
|
|
Dear subscribers I’m looking for a solution to archive the content of some tables in a product that uses Sybase as the database engine. The problem is that some of the table contain records in such large numbers that it affects the performance of the application thus we like to move content older than e.g. a year to an archive instance of the database on a regular basis. This archive instance will basically have the same table setup as the original version but will contain the old data. We have looked at Sybase’s Replication Server but I like to see if there are any other options available. My biggest worry is fault tolerance i.e. if anything goes wrong we mustn’t loose any data, i.e. that a row is deleted from the main database without being written properly to the archive database. If Sybase supports cross-database transactions maybe this task can be solved with a simple scheduled script? Any suggestions are most welcome. |
purpose. You can create an archival database, write stored procs /
scripts to archive the data periodically. Write scripts to retrieve
data. Archive periodically and retrieve whenever needed
-HTH
Manish Negandhi
[TeamSybase]
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.