SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Vs Oracle


SQL Server Vs Oracle

Author
Message
Venkatesan Prabu
Venkatesan Prabu
SSC-Addicted
SSC-Addicted (496 reputation)SSC-Addicted (496 reputation)SSC-Addicted (496 reputation)SSC-Addicted (496 reputation)SSC-Addicted (496 reputation)SSC-Addicted (496 reputation)SSC-Addicted (496 reputation)SSC-Addicted (496 reputation)

Group: General Forum Members
Points: 496 Visits: 205
Team,



Considering am having some data in DB2 and I need to migrate those data into the new system.



Am having around 30 million records with archive 30 million records... so totally 60 million records needs to be stored in my database.



We are expecting 10 million new records... Whether SQL Server is apt for this scenario... Or Oracle can be used for this scenario... Need justification for the same.



I am very much concern with the performance of my database too :-) ...............................



If SQL Server is good which version of SQL Server is best...2005 or 2008.... Need justification for the same.



Please help me..



Regards,

Venkatesan Prabu .J

http://venkattechnicalblog.blogspot.com/

Thanks and Regards,
Venkatesan Prabu, Tongue
My Blog:

http://venkattechnicalblog.blogspot.com/
GilaMonster
GilaMonster
SSC Guru
SSC Guru (227K reputation)SSC Guru (227K reputation)SSC Guru (227K reputation)SSC Guru (227K reputation)SSC Guru (227K reputation)SSC Guru (227K reputation)SSC Guru (227K reputation)SSC Guru (227K reputation)

Group: General Forum Members
Points: 227185 Visits: 46335
60 million rows is not beyond SQL's capabilities. I've had more than that in a single table. The design needs to be done carefully, but it is possible.

Are you expecting 10 million more rows per hour, per day, per month?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


EdVassie
EdVassie
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14186 Visits: 3901
My advise is to use whatever your organisation has the most skills in.

The first preference is to leave it in DB2, as moving it means you are paying money to stand still. If you absolutely have to move it, what other skills does your organisation have. If you are mainly a MySQL installation, put it into MySQL. If you are mainly a SQL Server installation, put it into SQL Server. Likewise for Oracle, Sybase, etc. Any enterprise-quality database that your organisation is skilled in will do the job. It is more important to leverage existing skills than introduce a new product.

Do not be tempted to put the data into departmental-class database systems such as Access, unless you do not mind loosing some of the data.

If you do decide on SQL Server, then use SQL Server 2008. Even though it has only recently been released it has many improvements over SQL Server 2005, and any serious bugs will have been fixed before you have completed your migration to it.

Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 14 Mar 2017: now over 40,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Quote: When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist. - Archbishop Hélder Câmara
davidr-632841
davidr-632841
Grasshopper
Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)

Group: General Forum Members
Points: 19 Visits: 143
Be sure to check licensing costs, too. Many org's find Oracle's license structure prohibitive.
David Benoit
David Benoit
SSCrazy Eights
SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)

Group: General Forum Members
Points: 8084 Visits: 3650
Agreed with all the comments. SQL Server 2005 / 2008 are both very capable of handling that and more, the question really has to be "what do you have skills in supporting?" because ultimately there are areas which need more attention when we start looking at larger data sets. So, assess your company profile, technology direction and then make your decision.

If you don't have any deep skills in any of the major DB platforms then SQL Server will offer the easiest learning curve for the most part and will offer the lowest managability price point (an often neglected consideration).

David

@SQLTentmaker

“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search