Mirror Server

i am looking at options for a 'hot spare' server for my SQL application
the ideal senario would be that the 2nd server would 'take over' under a
controlled manner as the same server etc
anybody using any third party solutions that can handle this?
Many thanks
Jez
jez_UK,
Do you want to protect your disks as well as the server hardware? Have a
look at clustering. How far apart physically are your servers? Also look
out for database mirroring in SQL Server 2005 next year - this has an
automatic three second failover time.
When you say "controlled manner" do you mean manually? How much data
loss can you tolerate? You might also want to consider log shipping and
possibly a third party replication tool like Double-Take from NSI software.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
jez_UK wrote:
> i am looking at options for a 'hot spare' server for my SQL application
> the ideal senario would be that the 2nd server would 'take over' under a
> controlled manner as the same server etc
> anybody using any third party solutions that can handle this?
>

Mirror Server

i am looking at options for a 'hot spare' server for my SQL application
the ideal senario would be that the 2nd server would 'take over' under a
controlled manner as the same server etc
anybody using any third party solutions that can handle this?
--
Many thanks
Jezjez_UK,
Do you want to protect your disks as well as the server hardware? Have a
look at clustering. How far apart physically are your servers? Also look
out for database mirroring in SQL Server 2005 next year - this has an
automatic three second failover time.
When you say "controlled manner" do you mean manually? How much data
loss can you tolerate? You might also want to consider log shipping and
possibly a third party replication tool like Double-Take from NSI software.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
jez_UK wrote:
> i am looking at options for a 'hot spare' server for my SQL application
> the ideal senario would be that the 2nd server would 'take over' under a
> controlled manner as the same server etc
> anybody using any third party solutions that can handle this?
>

Mirror Server

i am looking at options for a 'hot spare' server for my SQL application
the ideal senario would be that the 2nd server would 'take over' under a
controlled manner as the same server etc
anybody using any third party solutions that can handle this?
Many thanks
Jezjez_UK,
Do you want to protect your disks as well as the server hardware? Have a
look at clustering. How far apart physically are your servers? Also look
out for database mirroring in SQL Server 2005 next year - this has an
automatic three second failover time.
When you say "controlled manner" do you mean manually? How much data
loss can you tolerate? You might also want to consider log shipping and
possibly a third party replication tool like Double-Take from NSI software.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
jez_UK wrote:
> i am looking at options for a 'hot spare' server for my SQL application
> the ideal senario would be that the 2nd server would 'take over' under a
> controlled manner as the same server etc
> anybody using any third party solutions that can handle this?
>

Migrating to Sql25k

We’ve got hundreds of branch which are working with MSDE. As we are moving sql25k, what the ideal version would be adviceable to install there? Sql Express?

How to handle this? I have a fuss on my head because of there are many vesions available.

Thanks in advance for any comment or further information,

Yes, SQLExpress is the succesor to MSDE however "Express" is a much better core database engine as it support more hardware, less restrictions (including the fabled 5 connection limit of MSDE) etc.

Here is a link that lists out the differences between versions:

http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

And as far as the actual upgrade process you could perform either direct "inplace" upgrades or using named instances perform a slower migration. Either way backup everything!

Derek

|||Thank you|||

enric, could you please mark an answer. And your welcome.

thanks,

Derek