Enumerate Drives and Directories for .NET application

In the past I used the SQLDMO to get drive and directory information for a
target SQL Server. I do not want to use COM components in my .NET
application to accomplish this. What is the ".NET" way of doing this with
the assumption the SQL Server could be on a separate system than the one the
..NET application is running.
As you cannot be sure you have OS permissions to do this:
Run a profiler trace while doing this from your current app, or while EM is doing this, and pick up
the SQL procedures that are executed. Warning: Some of these are undocumented, use at your own risk.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bruce Parker" <bparkerhsd@.nospam.nospam> wrote in message
news:D96611AE-0CB4-41E7-92E4-A37F6216110D@.microsoft.com...
> In the past I used the SQLDMO to get drive and directory information for a
> target SQL Server. I do not want to use COM components in my .NET
> application to accomplish this. What is the ".NET" way of doing this with
> the assumption the SQL Server could be on a separate system than the one the
> .NET application is running.

Enumerate Drives and Directories for .NET application

In the past I used the SQLDMO to get drive and directory information for a
target SQL Server. I do not want to use COM components in my .NET
application to accomplish this. What is the ".NET" way of doing this with
the assumption the SQL Server could be on a separate system than the one the
.NET application is running.As you cannot be sure you have OS permissions to do this:
Run a profiler trace while doing this from your current app, or while EM is
doing this, and pick up
the SQL procedures that are executed. Warning: Some of these are undocumente
d, use at your own risk.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Bruce Parker" <bparkerhsd@.nospam.nospam> wrote in message
news:D96611AE-0CB4-41E7-92E4-A37F6216110D@.microsoft.com...
> In the past I used the SQLDMO to get drive and directory information for a
> target SQL Server. I do not want to use COM components in my .NET
> application to accomplish this. What is the ".NET" way of doing this with
> the assumption the SQL Server could be on a separate system than the one t
he
> .NET application is running.

Enterprise Edition doesnt install the SQL server instance.

I am trying to install the SQL Server 2005 Enterprise Edition, but on the components selection page, the only options I can check are Sample Book/Docs and Tools(Business Intelligence Studio, SQL Management Studio).

Even on the advanced page, those are the only options. Everything runs with no problem, except the SQL server instance.

I checked on the SQL Server Configuration Manager, and it does not show any SQL instances installed.

I tried adding a new instance using the add/remove>change for Microsoft SQL Server 2005 by selecting the setup.exe file in the Enterprise CD, but the it has the same options. If I select the setup.exe file from my Workgroup Edition CD, the option for adding new instances works.

What should I Do?

Cant I add SQL server instances using the Enterprise Edition? I was unable to install even the first instance.

The computer I am using meets all requirements and no SQL versions have been installed yet.

Thanks for the help.

go to the tools and servers folders respectively and install the components individually,.....dunno if it works just a surmise.....also you can refer this link might be useful........

http://dumthata.com/sqlchn/articles/install/insql.htm

|||

Enterprise Edition REQUIRES a server OS.

As you can see from the chart on this page, it does NOT install on Windows XP or VISTA.