Migration to SQL 2005 ... how to setup the new enviroment

Hello,

I have been made the point person for our migration to SQL2005. We are a law firm with approximately 750 users. The first SQL environment we will be upgrading is our document management system (DMS). This is an intensive SQL product. After this migration we will more of to our finical system, records system and then all home grown databases.

What we would like to do is consolidate servers and scale out the new SQL environment to a farm. After some initial research it does not look like we will be able to scale out, since the data in the DMS is always changing.

Does anyone have some advice or guidance on what direction we should be looking? I have done tons a online searches and can find out information on everything to do with SQL, except this.

Thanks in advance,

Jeff Carroll

See this link and watch webcast #4...

http://www.microsoft.com/events/series/technetsqlserver2005.mspx

Migration to MySQL?

From a "price point of view" migrating from the actual platform (2 node
cluster Windows server 2003 with SQL Server 2000 Enterprise Edition)to MySQL
can be very attractive.
In fact our management starts to think that way...
My question is related to the faisability of this operation in a critical
production cluster server.
Is it recommanded?
Pros and Cons?
Why yes and why no.
Please advise.
Franco
It is difficult to answer this type of questions rigorously in a newsgroup
forum. I'd suggest that you invole all the stakeholders and conduct a
comparative risk analysis on the migration. The compartive risk analysis
should cover the key risk factors that are important to your organizaton.
Note that cost factors are but one category among many others.
Some of risk factors to consider include reliability and resilience (e.g.
high availability, stability of the DBMS, proven platform, etc), scalability
and performance (e.g. scalability in terms of database size, # of processors,
memory size, partitioning, index maintenance, etc), manageability (e.g. ease
of backup/restore), operations issus (e.g. need for consistency checks,
availability of expetise, monitoring tools, etc), portfolio impact (e.g. what
is the mix of your installed DBMS and apps using various DBMS, dependencies
among the databases, etc), and supportability (e.g. vendor support, user
community, etc). Obviously, you would have to rate these and other factors
per their relative importance to your apps and organization.
Linchi
"Franco" wrote:

> From a "price point of view" migrating from the actual platform (2 node
> cluster Windows server 2003 with SQL Server 2000 Enterprise Edition)to MySQL
> can be very attractive.
> In fact our management starts to think that way...
> My question is related to the faisability of this operation in a critical
> production cluster server.
> Is it recommanded?
> Pros and Cons?
> Why yes and why no.
> Please advise.
> --
> Franco

Migrating to SQL Server from Versant

Can anyone point me to someone who could advise on migrating databases. I am
a system consultant (but not a database consultant or expert) and one of my
customers wants to convert their database from Versant to SQL server. The
Database is used to record customer information and includes the following
requirements. All data entered or changed must have a change history
recorded. Pictures will be save and linked to customers and the ability to
annotate the pictures is also required. The system will be used in various
locations worldwide.
Any help would be required.
thanks
George
George Adrian
All possible to do in SQL Server. I have no clue what Versant is, I've
never heard of it.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"George Adrian" <GeorgeAdrian@.discussions.microsoft.com> wrote in message
news:32CF3D1B-B261-48AD-A8A4-7CBF2CEEB24F@.microsoft.com...
> Can anyone point me to someone who could advise on migrating databases. I
> am
> a system consultant (but not a database consultant or expert) and one of
> my
> customers wants to convert their database from Versant to SQL server. The
> Database is used to record customer information and includes the following
> requirements. All data entered or changed must have a change history
> recorded. Pictures will be save and linked to customers and the ability to
> annotate the pictures is also required. The system will be used in various
> locations worldwide.
> Any help would be required.
> thanks
> George
> --
> George Adrian
|||The biggest issue is that since Versant is an Object Oriented database, you
will have to redesign the data model - Identity columns to replace
ObjectID's, Foreign Key columns to replace object references, etc. I would
recommend rethinking the data model completely to produce an efficient
relational model rather than trying to map their OO schema directly to a
relational schema.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:OKjSseSDGHA.2040@.TK2MSFTNGP14.phx.gbl...
> All possible to do in SQL Server. I have no clue what Versant is, I've
> never heard of it.
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
> "George Adrian" <GeorgeAdrian@.discussions.microsoft.com> wrote in message
> news:32CF3D1B-B261-48AD-A8A4-7CBF2CEEB24F@.microsoft.com...
>

Migrating to SQL Server from Versant

Can anyone point me to someone who could advise on migrating databases. I am
a system consultant (but not a database consultant or expert) and one of my
customers wants to convert their database from Versant to SQL server. The
Database is used to record customer information and includes the following
requirements. All data entered or changed must have a change history
recorded. Pictures will be save and linked to customers and the ability to
annotate the pictures is also required. The system will be used in various
locations worldwide.
Any help would be required.
thanks
George
--
George AdrianAll possible to do in SQL Server. I have no clue what Versant is, I've
never heard of it.
--
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"George Adrian" <GeorgeAdrian@.discussions.microsoft.com> wrote in message
news:32CF3D1B-B261-48AD-A8A4-7CBF2CEEB24F@.microsoft.com...
> Can anyone point me to someone who could advise on migrating databases. I
> am
> a system consultant (but not a database consultant or expert) and one of
> my
> customers wants to convert their database from Versant to SQL server. The
> Database is used to record customer information and includes the following
> requirements. All data entered or changed must have a change history
> recorded. Pictures will be save and linked to customers and the ability to
> annotate the pictures is also required. The system will be used in various
> locations worldwide.
> Any help would be required.
> thanks
> George
> --
> George Adrian|||The biggest issue is that since Versant is an Object Oriented database, you
will have to redesign the data model - Identity columns to replace
ObjectID's, Foreign Key columns to replace object references, etc. I would
recommend rethinking the data model completely to produce an efficient
relational model rather than trying to map their OO schema directly to a
relational schema.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:OKjSseSDGHA.2040@.TK2MSFTNGP14.phx.gbl...
> All possible to do in SQL Server. I have no clue what Versant is, I've
> never heard of it.
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
> "George Adrian" <GeorgeAdrian@.discussions.microsoft.com> wrote in message
> news:32CF3D1B-B261-48AD-A8A4-7CBF2CEEB24F@.microsoft.com...
>> Can anyone point me to someone who could advise on migrating databases. I
>> am
>> a system consultant (but not a database consultant or expert) and one of
>> my
>> customers wants to convert their database from Versant to SQL server. The
>> Database is used to record customer information and includes the
>> following
>> requirements. All data entered or changed must have a change history
>> recorded. Pictures will be save and linked to customers and the ability
>> to
>> annotate the pictures is also required. The system will be used in
>> various
>> locations worldwide.
>> Any help would be required.
>> thanks
>> George
>> --
>> George Adrian
>

Migrating to SQL Server from Versant

Can anyone point me to someone who could advise on migrating databases. I am
a system consultant (but not a database consultant or expert) and one of my
customers wants to convert their database from Versant to SQL server. The
Database is used to record customer information and includes the following
requirements. All data entered or changed must have a change history
recorded. Pictures will be save and linked to customers and the ability to
annotate the pictures is also required. The system will be used in various
locations worldwide.
Any help would be required.
thanks
George
--
George AdrianAll possible to do in SQL Server. I have no clue what Versant is, I've
never heard of it.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"George Adrian" <GeorgeAdrian@.discussions.microsoft.com> wrote in message
news:32CF3D1B-B261-48AD-A8A4-7CBF2CEEB24F@.microsoft.com...
> Can anyone point me to someone who could advise on migrating databases. I
> am
> a system consultant (but not a database consultant or expert) and one of
> my
> customers wants to convert their database from Versant to SQL server. The
> Database is used to record customer information and includes the following
> requirements. All data entered or changed must have a change history
> recorded. Pictures will be save and linked to customers and the ability to
> annotate the pictures is also required. The system will be used in various
> locations worldwide.
> Any help would be required.
> thanks
> George
> --
> George Adrian|||The biggest issue is that since Versant is an Object Oriented database, you
will have to redesign the data model - Identity columns to replace
ObjectID's, Foreign Key columns to replace object references, etc. I would
recommend rethinking the data model completely to produce an efficient
relational model rather than trying to map their OO schema directly to a
relational schema.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:OKjSseSDGHA.2040@.TK2MSFTNGP14.phx.gbl...
> All possible to do in SQL Server. I have no clue what Versant is, I've
> never heard of it.
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
> "George Adrian" <GeorgeAdrian@.discussions.microsoft.com> wrote in message
> news:32CF3D1B-B261-48AD-A8A4-7CBF2CEEB24F@.microsoft.com...
>