Can't see mapped drives

Hi,
Am unable to see mapped drive when going to restore db in
sql 2000 enterprise manager. Service is set to start
with a lan acct. acct is in the local machine admin grp
and remote machine admin grp.
Any suggestions:-)
Thanks in advanceDo not use mapped drives for backup\restore with SQL server. Use UNC names
instead. SQL may or may not see a mapped drive correctly but will always
find a UNC share that it has permission and connection to.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
<anonymous@.discussions.microsoft.com> wrote in message
news:8f9b01c40541$3ade3230$a301280a@.phx.gbl...
> Hi,
> Am unable to see mapped drive when going to restore db in
> sql 2000 enterprise manager. Service is set to start
> with a lan acct. acct is in the local machine admin grp
> and remote machine admin grp.
> Any suggestions:-)
> Thanks in advance|||Hi,
You cant see the mapped drives in Enterprise manager. Rather you can
directly mention the UNC path directly in Enterprise manager or use
Restore database command from Query Analyzer.
Restore database <dbname> from disk='\\machinename\share\backupfile.bak'
with stats=10 With
Move 'logicaldatafile' to physcaldatafile',
Move 'logiallogfile' to physcallogfile'
stats will show the restore status
Thanks
Hari
MCDBA
<anonymous@.discussions.microsoft.com> wrote in message
news:8f9b01c40541$3ade3230$a301280a@.phx.gbl...
> Hi,
> Am unable to see mapped drive when going to restore db in
> sql 2000 enterprise manager. Service is set to start
> with a lan acct. acct is in the local machine admin grp
> and remote machine admin grp.
> Any suggestions:-)
> Thanks in advance|||It is possible to get SQL Server to use mapped network drives, through the u
se of trace flag 1807.
Check out knowledge base article #304261 for full details
http://support.microsoft.com/defaul...1&Product=sql2k

Can't see D partition

I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
physical drive divided into 5 partitions. When I choose to backup or restor
e
I can only see C and E partitions but not the D partition. All three are
NTFS partitions.
Thanks in advance.
JohnI found the problem, but don't understand why. The D partition did not have
the Everyone group define to read the drive, however other groups as well as
myself specifically have rights to it. Why does the group Everyone need to
have read in order to see it?
"John" wrote:

> I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has o
ne
> physical drive divided into 5 partitions. When I choose to backup or rest
ore
> I can only see C and E partitions but not the D partition. All three are
> NTFS partitions.
> Thanks in advance.
> John|||John wrote:
> I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has o
ne
> physical drive divided into 5 partitions. When I choose to backup or rest
ore
> I can only see C and E partitions but not the D partition. All three are
> NTFS partitions.
> Thanks in advance.
> John
Probably a permissions issue. What happens if you use the BACKUP
DATABASE command to send a backup to that volume?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||John wrote:
> I found the problem, but don't understand why. The D partition did not ha
ve
> the Everyone group define to read the drive, however other groups as well
as
> myself specifically have rights to it. Why does the group Everyone need t
o
> have read in order to see it?
>
When you run a backup, it's going to be run within the context of the
user that SQL Server is running under, NOT your personal login. Check
the service account for the SQL Server service, if that user doesn't
have rights to see the D: partition, then it's not going to show up in
your GUI.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Playing some more and comparing to a collegues setup, it appers to be the
local group system was missing.
Thanks so much for the quick responses.
"Tracy McKibben" wrote:

> John wrote:
> Probably a permissions issue. What happens if you use the BACKUP
> DATABASE command to send a backup to that volume?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Can't see D partition

I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
physical drive divided into 5 partitions. When I choose to backup or restore
I can only see C and E partitions but not the D partition. All three are
NTFS partitions.
Thanks in advance.
JohnI found the problem, but don't understand why. The D partition did not have
the Everyone group define to read the drive, however other groups as well as
myself specifically have rights to it. Why does the group Everyone need to
have read in order to see it?
"John" wrote:
> I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
> physical drive divided into 5 partitions. When I choose to backup or restore
> I can only see C and E partitions but not the D partition. All three are
> NTFS partitions.
> Thanks in advance.
> John|||John wrote:
> I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
> physical drive divided into 5 partitions. When I choose to backup or restore
> I can only see C and E partitions but not the D partition. All three are
> NTFS partitions.
> Thanks in advance.
> John
Probably a permissions issue. What happens if you use the BACKUP
DATABASE command to send a backup to that volume?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||John wrote:
> I found the problem, but don't understand why. The D partition did not have
> the Everyone group define to read the drive, however other groups as well as
> myself specifically have rights to it. Why does the group Everyone need to
> have read in order to see it?
>
When you run a backup, it's going to be run within the context of the
user that SQL Server is running under, NOT your personal login. Check
the service account for the SQL Server service, if that user doesn't
have rights to see the D: partition, then it's not going to show up in
your GUI.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Playing some more and comparing to a collegues setup, it appers to be the
local group system was missing.
Thanks so much for the quick responses.
"Tracy McKibben" wrote:
> John wrote:
> > I have SQL 2000 and SQL 2005 installed on a XP machine. The machine has one
> > physical drive divided into 5 partitions. When I choose to backup or restore
> > I can only see C and E partitions but not the D partition. All three are
> > NTFS partitions.
> >
> > Thanks in advance.
> > John
> Probably a permissions issue. What happens if you use the BACKUP
> DATABASE command to send a backup to that volume?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Can't see all drives in a cluster within Enterprise manager

When I am in Enterprise Manager to create a new database, I click on the location of the data and log file, I only see 1 drive where SQL Server was installed...How do I get SQL Server to display all the other drives the node owns in the cluster? I can view them under My Computer and within the Cluster Administrator. Each node owns it's own drives. But I should be able to see all drives owned by the node when browsing to create a new database so I can assign different drives for the Data and Log files.
Any ideas would be helpful
Thanks
WarrenPerhaps you have to restart SQL Server?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Warren Tyler" <anonymous@.discussions.microsoft.com> wrote in message
news:B873E1EB-030A-41F4-910A-1F15FE1A2D7B@.microsoft.com...
> When I am in Enterprise Manager to create a new database, I click on the location of the data and
log file, I only see 1 drive where SQL Server was installed...How do I get SQL Server to display all
the other drives the node owns in the cluster? I can view them under My Computer and within the
Cluster Administrator. Each node owns it's own drives. But I should be able to see all drives
owned by the node when browsing to create a new database so I can assign different drives for the
Data and Log files..
> Any ideas would be helpful,
> Thanks,
> Warren|||Dear Tibor
I will try it and let you know
Thanks
Warren|||Dear Tibor,
Same result. Still can't see all the drives?|||Sorry, that was just a wild guess...
Re-reading your original post, you say that you only see the drive where SQL Server was installed.
Do you mean the local drive? That would imply, methinks, that you didn't install the SQL Server as a
clustered SQL Server. SQL Server should not show the local drives when creating databases etc, it
should only show the "shared" drives.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Warren Tyler" <anonymous@.discussions.microsoft.com> wrote in message
news:7B544C67-CF57-4D8B-B726-3C259486A975@.microsoft.com...
> Dear Tibor,
> Same result. Still can't see all the drives?|||I found the answer. After a successful install of SQL Server on the cluster and testing fail-over. You have to take one node off-line and add dependencies (IE. the other drives) to the SQl Server , bring that node back on-line and repeat for the other node. This should be your last step then, re-test failover and moving the cluster between nodes
Whew
Thanks
Warren

Can't see all drives in a cluster within Enterprise manager

When I am in Enterprise Manager to create a new database, I click on the loc
ation of the data and log file, I only see 1 drive where SQL Server was inst
alled...How do I get SQL Server to display all the other drives the node own
s in the cluster? I can vi
ew them under My Computer and within the Cluster Administrator. Each node o
wns it's own drives. But I should be able to see all drives owned by the no
de when browsing to create a new database so I can assign different drives f
or the Data and Log files..
Any ideas would be helpful,
Thanks,
WarrenPerhaps you have to restart SQL Server?
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"Warren Tyler" <anonymous@.discussions.microsoft.com> wrote in message
news:B873E1EB-030A-41F4-910A-1F15FE1A2D7B@.microsoft.com...

quote:

---

> When I am in Enterprise Manager to create a new database, I click on the location of the d
ata and

---

log file, I only see 1 drive where SQL Server was installed...How do I get S
QL Server to display all
the other drives the node owns in the cluster? I can view them under My Com
puter and within the
Cluster Administrator. Each node owns it's own drives. But I should be abl
e to see all drives
owned by the node when browsing to create a new database so I can assign dif
ferent drives for the
Data and Log files..

quote:

---

> Any ideas would be helpful,
> Thanks,
> Warren

---

|||Dear Tibor,
I will try it and let you know.
Thanks,
Warren|||Dear Tibor,
Same result. Still can't see all the drives?|||Sorry, that was just a wild guess...
Re-reading your original post, you say that you only see the drive where SQL
Server was installed.
Do you mean the local drive? That would imply, methinks, that you didn't ins
tall the SQL Server as a
clustered SQL Server. SQL Server should not show the local drives when creat
ing databases etc, it
should only show the "shared" drives.
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=...ls
erver
"Warren Tyler" <anonymous@.discussions.microsoft.com> wrote in message
news:7B544C67-CF57-4D8B-B726-3C259486A975@.microsoft.com...

quote:

---

> Dear Tibor,
> Same result. Still can't see all the drives?

---

|||I found the answer. After a successful install of SQL Server on the cluster
and testing fail-over. You have to take one node off-line and add dependen
cies (IE. the other drives) to the SQl Server , bring that node back on-line
and repeat for the other n
ode. This should be your last step then, re-test failover and moving the cl
uster between nodes.
Whew!
Thanks,
Warren

can't move file for full-text index

Hi,
I need to move the file for my full-text catalog to a different drive due to
space issues. I've tried the following:
ALTER DATABASE mailarchivedec05
MODIFY FILE (NAME = MailArchiver3, filename = 'F:\FTDATA')
But get an error:
Server: Msg 5037, Level 16, State 1, Line 1
MODIFY FILE failed. Do not specify physical name.
According to the posting below I should take the database first offline, but
that gives a different error message about the db being offline.
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?query=full-text+alter&dg=&cat=en-us-technet-sqlserv&lang=en&cr=US&pt=261BA873-F3AB-420E-96D6-E3004596A551&catlist=328BAFD2-1A81-4558-B1DE-B6EB49F31B7E&dglist=&ptlist=&exp=&sloc=en-us
Any other ideas? Thanks.
Panos.
Yes, it should be the logical name. Here is an example of how to do it.
1) determine the logical name of your full-text catalog file. Issue
the following command:
SELECT name FROM SYS.DATABASE_FILES WHERE TYPE_DESC='FULLTEXT'
Note the value returned in the name column. This is your logical name for
your full-text catalog. It will look something like this:
sysft_MyCatalogName where MyCatalogName is the name of your catalog.
2) Issue the below command:
ALTER DATABASE database_name SET OFFLINE
3) Stop Full-Text Search
4) Move the full-text catalog to the new location
5) Restart Full-Text Search
6) Issue the below command:
ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name , FILENAME =
'new_path')
Where new_path is the new path to where you have moved your catalog.
7) Issue the below command:
ALTER DATABASE database_name SET ONLINE
You are now ready to query your full-text catalogs again.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
message news:CAB627A0-C3AE-44B7-B12F-F1D98643E6F6@.microsoft.com...
> Hi,
> I need to move the file for my full-text catalog to a different drive due
> to
> space issues. I've tried the following:
> ALTER DATABASE mailarchivedec05
> MODIFY FILE (NAME = MailArchiver3, filename = 'F:\FTDATA')
> But get an error:
> Server: Msg 5037, Level 16, State 1, Line 1
> MODIFY FILE failed. Do not specify physical name.
> According to the posting below I should take the database first offline,
> but
> that gives a different error message about the db being offline.
> http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?query=full-text+alter&dg=&cat=en-us-technet-sqlserv&lang=en&cr=US&pt=261BA873-F3AB-420E-96D6-E3004596A551&catlist=328BAFD2-1A81-4558-B1DE-B6EB49F31B7E&dglist=&ptlist=&exp=&sloc=en-us
> Any other ideas? Thanks.
> Panos.
|||Hilary,
It still doesn't work. By the way I am using 2000 not 2005, does it make any
difference? For example the command SELECT name FROM SYS.DATABASE_FILES
WHERE TYPE_DESC='FULLTEXT'
does't work. But I am sure I have the right logical name for my index.
I've managed to physically move the files as in step 4 but when the issue
the alter database command I still get the same error message. It doesn't
also like it when the database is offline, gives me an error.
Any other ideas? Thanks.
Panos.
"Hilary Cotter" wrote:

> Yes, it should be the logical name. Here is an example of how to do it.
> 1) determine the logical name of your full-text catalog file. Issue
> the following command:
> SELECT name FROM SYS.DATABASE_FILES WHERE TYPE_DESC='FULLTEXT'
> Note the value returned in the name column. This is your logical name for
> your full-text catalog. It will look something like this:
> sysft_MyCatalogName where MyCatalogName is the name of your catalog.
> 2) Issue the below command:
> ALTER DATABASE database_name SET OFFLINE
> 3) Stop Full-Text Search
> 4) Move the full-text catalog to the new location
> 5) Restart Full-Text Search
> 6) Issue the below command:
> ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name , FILENAME =
> 'new_path')
> Where new_path is the new path to where you have moved your catalog.
> 7) Issue the below command:
> ALTER DATABASE database_name SET ONLINE
> You are now ready to query your full-text catalogs again.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
> message news:CAB627A0-C3AE-44B7-B12F-F1D98643E6F6@.microsoft.com...
>
>
|||I did not realize you were using SQL 2000. In this case follow these steps:
http://support.microsoft.com/kb/240867
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
message news:153D7F5D-76C4-45D2-835B-B0AB382DDD7B@.microsoft.com...[vbcol=seagreen]
> Hilary,
> It still doesn't work. By the way I am using 2000 not 2005, does it make
> any
> difference? For example the command SELECT name FROM SYS.DATABASE_FILES
> WHERE TYPE_DESC='FULLTEXT'
> does't work. But I am sure I have the right logical name for my index.
> I've managed to physically move the files as in step 4 but when the issue
> the alter database command I still get the same error message. It doesn't
> also like it when the database is offline, gives me an error.
> Any other ideas? Thanks.
> Panos.
>
> "Hilary Cotter" wrote:
|||That worked fine. Thanks.
"Hilary Cotter" wrote:

> I did not realize you were using SQL 2000. In this case follow these steps:
> http://support.microsoft.com/kb/240867
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
> message news:153D7F5D-76C4-45D2-835B-B0AB382DDD7B@.microsoft.com...
>
>

can't install SQL Server on a partition other than c:\

Hello --
My laptop drive is partitioned into c: and e:. I want to install on
e:.
During Install, in Feature Selection, when I click the icon for Client
Components, the Browse button to allow an install path other than c:
\... is disabled, indicating that the shared path has already been
configured).
Can someone tell me
1 - what I installed prior that does not allow me to install the
complete SQL Server on e:?
2 - what must I uninstall and then reinstall, and, in what sequence,
to be able to install on e:?
Thanks in advance for any help.
Larry MehlYou can't install the whole SQL Server related files into your "e:" drive.
Some files are installed to the default path "C:\Program Files\Microsoft SQL
Server...". Generally, you can say "Common components like SSIS, Client
Components etc. will be installed to this default path"
--
Ekrem Önsoy
"mehlREMOVETHIS@.cyvest.com" <mehl@.cyvest.com> wrote in message
news:5581b71e-f6de-4d58-833e-e931a8d5c3b3@.t12g2000prg.googlegroups.com...
> Hello --
> My laptop drive is partitioned into c: and e:. I want to install on
> e:.
> During Install, in Feature Selection, when I click the icon for Client
> Components, the Browse button to allow an install path other than c:
> \... is disabled, indicating that the shared path has already been
> configured).
> Can someone tell me
> 1 - what I installed prior that does not allow me to install the
> complete SQL Server on e:?
> 2 - what must I uninstall and then reinstall, and, in what sequence,
> to be able to install on e:?
> Thanks in advance for any help.
> Larry Mehl
>
>|||Unfortunately, that's one of the fundamentally flawed design choices that SQL
Server seems to be stuck with. It's fundamentally flawed because this forces
the system to store states on the local machine. Not being able to choose an
arbitrary drive is just a minor inconvenience in comparison.
Linchi
"mehlREMOVETHIS@.cyvest.com" wrote:
> Hello --
> My laptop drive is partitioned into c: and e:. I want to install on
> e:.
> During Install, in Feature Selection, when I click the icon for Client
> Components, the Browse button to allow an install path other than c:
> \... is disabled, indicating that the shared path has already been
> configured).
> Can someone tell me
> 1 - what I installed prior that does not allow me to install the
> complete SQL Server on e:?
> 2 - what must I uninstall and then reinstall, and, in what sequence,
> to be able to install on e:?
> Thanks in advance for any help.
> Larry Mehl
>
>|||On May 4, 2:09 am, Ekrem =D6nsoy <ek...@.compecta.com> wrote:
> You can't install the whole SQL Server related files into your "e:" drive.=
> Some files are installed to the default path "C:\Program Files\Microsoft S=QL
> Server...". Generally, you can say "Common components like SSIS, Client
> Components etc. will be installed to this default path"
> --
> Ekrem =D6nsoy
> "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> news:5581b71e-f6de-4d58-833e-e931a8d5c3b3@.t12g2000prg.googlegroups.com...
> > Hello --
> > My laptop drive is partitioned into c: and e:. I want to install on
> > e:.
> > During Install, in Feature Selection, when I click the icon for Client
> > Components, the Browse button to allow an install path other than c:
> > \... is disabled, indicating that the shared path has already been
> > configured).
> > Can someone tell me
> > 1 - what I installed prior that does not allow me to install the
> > complete SQL Server on e:?
> > 2 - what must I uninstall and then reinstall, and, in what sequence,
> > to be able to install on e:?
> > Thanks in advance for any help.
> > Larry Mehl
Ekrem --
Thank you.
How do I install "Common components like SSIS, Client Components
etc. ... to the default path" so that I can then install the remaining
part of SQL Server to my "e:" drive?
Do I execute the install process twice ... so that
- I first install the common components (in c:) and
- then install I install the remaining components in e: ?
Is it only the common components that cause this, or was it the
installation of other applications such as .NET, Document Explorer,
2005 Samples, Native Client, Setup Support Files, VSS Writer that
installed into c: and are consequently causing this limitation?
If I must, I will enlarge the c: partition to allow installation of
everything into c: What partition manager do you recommend for this?
I will appreciate any further information.
Larry Mehl|||You can install services and components to different paths at once.
In SQL Server Setup, click Advanced button in Components to Install window.
Click on the item and then click the Browse button to install it to a
different path in the Feature Selection window.
For example you can install Database Engine, Analysis Services, Reporting
Services to a different path, but you can't change the path of Documentation
and Samples or Client Components...
--
Ekrem Önsoy
"mehlREMOVETHIS@.cyvest.com" <mehl@.cyvest.com> wrote in message
news:24957b8a-c6ce-426e-9221-04e844f32777@.t12g2000prg.googlegroups.com...
On May 4, 2:09 am, Ekrem Önsoy <ek...@.compecta.com> wrote:
> You can't install the whole SQL Server related files into your "e:" drive.
> Some files are installed to the default path "C:\Program Files\Microsoft
> SQL
> Server...". Generally, you can say "Common components like SSIS, Client
> Components etc. will be installed to this default path"
> --
> Ekrem Önsoy
> "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> news:5581b71e-f6de-4d58-833e-e931a8d5c3b3@.t12g2000prg.googlegroups.com...
> > Hello --
> > My laptop drive is partitioned into c: and e:. I want to install on
> > e:.
> > During Install, in Feature Selection, when I click the icon for Client
> > Components, the Browse button to allow an install path other than c:
> > \... is disabled, indicating that the shared path has already been
> > configured).
> > Can someone tell me
> > 1 - what I installed prior that does not allow me to install the
> > complete SQL Server on e:?
> > 2 - what must I uninstall and then reinstall, and, in what sequence,
> > to be able to install on e:?
> > Thanks in advance for any help.
> > Larry Mehl
Ekrem --
Thank you.
How do I install "Common components like SSIS, Client Components
etc. ... to the default path" so that I can then install the remaining
part of SQL Server to my "e:" drive?
Do I execute the install process twice ... so that
- I first install the common components (in c:) and
- then install I install the remaining components in e: ?
Is it only the common components that cause this, or was it the
installation of other applications such as .NET, Document Explorer,
2005 Samples, Native Client, Setup Support Files, VSS Writer that
installed into c: and are consequently causing this limitation?
If I must, I will enlarge the c: partition to allow installation of
everything into c: What partition manager do you recommend for this?
I will appreciate any further information.
Larry Mehl|||On May 4, 12:04 pm, Ekrem =D6nsoy <ek...@.compecta.com> wrote:
> You can install services and components to different paths at once.
> In SQL Server Setup, click Advanced button in Components to Install window=.
> Click on the item and then click the Browse button to install it to a
> different path in the Feature Selection window.
> For example you can install Database Engine, Analysis Services, Reporting
> Services to a different path, but you can't change the path of Documentati=on
> and Samples or Client Components...
> --
> Ekrem =D6nsoy
> "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> news:24957b8a-c6ce-426e-9221-04e844f32777@.t12g2000prg.googlegroups.com...
> On May 4, 2:09 am, Ekrem =D6nsoy <ek...@.compecta.com> wrote:
>
> > You can't install the whole SQL Server related files into your "e:" driv=e.
> > Some files are installed to the default path "C:\Program Files\Microsoft=
> > SQL
> > Server...". Generally, you can say "Common components like SSIS, Client
> > Components etc. will be installed to this default path"
> > --
> > Ekrem =D6nsoy
> > "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> >news:5581b71e-f6de-4d58-833e-e931a8d5c3b3@.t12g2000prg.googlegroups.com...=
> > > Hello --
> > > My laptop drive is partitioned into c: and e:. I want to install on
> > > e:.
> > > During Install, in Feature Selection, when I click the icon for Client=
> > > Components, the Browse button to allow an install path other than c:
> > > \... is disabled, indicating that the shared path has already been
> > > configured).
> > > Can someone tell me
> > > 1 - what I installed prior that does not allow me to install the
> > > complete SQL Server on e:?
> > > 2 - what must I uninstall and then reinstall, and, in what sequence,
> > > to be able to install on e:?
> > > Thanks in advance for any help.
> > > Larry Mehl
> Ekrem --
> Thank you.
> How do I install "Common components like SSIS, Client Components
> etc. ... to the default path" so that I can then install the remaining
> part of SQL Server to my "e:" drive?
> Do I execute the install process twice ... so that
> - I first install the common components (in c:) and
> - then install I install the remaining components in e: ?
> Is it only the common components that cause this, or was it the
> installation of other applications such as .NET, Document Explorer,
> 2005 Samples, Native Client, Setup Support Files, VSS Writer that
> installed into c: and are consequently causing this limitation?
> If I must, I will enlarge the c: partition to allow installation of
> everything into c: What partition manager do you recommend for this?
> I will appreciate any further information.
> Larry Mehl
Ekrem --
Thank you for the method.
Linchi -- Thanks for responding. His response seems to conflict with
yours. What do you think?
Larry|||And just to elaborate, some of the components/items are customizable, some
are not.
Also I don't see how Linchi's reply conflicts with anything else that has
been stated in this thread.
On 5/4/08 3:04 PM, in article
6C568227-DB0D-428C-AF70-BD0AC2BE835E@.microsoft.com, "Ekrem Önsoy"
<ekrem@.compecta.com> wrote:
> You can install services and components to different paths at once.
> In SQL Server Setup, click Advanced button in Components to Install window.
> Click on the item and then click the Browse button to install it to a
> different path in the Feature Selection window.
> For example you can install Database Engine, Analysis Services, Reporting
> Services to a different path, but you can't change the path of Documentation
> and Samples or Client Components...|||To be clearer, what is the confliction do you think?
--
Ekrem Önsoy
"mehlREMOVETHIS@.cyvest.com" <mehl@.cyvest.com> wrote in message
news:ef59ea4d-a2e7-4cb1-af9a-8475dc81f80f@.j9g2000prn.googlegroups.com...
On May 4, 12:04 pm, Ekrem Önsoy <ek...@.compecta.com> wrote:
> You can install services and components to different paths at once.
> In SQL Server Setup, click Advanced button in Components to Install
> window.
> Click on the item and then click the Browse button to install it to a
> different path in the Feature Selection window.
> For example you can install Database Engine, Analysis Services, Reporting
> Services to a different path, but you can't change the path of
> Documentation
> and Samples or Client Components...
> --
> Ekrem Önsoy
> "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> news:24957b8a-c6ce-426e-9221-04e844f32777@.t12g2000prg.googlegroups.com...
> On May 4, 2:09 am, Ekrem Önsoy <ek...@.compecta.com> wrote:
>
> > You can't install the whole SQL Server related files into your "e:"
> > drive.
> > Some files are installed to the default path "C:\Program Files\Microsoft
> > SQL
> > Server...". Generally, you can say "Common components like SSIS, Client
> > Components etc. will be installed to this default path"
> > --
> > Ekrem Önsoy
> > "mehlREMOVET...@.cyvest.com" <m...@.cyvest.com> wrote in message
> >news:5581b71e-f6de-4d58-833e-e931a8d5c3b3@.t12g2000prg.googlegroups.com...
> > > Hello --
> > > My laptop drive is partitioned into c: and e:. I want to install on
> > > e:.
> > > During Install, in Feature Selection, when I click the icon for Client
> > > Components, the Browse button to allow an install path other than c:
> > > \... is disabled, indicating that the shared path has already been
> > > configured).
> > > Can someone tell me
> > > 1 - what I installed prior that does not allow me to install the
> > > complete SQL Server on e:?
> > > 2 - what must I uninstall and then reinstall, and, in what sequence,
> > > to be able to install on e:?
> > > Thanks in advance for any help.
> > > Larry Mehl
> Ekrem --
> Thank you.
> How do I install "Common components like SSIS, Client Components
> etc. ... to the default path" so that I can then install the remaining
> part of SQL Server to my "e:" drive?
> Do I execute the install process twice ... so that
> - I first install the common components (in c:) and
> - then install I install the remaining components in e: ?
> Is it only the common components that cause this, or was it the
> installation of other applications such as .NET, Document Explorer,
> 2005 Samples, Native Client, Setup Support Files, VSS Writer that
> installed into c: and are consequently causing this limitation?
> If I must, I will enlarge the c: partition to allow installation of
> everything into c: What partition manager do you recommend for this?
> I will appreciate any further information.
> Larry Mehl
Ekrem --
Thank you for the method.
Linchi -- Thanks for responding. His response seems to conflict with
yours. What do you think?
Larry

Can't get new LUN/Logical Drive visible from within SQL Server on cluster.

We have had a working SQL Server 2000 SP3 (default instance) on two node MS
Windows 2000 Advanced Server with MS Cluster servcie working for over a year
now.
The shared Q: and E: drives are actually two seperate LUNS from a SAN
connected via Host Bus Adapters..
Recently, needed another logical drive. Added another LUN from the SAN.
Configured it as basic disk, drive letter F: It show up in Disk Manager
exactly like the pre-existing E: drive in terms of attribute values.
It is a working a normal drive on the primary node.
Using the cluster administrator, it was added as a physical disk resource
and added to the iManage SQL Cluster Group, the same as the E: drive.
It shows up as online and owned by the primary node where the SQL Server is
active.
However, it does not show up with the Enterprise Manage for the SQL Server.
Only E: is showing. Have even rebooted the nodes for the cluster.
The logical drive F: is available for all other uses, but it cannot be seen
by the SQL Server.
Scott Lord
Willkie Farr & Gallagher LLP
New York, New York
slord@.willkie.com
you have to add new drive as a SQL Server Dependency in cluster administrator. once you added into sqlserver dependency then enterprise mangager see the drive.
Regards
Ram
Systems SQL DBA|||I for get tell one more step . you have to add resource in Cluster administrator.
Regards
Ram

Quote:

Originally posted by yvr4
you have to add new drive as a SQL Server Dependency in cluster administrator. once you added into sqlserver dependency then enterprise mangager see the drive.
Regards
Ram
Systems SQL DBA

|||Have you made it a dependency of the SQL Server group?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
..
"Scott Lord" <nomail@.nomail.com> wrote in message
news:ehHkGQKCFHA.2404@.TK2MSFTNGP15.phx.gbl...
We have had a working SQL Server 2000 SP3 (default instance) on two node MS
Windows 2000 Advanced Server with MS Cluster servcie working for over a year
now.
The shared Q: and E: drives are actually two seperate LUNS from a SAN
connected via Host Bus Adapters..
Recently, needed another logical drive. Added another LUN from the SAN.
Configured it as basic disk, drive letter F: It show up in Disk Manager
exactly like the pre-existing E: drive in terms of attribute values.
It is a working a normal drive on the primary node.
Using the cluster administrator, it was added as a physical disk resource
and added to the iManage SQL Cluster Group, the same as the E: drive.
It shows up as online and owned by the primary node where the SQL Server is
active.
However, it does not show up with the Enterprise Manage for the SQL Server.
Only E: is showing. Have even rebooted the nodes for the cluster.
The logical drive F: is available for all other uses, but it cannot be seen
by the SQL Server.
Scott Lord
Willkie Farr & Gallagher LLP
New York, New York
slord@.willkie.com
|||Thanks to Tom Moreau and yvr4 for their answers. I am pretty sure they both
identified the problem, I haven't been able to successfully test their
solution.
I had not added it as a dependency for the SQL Server. I only had it added
it to the SQL Cluster Group. I just tried adding it as a dependency to the
SQL Server.
FYI: The disk resource F: is online to the primary node and the SQL Server
is and online to the primary node.
In the cluster administrator, simply pulling up the properties to the SQL
Server and going to the Dependencies tab showed the F: drive on the left as
an available resource to be added as a dependency. I highlighted the F:
drive and tried to add it. I got a slightly ambiguous error message which I
will also type the text from the error message box.
Message box title: Cluster Administrator
Yellow triangle with exclamation point icon.
An error occurred attempting to add 'Disk F:' as a dependency of 'SQL
Server':
The operation could not be completed because the cluster resource is online.
Error ID: 5019 (0000139b).
This is a production environment: I am concerned about two things. Which
resource, the F: drive or the SQL Server is the error message meaning when
it say 'because the cluster resource is online' I know that I would like
for it to mean the disk drive, but I am modifying the SQL Server dependency
tree, so it is possible it means the SQL Server. I can't take that offline
except during a maintenance window. Also, if I simply take the disk drive
F: resource offline in the cluster administrator window in order to add it
to the SQL Server dependency tree, will it cause a fail-over of the SQL
Server since the newly defined dependency, F: disk drive resource, is not
online. That is what the dependency tree is for, isn't it.
I hope the answer is simply, take the disk drive F: resource offline in
cluster administrator, add it as a dependency to the SQL Server, and it will
either come online itself or I can manually bring it online, without the SQL
Server failing over.
Alternatively, I can accept needing to take the SQL Server offline in the
cluster administrator, having the disk drive F: resource online, adding it
as a dependency to the SQL Server and bringing the SQL Server online.
Sorry about these additional questions, but I thought the error message was
a little ambiguous, and I am concerned about adding an offline resource as a
dependency if it will cause a fail-over in our production environment. We
do not have a test cluster to try this on.
Scott Lord
Willkie Farr & Gallagher LLP
New York, New York
slord@.willkie.com
"yvr4" <yvr4.1jt3a0@.mail.mcse.ms> wrote in message
news:yvr4.1jt3a0@.mail.mcse.ms...
> you have to add new drive as a SQL Server Dependency in cluster
> administrator. once you added into sqlserver dependency then enterprise
> mangager see the drive.
> Regards
> Ram
> Systems SQL DBA
>
> --
> yvr4
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message1393040.html
>
|||That error message is correct. You must take the SQL Server resource
offline to change its dependencies.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Scott Lord" <nomail@.nomail.com> wrote in message
news:e97ziSUCFHA.2384@.TK2MSFTNGP14.phx.gbl...
> Thanks to Tom Moreau and yvr4 for their answers. I am pretty sure they
both
> identified the problem, I haven't been able to successfully test their
> solution.
> I had not added it as a dependency for the SQL Server. I only had it
added
> it to the SQL Cluster Group. I just tried adding it as a dependency to
the
> SQL Server.
> FYI: The disk resource F: is online to the primary node and the SQL
Server
> is and online to the primary node.
> In the cluster administrator, simply pulling up the properties to the SQL
> Server and going to the Dependencies tab showed the F: drive on the left
as
> an available resource to be added as a dependency. I highlighted the F:
> drive and tried to add it. I got a slightly ambiguous error message which
I
> will also type the text from the error message box.
> --
> Message box title: Cluster Administrator
> Yellow triangle with exclamation point icon.
> An error occurred attempting to add 'Disk F:' as a dependency of 'SQL
> Server':
> The operation could not be completed because the cluster resource is
online.
> Error ID: 5019 (0000139b).
> --
> This is a production environment: I am concerned about two things. Which
> resource, the F: drive or the SQL Server is the error message meaning when
> it say 'because the cluster resource is online' I know that I would like
> for it to mean the disk drive, but I am modifying the SQL Server
dependency
> tree, so it is possible it means the SQL Server. I can't take that
offline
> except during a maintenance window. Also, if I simply take the disk drive
> F: resource offline in the cluster administrator window in order to add it
> to the SQL Server dependency tree, will it cause a fail-over of the SQL
> Server since the newly defined dependency, F: disk drive resource, is not
> online. That is what the dependency tree is for, isn't it.
> I hope the answer is simply, take the disk drive F: resource offline in
> cluster administrator, add it as a dependency to the SQL Server, and it
will
> either come online itself or I can manually bring it online, without the
SQL
> Server failing over.
> Alternatively, I can accept needing to take the SQL Server offline in the
> cluster administrator, having the disk drive F: resource online, adding it
> as a dependency to the SQL Server and bringing the SQL Server online.
> Sorry about these additional questions, but I thought the error message
was
> a little ambiguous, and I am concerned about adding an offline resource as
a
> dependency if it will cause a fail-over in our production environment. We
> do not have a test cluster to try this on.
> Scott Lord
> Willkie Farr & Gallagher LLP
> New York, New York
> slord@.willkie.com
> "yvr4" <yvr4.1jt3a0@.mail.mcse.ms> wrote in message
> news:yvr4.1jt3a0@.mail.mcse.ms...
>
|||Thank you Geoff.
I will schedule the change to the dependency tree for SQL Server to occur
during a maintenance window.
Scott
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23mHvubUCFHA.4004@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> That error message is correct. You must take the SQL Server resource
> offline to change its dependencies.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Scott Lord" <nomail@.nomail.com> wrote in message
> news:e97ziSUCFHA.2384@.TK2MSFTNGP14.phx.gbl...
> both
> added
> the
> Server
SQL[vbcol=seagreen]
> as
which[vbcol=seagreen]
> I
> online.
Which[vbcol=seagreen]
when[vbcol=seagreen]
like[vbcol=seagreen]
> dependency
> offline
drive[vbcol=seagreen]
it[vbcol=seagreen]
not[vbcol=seagreen]
> will
> SQL
the[vbcol=seagreen]
it[vbcol=seagreen]
> was
as[vbcol=seagreen]
> a
We[vbcol=seagreen]
enterprise
>