SEO

#1 (**permalink**) 02-24-2008, 11:57 AM

Hi Everyone,

I'm looking for a database consolidation template plan. Something that
will just speak about the issues, steps, and needs for database
consolidation. Also, if you could identify any potential problems
with consolidating a database.

Thanks,
Dnguy19

#2 (**permalink**) 02-24-2008, 11:58 AM

dnguy19@gmail.com wrote:

> Hi Everyone,
>
> I'm looking for a database consolidation template plan. Something that
> will just speak about the issues, steps, and needs for database
> consolidation. Also, if you could identify any potential problems
> with consolidating a database.
>
> Thanks,
> Dnguy19

For anyone to help you more information is required.

For example ... are you consolidating DB2 into Oracle or Oracle 7.3.4
into 10gR1, or Oracle Financials into a datawarehouse?

Crystal balls and taro card aren't working this week.
--
Daniel A. Morgan
University of Washington
damorgan@x.washington.edu
(replace 'x' with 'u' to respond)

#3 (**permalink**) 02-24-2008, 12:01 PM

Hi Daniel,

I'm looking for something with regards to Cache. It's not a well-known
database. But what I would really like to know is with regards to a
database consolidataion plan, what are some of the issues that could
possible go wrong? (Securityy, stability, data loss, performance, etc).
The plan doesn't have to be specifically for a database product, just
what are the general issues that can be experienced with this type of
project.

Thanks,
Dnguy19

#4 (**permalink**) 02-24-2008, 12:02 PM

dnguy19@gmail.com wrote:

> Hi Daniel,
>
> I'm looking for something with regards to Cache. It's not a well-known
> database. But what I would really like to know is with regards to a
> database consolidataion plan, what are some of the issues that could
> possible go wrong? (Securityy, stability, data loss, performance, etc).
> The plan doesn't have to be specifically for a database product, just
> what are the general issues that can be experienced with this type of
> project.
>
> Thanks,
> Dnguy19
>

Generically:

Duplicating functionality
Migrating business logic
Migrating data
Security
Performance
Stability
Inability of technical staff to code for it (they may get the syntax but
do they understand the architecture and concepts and best practices?)
Inability of technical staff to debug problems
Inability of technical staff to provide tuning
Lack of management support with sufficient training $ before and after
Inability to recover from hardware and other crashes
Inability to restore transactions due to failures
Lack of willingness of current employees to evolve to new technology
Lack of willingness of end users to evolve to new technology

Is that enough to make you want a bottle of scotch of your own?
Mine's taken.
--
Daniel A. Morgan
University of Washington
damorgan@x.washington.edu
(replace 'x' with 'u' to respond)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Database Consolidation