Home Truths

[suityou01]

Bollocks

I would work with EO, and possibly Doodab, and the remote possibly of eek. The rest of you are car crashes waiting to happen in data migration terms.

Very seriously, unless you have been on a migration project against a deadline, and then had to pull it out of the tulipe you cannot comment.

It IS that hard. No other branch of IT will you be soooo involved with end users, soooo dependant on end users, so exposed for not having clearly defined requirements, so much in the firing line for the system not going live (as the code is written and tested, they're just waiting on the data .....)

Troll all you want (and I'm sure you will). A select few showed their scars in this thread, good men all of them and I salute them.

The rest have not done a big **** off, arsehole ******, big bag of shoite, utter back breaking, total runaround, nest of vipers, think you're nearly done but in actual fact you've got nowhere, bag of wank, cluster**** data migration before.

[Platypus]

The rest have not done a big **** off, arsehole ******, big bag of shoite, utter back breaking, total runaround, nest of vipers, think you're nearly done but in actual fact you've got nowhere, bag of wank, cluster**** data migration before.

Sheesh calm down

[suityou01]

Sheesh calm down

That bad?

[MarillionFan]

Sheesh calm down

I actually agree with Aussielong. Data migration while time consuming and a main in the backside is not really that complex IMHO unless the people doing it have no fricking concept of the data or business. Like Bob.

[suityou01]

I actually agree with Aussielong. Data migration while time consuming and a main in the backside is not really that complex IMHO unless the people doing it have no fricking concept of the data or business. Like Bob.

Well now. Says the idiot who can't hire contractors that he needs then runs for the hills blaming then when they don't deliver what he needs, clearly when failing to

a) Identify the staff he needs
b) Identify the deliverables

You are already exposed on here as a joke since your recent foray into management so you opinion counts for **** all.

Truly HTH BISDI.

[MarillionFan]

Well now. Says the idiot who can't hire contractors that he needs then runs for the hills blaming then when they don't deliver what he needs, clearly when failing to

a) Identify the staff he needs
b) Identify the deliverables

You are already exposed on here as a joke since your recent foray into management so you opinion counts for **** all.

Truly HTH BISDI.

B) before A) except after Zzzzzzz.

[suityou01]

B) before A) except after Zzzzzzz.

Get some sleep. You'll probably need it after all the jet lag. Then once you are rested, come on here an construct an argument worth arguing with.

I'm supposed to be the bedwetter on here, right? ******* pathetic that it's so ******* easy to paste your ass all over these boards these days.

You seriously disgust me, you utter loser.

Now **** off and get some sleep you arsewipe.

[aussielong]

I would work with EO, and possibly Doodab, and the remote possibly of eek. The rest of you are car crashes waiting to happen in data migration terms.

Very seriously, unless you have been on a migration project against a deadline, and then had to pull it out of the tulipe you cannot comment.

It IS that hard. No other branch of IT will you be soooo involved with end users, soooo dependant on end users, so exposed for not having clearly defined requirements, so much in the firing line for the system not going live (as the code is written and tested, they're just waiting on the data .....)

Troll all you want (and I'm sure you will). A select few showed their scars in this thread, good men all of them and I salute them.

The rest have not done a big **** off, arsehole ******, big bag of shoite, utter back breaking, total runaround, nest of vipers, think you're nearly done but in actual fact you've got nowhere, bag of wank, cluster**** data migration before.

You make the business own the reconciliations. They sign off on the migrations. You have multiple dry runs. By the time you run the real migration it's a point, click and kickback n relax exercise. You seem to get wound up fairly quickly, come on, it's only data migration!- when your scripts fail just make sure you have enough pairs of hands to key it all into the target system and four eye check it.

[mudskipper]

Get some sleep. You'll probably need it after all the jet lag. Then once you are rested, come on here an construct an argument worth arguing with.

I'm supposed to be the bedwetter on here, right? ******* pathetic that it's so ******* easy to paste your ass all over these boards these days.

You seriously disgust me, you utter loser.

Now **** off and get some sleep you arsewipe.

Suity's been on the vitamins.

The reason data migration is hard is that the source data is usually crap - addresses in random free text formats, phone numbers in any format you can imagine, dates in text fields, missing data, orphaned data etc. If the data was all nice, clean and well-defined, migration of said data would be a doddle.

[aussielong]

Suity's been on the vitamins.

The reason data migration is hard is that the source data is usually crap - addresses in random free text formats, phone numbers in any format you can imagine, dates in text fields, missing data, orphaned data etc. If the data was all nice, clean and well-defined, migration of said data would be a doddle.

You should never try and clean up the data as part of the migration. Trap for new players. I'll leave you to draw your own conclusions. But you have only two real choices.