Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jibrish
Starting Member
4 Posts |
 Posted - 2004-04-21 : 10:10:38
|
| Hello!In our database there is more than 3 billion of records and seems growing up each day.We are thinking to transfer the content of this database increasingly one point to another over a secure SSL network to analyze it locally instead of using the on-living one which deals more than three hundreds of clients at the same time.Is there any suggestions or problems that we are going to face it that you have lived before?Thank you |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-04-21 : 12:42:39
|
| How are you going to transfer it? I would recommend using sp_detach_db/sp_attach_db if you can take the database down temporarily or BACKUP/RESTORE method if you can't. How big is the database?Tara |
 |
|
|
jibrish
Starting Member
4 Posts |
Posted - 2004-04-22 : 06:58:21
|
quote:
How are you going to transfer it?
While the first db was serving to my other applications; pre-setted-up job would be executed for transferring the data increasingly as i said before from this server to another server. Network between them is TCP/IP and the distant is maybe over-continent.quote:
I would recommend using sp_detach_db/sp_attach_db if you can take the database down temporarily or BACKUP/RESTORE method if you can't.
There is no possibility to take the database offline. And B/R methods for saving the database file to the permanent-media and restoring upon it. So, I have decided to use Replication facitilies of Sql Server to do it with well-known methods.quote:
How big is the database?
The database files currently occupies ~10GB and this size is growing up as each day passes by the size of ~0.5GB.Thank you. |
|
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2004-04-22 : 07:45:02
|
| jibrish, why do you say you cannot use Backup and restore? Isn't the most convenient way to take a backup onto a DAT or DLT and ship it across to the destination? Of course this works well if you dont want to do it very often. Replication is going to be very slow and will take up quite a bit of server resources.OS |
|
|
|
jibrish
Starting Member
4 Posts |
Posted - 2004-04-22 : 08:26:36
|
quote:
jibrish, why do you say you cannot use Backup and restore
I say this because 'this works well if you dont want to do it very often' is negative for me. A daily job would run to make it and the data in which only had been updated would be translated.Have any other suggestions for the situation?Thank you much |
|
|
|
mohdowais
Sheikh of Yak Knowledge
1456 Posts |
Posted - 2004-04-22 : 10:09:45
|
| I think you are trying to implement a DSS or Reporting server away from your OLTP database. But for your given timeframe, replication seems to be the more logical choice for you. I have an idea for "manual log-shipping" but I dont know how well that would work... maybe one of the more experienced DBAs here can confirm. It goes something like this: you take a backup of your database currently and restore in on the remote location the first time. Then you take periodical transaction log backups of your live database. At the end of the day, you schedule a process to take the day's log backups and copy them over to the DSS server and apply them in the correct order. Then your DSS database should be in sync with your live database upto the last log backup restored. I haven't tried this before... Tara, Derrick, anybody got any comments on this?OS |
|
|
|
|
|
|
Massive data transferring