August 29, 2005 at 2:59 pm
Hi,
We have very large database (~ 1 terrabyte) currently running in sybase. We are planning to start using SQL Server 2005. The database is a 24/7 production databse and we cannot stop the database, we need to come up with some design stragies to somehow port these database to SQL Server with all its data without affecting the production environment.
We do have a lot of large tables in the range of ~50 m records. Lots of table with blob data.
We are currently trying to come up with some design, we think people out there has done these kind of database port. Unfortunately we cannot find lots of reading material out in the internet. There are some but there are very generic. We are trying to get as much information as possible and if you guys can shed some light in these problem it will be greatly appreciated.
I am not sure whether these is the correct forum for this kind of topic or not. Please let me know if its not then I can post it in some other forum.
Thanks,
Sourav
August 29, 2005 at 5:47 pm
Ha that's a great malaprop you mean 'shed some light' not 'shade some light'.
I just typed about three paragraphs of potential solutions and hit 'Preview' and poof!! all my text was gone. I hate that.
We have done this several times ... let me think about this, talk w/my co-workers and I'll post again tomorrow.
There are some very knowledgable professionals in this forum who will help I'm sure.
Are you familiar with dynamic data warehouse loading techniques like automated ETL ?
Do you have a ErWin or .csv or text file of you schema with all the pri/foreign/keys and constraints ?
August 29, 2005 at 5:58 pm
Yes we do have a text file that has the Database schema with all the pri/foreign keys and other contrainsts.
I heard about automated ETL but never worked on any product that uses ETL technology.
Thanks,
Sourav.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply