Install New Instance/ Store Data & Log Files in existing drive

Hello,
I need to install a new instance of SQL Server 2000 on a cluster.
Currently, we have three instances. Each instances stores program files on
the E:\ Drive. Each instance has its own drive for data and another for
logs. However, there is no more unallocated space on the array to create
another partitioned drive.
My question is: If I create the new instance, can I store the data and log
files on an existing drive? Are there any performance or overhead costs that
should be considered?
Thank you,
Caroline
Each instance must have separate disk resources from any other instances.
You will need new disks to create another instance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Caroline" <Caroline@.community.nospam> wrote in message
news:4E870F35-33B9-4E92-91E6-1993FD8FE4C4@.microsoft.com...
> Hello,
> I need to install a new instance of SQL Server 2000 on a cluster.
> Currently, we have three instances. Each instances stores program files
> on
> the E:\ Drive. Each instance has its own drive for data and another for
> logs. However, there is no more unallocated space on the array to create
> another partitioned drive.
> My question is: If I create the new instance, can I store the data and
> log
> files on an existing drive? Are there any performance or overhead costs
> that
> should be considered?
> Thank you,
> Caroline
sql

Inserting Unicode data

Hi.

We have a sql server db that we need to store Unicode text in. The fields are of the type nvarchar, ntext and nchar. Our solution uses both Oracle and SqlServer as a backing database. In Oracle there is a connection string switch "Unicode=True" that fixes the problem. Is there something similar in SqlServer? Since the db layer is generic we'ed like to avoid using a N' prefix on text strings in query statements.

Hi Kim,

As far as I can see, when the fields types are set to such as NVarChar and the update parameters have been set to the corresponding type, the data will be updated as Unicode in SQL Server. When updating the database, the N' prefix will be added automatically by ADO.NET.

That means you don't need to add anything additional to achieve this.

Are you getting some problem when updating the data in the way I mentioned? If so, please let me know the problem. Thanks!

|||

Hi Kevin,

Thank you for the response. The problem is that this is a system that's gone into production. The code is not written by me and I'm sorry to say it doesn't use command parameters for transfering variables. I guess the fix will have to wait until the next upgrade.