Data Manipulation without Scribe?

I know Scribe is the preferred tool, but in order to help my understanding of
options, and system capabilities, I am wondering:

How would one go about doing complex data manipulation with MSCRM data? i.e.
Mass merging of duplicates, migrating tables including their record
relationships, etc?.

I am not sure if I read this somewhere, but I have gotten the feeling that
it is not supported (or dissasterous) to work with the data from the SQL
backend. Is this so?

If Scribe did not exist, how would we work with the data? Are there other
parts of the system that would need modification, for example.

I have very experience with working with SQL at the moment.

Dave
Mon Oct 16 13:37:21 CDT 2006

Rich,
1) Yes, it is not supported, and very likely disasterous to directly
update any SQL tables in the MSCRM or METABASE databases. (Read is OK.)

2) c360 has a Duplicate Detection product at www.c360.com
3) All Scribe has done is slap a GUI in front of MSCRM API calls. They
used the SDK to call the Update method, e.g., when you select the
Update step in the Scribe GUI.

So, with or without Scribe, the only way to programatically manipulate
objects in MSCRM is through the SDK. HTH,
Dave

Rich wrote:
> I know Scribe is the preferred tool, but in order to help my understanding of
> options, and system capabilities, I am wondering:
>
> How would one go about doing complex data manipulation with MSCRM data? i.e.
> Mass merging of duplicates, migrating tables including their record
> relationships, etc?.
>
> I am not sure if I read this somewhere, but I have gotten the feeling that
> it is not supported (or dissasterous) to work with the data from the SQL
> backend. Is this so?
>
> If Scribe did not exist, how would we work with the data? Are there other
> parts of the system that would need modification, for example.
>
> I have very experience with working with SQL at the moment.