Re: Migrate existing standalone to cluster

To create a database with a case-sensitive collation, just use the COLLATE
option:

create database MyDB
collate Latin1_General_CS_AI

As for the other bit, you'll have to create the new virtual server (and
named instance) in the same manner as you created the other virtual server
and instance. However, you can specify the collation for the new instance
at that time. Once that's done, then backup and restore the DB's from the
standalone to the new instance. Finally, remove the standalone.


--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Cary" <Cary@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FBFC5A77-4A41-4B6E-B076-370E9111321B@xxxxxxxxxxxxxxxx
Not that it will matter much anyway, since it is already installed, but how
do you go about making a case-sensitive db inside of an insensitive
instance?

And I still need to know how to change the standalone to a clustered... :)

"Tom Moreau" wrote:

> That's not justification enough. You can create a case-sensitive database
> within an instance that is not case sensitive.
>
> --
> Tom
>
> ----------------------------------------------------
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> ..
> "Cary" <Cary@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A8F1525E-3D96-4842-AFBD-87160EC34CB8@xxxxxxxxxxxxxxxx
> Oh you'll love this....
>
> The software we purchased for our new document management system *cough*
> Documentum *cough*, is designed so as to require a case-sensitive
> database.
> I know....D-U-M Dum...And because all of our other databases are NOT
> case-sensitive (and there's no way in h*ll I would change that) we had to
> create a new instance that was.
>
> "Tom Moreau" wrote:
>
> > Is it possible to go with the existing clustered instance and simply
> > move
> > the DB's to the cluster? What's driving the need for two instances?
> >
> > --
> > Tom
> >
> > ----------------------------------------------------
> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> > SQL Server MVP
> > Columnist, SQL Server Professional
> > Toronto, ON Canada
> > www.pinpub.com
> > ..
> > "Cary" <Cary@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:F9743B37-FC4D-4909-A4CA-608078BB5A3E@xxxxxxxxxxxxxxxx
> > While away on vacation my company had some software installed that
> > required
> > a
> > new instance of SQL Server 2K to be created on our existing
> > active/passive
> > cluster.
> > Because the techs doing the install did not know the password for our
> > domain
> > cluster user account they created the standalone instance on the db
> > server.
> > What I need to know is how do I go about migrating it to a clustered
> > instance
> > instead of a standalone so as to take advantage of the failover
> > capabilities?
> >
> > i.e. I already have a clustered server with one clustered instance.
> > They
> > installed a standalone instance alongside and now I need to migrate the
> > new
> > instance to another named clustered instance.
> >
> >
>
>

.

Relevant Pages

  • Re: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Cluster will not fail over.
    ... As far as the TCP/IP issue goes, you had to rebuild the cluster and were not ... able to restore the master database. ... the entire installation configuration just as if nothing was running on it. ... > This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Cluster will not fail over.
    ... This worked bringing up the sql server in minimal mode. ... > Start SQL Server in single user mode with trace flag -T3608. ... > SQL from recovering anything except the master database. ... > You didn't mention whether you blew the cluster away or not or just ...
    (microsoft.public.sqlserver.clustering)
  • Re: Cluster will not fail over.
    ... I honestly did not have time to investigate as to why the cluster would not ... SQL Server would immediately turn off. ... >> SQL from recovering anything except the master database. ... use files copied from another installation at the exact ...
    (microsoft.public.sqlserver.clustering)
  • SQL Replication How To
    ... I currently have a two SQL Servers in a Windows 2003 Cluster with the ... I have another SQL Server (Standalone) in a remote location that is ... What is the best way to replicate the data from the cluster to the ...
    (microsoft.public.sqlserver.replication)