Showing posts with label drive. Show all posts
Showing posts with label drive. Show all posts

Tuesday, March 27, 2012

Cluster Server installation other than default directory

Is anyone aware of any issues that can arise from installing MS SQL Server
2000 on the root of a drive - x:\\MSSQL\Data - instead of using the using
the default structure - x:\Program Files\Microsoft SQL Server\MSSQL\Data?
I have always installed to the root directory be it stand-alone or clustered
installs without any issues but I need to know whether there might be
issues especially regarding virtual sql servers installs.
Thanks
I have not seen any differences with clustering, you should be fine with any
path, as long as all possible owners have the same paths.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Gboyega Adepegba" <muyid@.hotmail.com> wrote in message
news:u5IVSaOZEHA.3752@.TK2MSFTNGP12.phx.gbl...
> Is anyone aware of any issues that can arise from installing MS SQL Server
> 2000 on the root of a drive - x:\\MSSQL\Data - instead of using the using
> the default structure - x:\Program Files\Microsoft SQL Server\MSSQL\Data?
> I have always installed to the root directory be it stand-alone or
clustered
> installs without any issues but I need to know whether there might be
> issues especially regarding virtual sql servers installs.
> Thanks
>
|||No issues. I have installed clustered instances of SQL Server 2000 on non-default locations without any problems.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way
to do this is to visit the following websites: http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
sqlsql

Cluster quirum drive size

I need a sql failover cluster box with 10 instances, how big the quorum
drive size that I need --estimate
Thanks
Your Quorum drive does not need much space
minimum 500MB, 1GB will work fine
Rgds,
Edwin.
"mecn" <mecn2002@.yahoo.com> wrote in message
news:e$wj5JvaHHA.1240@.TK2MSFTNGP04.phx.gbl...
> I need a sql failover cluster box with 10 instances, how big the quorum
> drive size that I need --estimate
> Thanks
>
|||Our quorum drives are sized to 640MB.
Linchi
"mecn" wrote:

> I need a sql failover cluster box with 10 instances, how big the quorum
> drive size that I need --estimate
> Thanks
>
>
sqlsql

Monday, March 19, 2012

cluster ? on muliple data disks

Hi,
I have setup a 2 node a/p cluster. During install i picked the s drive as
the data drive, and the L drive as the log drive.
i was able to create a db on the S drive
now i want to create a database and use the z drive. but it won't show me
the Z drive as a option when i try to browse to a different drive as part of
the create new db steps.
both disks are disk resources managed by the cluster
in the past, i have been able to do it on a non clustered server
what is the trick with a cluster?
The "trick" is twofold. First, you have to make the disks Cluster Resources
and put them in the resource group for the SQL virtual server. I am
guessing this is where you are at. Second, you have to make the SQL Service
dependent on the disk resource. You will have to take the service offline
to make the change. Look at the dependency relationship between the SQL
service and the existing disk resources.
Geoff N. Hiten
Microsoft SQL Server MVP
"jason" <jason@.discussions.microsoft.com> wrote in message
news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
> Hi,
> I have setup a 2 node a/p cluster. During install i picked the s drive as
> the data drive, and the L drive as the log drive.
> i was able to create a db on the S drive
> now i want to create a database and use the z drive. but it won't show me
> the Z drive as a option when i try to browse to a different drive as part
> of
> the create new db steps.
> both disks are disk resources managed by the cluster
> in the past, i have been able to do it on a non clustered server
> what is the trick with a cluster?
|||Geoff, that did it thanks!
"Geoff N. Hiten" wrote:

> The "trick" is twofold. First, you have to make the disks Cluster Resources
> and put them in the resource group for the SQL virtual server. I am
> guessing this is where you are at. Second, you have to make the SQL Service
> dependent on the disk resource. You will have to take the service offline
> to make the change. Look at the dependency relationship between the SQL
> service and the existing disk resources.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "jason" <jason@.discussions.microsoft.com> wrote in message
> news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
>
>

cluster ? on muliple data disks

