Migrating from Oracle to MS SQL

Albert_Roodt_(x-comparexadmin_-_(deleted))

Has anybody done this before?We're looking at migrating an Oracle Instance with External Storage to MicroSoft SQL.Rgds,Albertalbertr@comparexafrica.co.za

Find more posts tagged with

Comments

John_Shoun

It is possible to migrate from Oracle to SQL Server. Support has published a paper (attached) that describes the process. SQL Server has some tools that will import directly from the Oracle database.However, the performance using SQL server was very poor. We not not able to do any tuning to get reasonable performance from the SQL server database. Fortunately we only did this for testing and not for a production site.I would avoid it if at all possible.

Eric_Slaghuis_(sasoladmin_-_(deleted))

We went through a migration from Oracle on SUN to MS SQL 2000 and I can say my performance is beautiful. Using the Livelink performance analyzer (which by the way I can really recommend) our SQL time has improved 300% on some transactions. I must say I am very pleased. The only draw back is the way Microsoft does page locking instead of record level locking, which allows a single user to influence other users by doing irresponsible things. We have a ticket open on this one, maybe we get an answer for this.

volvostephen

We have been running SQL Server all along and we for sure have experienced what you are mentioning about irresponsible activities. Mass delete is very bad, mass move is bad and mass copy is not good. To address the mass deletion problem, I wrote a very simple module that limits deletions to a configurable number. Also, it can prevent deletion if a folder contains objects of subtype 'x'. The way we have it setup is, you cannot delete a folder if it contains a sub folder and you cannot delete a folder if it contains 40 or more items. This module has worked extremely well for us and has mitigated the SQL locking issue. Also - to throw in, I understand that they are working on fixing this issue in a future release. I believe they are breaking up these transactions to smaller chuncks so they will have less of an impact.If you are interested in reviewing the module I have written, let me know. It isn't well documented but it only overrides one method.Stephen

Eric_Slaghuis_(sasoladmin_-_(deleted))

Does this module limit the users if they use Livelink Explorer Professional 4.3.4 as well?If so, I would love to evaluate it. I need to do whatever I can to reduce the numer of locks in our system

x-unileveruser11_-_(deleted)

Stephen,I would also be interested in taking a look at this module.

volvostephen

I wrote the code to work through both LAPI and the web interface so I am assuming it will work with Explorer as well.

volvostephen

This isn't really worthy of being called a module - it is one oscript that has been overridden (The NodeDeleteSubclassPre function for Folders).To make this work, you need these opentext.ini settings:[DeleteSettings]PreventDeleteCount=40PreventDeleteSubtypes={0}The Count variable (40) can be set to any number - if it is deleted, it is unlimited. The Subtypes variable is a list of subtypes that when present in a folder - you would want to prevent a deletion. Candidates for this would be discussions, projects, task lists etc. It is just a comma separated list. If it is removed, there are no restrictions.The code is quite straight forward. It was written to be as performant as possible so I didn't bother enumerating a folder and all its children and its childrens children etc. I just take information that its available for the folder being deleted and evaluate that. If there is a sub folder, I prevent deletion because I don't know how many items it could have had. Of course, I could have gotten that information but if it is a top level folder, how deep would you want to go... I guess I could have set a limit and then evaluate the childcount and increment from there enumerating the folders until I hit the configured limit. So - in retrospect today, that would have been a better way to go but I am reluctant to change this now.Bottom line - this was a life saver for us. Users would do mass deletions (often by accident) and this is no longer an issue (and thnak **** we don't have to do the mass restores). We also had problems with mass copies and then the users would go back to delete one of the copies which would bring the system doen. For the copy issue - Authorlink from Formark was facilitationg the easy accidental copy and we configured that differently to mitigate that.If you have any questions - feel free to email me or post them here.A final note: System Administrators can still perform deletions as per usual. I thought it was imperative to put that in because I didn't want to have this rule apply to me. This way I can do mass deletes at off peak hours and not have to worry.________________________________________Stephen FisherKnowledge Management Systems SpecialistAstraZeneca Canada Inc.1004 Middlegate RoadMississauga, OntarioL4Y 1M4Phone- (905) 896-6658Fax-(905) 615-6830E-mail stephen.fisher@astrazeneca.com________________________________________