Hi,
I have setup a 2 node a/p cluster. During install i picked the s drive as
the data drive, and the L drive as the log drive.
i was able to create a db on the S drive
now i want to create a database and use the z drive. but it won't show me
the Z drive as a option when i try to browse to a different drive as part of
the create new db steps.
both disks are disk resources managed by the cluster
in the past, i have been able to do it on a non clustered server
what is the trick with a cluster?The "trick" is twofold. First, you have to make the disks Cluster Resources
and put them in the resource group for the SQL virtual server. I am
guessing this is where you are at. Second, you have to make the SQL Service
dependent on the disk resource. You will have to take the service offline
to make the change. Look at the dependency relationship between the SQL
service and the existing disk resources.
Geoff N. Hiten
Microsoft SQL Server MVP
"jason" <jason@.discussions.microsoft.com> wrote in message
news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
> Hi,
> I have setup a 2 node a/p cluster. During install i picked the s drive as
> the data drive, and the L drive as the log drive.
> i was able to create a db on the S drive
> now i want to create a database and use the z drive. but it won't show me
> the Z drive as a option when i try to browse to a different drive as part
> of
> the create new db steps.
> both disks are disk resources managed by the cluster
> in the past, i have been able to do it on a non clustered server
> what is the trick with a cluster?|||Geoff, that did it thanks!
"Geoff N. Hiten" wrote:
> The "trick" is twofold. First, you have to make the disks Cluster Resources
> and put them in the resource group for the SQL virtual server. I am
> guessing this is where you are at. Second, you have to make the SQL Service
> dependent on the disk resource. You will have to take the service offline
> to make the change. Look at the dependency relationship between the SQL
> service and the existing disk resources.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "jason" <jason@.discussions.microsoft.com> wrote in message
> news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
> > Hi,
> > I have setup a 2 node a/p cluster. During install i picked the s drive as
> > the data drive, and the L drive as the log drive.
> > i was able to create a db on the S drive
> > now i want to create a database and use the z drive. but it won't show me
> > the Z drive as a option when i try to browse to a different drive as part
> > of
> > the create new db steps.
> >
> > both disks are disk resources managed by the cluster
> >
> > in the past, i have been able to do it on a non clustered server
> >
> > what is the trick with a cluster?
>
>

cluster ? on muliple data disks

Hi,
I have setup a 2 node a/p cluster. During install i picked the s drive as
the data drive, and the L drive as the log drive.
i was able to create a db on the S drive
now i want to create a database and use the z drive. but it won't show me
the Z drive as a option when i try to browse to a different drive as part of
the create new db steps.
both disks are disk resources managed by the cluster
in the past, i have been able to do it on a non clustered server
what is the trick with a cluster?The "trick" is twofold. First, you have to make the disks Cluster Resources
and put them in the resource group for the SQL virtual server. I am
guessing this is where you are at. Second, you have to make the SQL Service
dependent on the disk resource. You will have to take the service offline
to make the change. Look at the dependency relationship between the SQL
service and the existing disk resources.
Geoff N. Hiten
Microsoft SQL Server MVP
"jason" <jason@.discussions.microsoft.com> wrote in message
news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
> Hi,
> I have setup a 2 node a/p cluster. During install i picked the s drive as
> the data drive, and the L drive as the log drive.
> i was able to create a db on the S drive
> now i want to create a database and use the z drive. but it won't show me
> the Z drive as a option when i try to browse to a different drive as part
> of
> the create new db steps.
> both disks are disk resources managed by the cluster
> in the past, i have been able to do it on a non clustered server
> what is the trick with a cluster?|||Geoff, that did it thanks!
"Geoff N. Hiten" wrote:

> The "trick" is twofold. First, you have to make the disks Cluster Resourc
es
> and put them in the resource group for the SQL virtual server. I am
> guessing this is where you are at. Second, you have to make the SQL Servi
ce
> dependent on the disk resource. You will have to take the service offline
> to make the change. Look at the dependency relationship between the SQL
> service and the existing disk resources.
> Geoff N. Hiten
> Microsoft SQL Server MVP
> "jason" <jason@.discussions.microsoft.com> wrote in message
> news:FA7F35A5-7EDE-4162-90CE-E6AAD7D43057@.microsoft.com...
>
>

Saturday, February 25, 2012

Cloned Drive

I have a machine named DOG with MSDE (computername=DOG). I clone the machine
to another and rename the machine CAT. When I do this, SQL Server reports
"Your SQL Server installation is either corrupt or has been tampered with
(unknown package id). Please rerun setup." I understand why this happens,
the computername changed.
Is there a way to change the package id to work with the new computername?
Of course I can reinstall MSDE, but that defeats the mai purpose of the
clone.
TIA,
Will
hi Will,
Will T wrote:
> I have a machine named DOG with MSDE (computername=DOG). I clone the
> machine to another and rename the machine CAT. When I do this, SQL
> Server reports "Your SQL Server installation is either corrupt or has
> been tampered with (unknown package id). Please rerun setup." I
> understand why this happens, the computername changed.
> Is there a way to change the package id to work with the new
> computername? Of course I can reinstall MSDE, but that defeats the
> mai purpose of the clone.
to the best of my knowledge, this was a problem with SQL Server 7.0 and MSDE
1.0(http://support.microsoft.com/default...b;en-us;229875), as SQL
Server 7.0 could be "managed" rerunning the setup (
http://databasejournal.com/features/...0894_2194711_3 ),
where no work around was available for MSDE 1.0...
for SQL Server 2000, if you change the computer name, you only need to
delete and re-create the server registration in Enterprise Manager, but as
MSDE doew not provide it, you need nothing on MSDE 2000...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply