Installing IIS v6.0 on SQL Server 2000

I have heard and read if at all possible do not install IIS on your SQL Servers. It is best to keep them seperate for 1) Performance 2) Opens up security issues. So we have always installed IIS on our web servers only. Isn't this the best case scenario
? I have a developer who wants to install IIS on all the SQL Server boxes and I am against it. What would his reasonings be?
Thanks,
Warren
IIS is very complex thing and there are many patches and unpatched things
especially if you enable full functionallity.
Here last one
http://www.securityfocus.com/bid/10116
If someone get access to the web server, if you use sql account with limited
rights he still will not be able to hurt your data, but if he get access to
the same machine where is your data he can do everything. The data is the
most critical thing. If you burn your web server it will take few hours to
get the application copied and configured but if your data server is gone
then you must find your last backup and most probably you will lose data,
see that I do not talk that if someone get sensitive data about your
business or clients he can burn your entire business or your reputacy.
If IIS is not critically needed at the SQL Server side - do not install it.
Price for another server is much lower that the risk.
Bojidar Alexandrov

Installing IIS v6.0 on SQL Server 2000

I have heard and read if at all possible do not install IIS on your SQL Servers. It is best to keep them seperate for 1) Performance 2) Opens up security issues. So we have always installed IIS on our web servers only. Isn't this the best case scenario? I have a developer who wants to install IIS on all the SQL Server boxes and I am against it. What would his reasonings be
Thanks
WarrenIIS is very complex thing and there are many patches and unpatched things
especially if you enable full functionallity.
Here last one
http://www.securityfocus.com/bid/10116
If someone get access to the web server, if you use sql account with limited
rights he still will not be able to hurt your data, but if he get access to
the same machine where is your data he can do everything. The data is the
most critical thing. If you burn your web server it will take few hours to
get the application copied and configured but if your data server is gone
then you must find your last backup and most probably you will lose data,
see that I do not talk that if someone get sensitive data about your
business or clients he can burn your entire business or your reputacy.
If IIS is not critically needed at the SQL Server side - do not install it.
Price for another server is much lower that the risk.
Bojidar Alexandrovsql

Installing IIS v6.0 on SQL Server 2000

I have heard and read if at all possible do not install IIS on your SQL Serv
ers. It is best to keep them seperate for 1) Performance 2) Opens up securi
ty issues. So we have always installed IIS on our web servers only. Isn't
this the best case scenario
? I have a developer who wants to install IIS on all the SQL Server boxes a
nd I am against it. What would his reasonings be?
Thanks,
WarrenIIS is very complex thing and there are many patches and unpatched things
especially if you enable full functionallity.
Here last one
http://www.securityfocus.com/bid/10116
If someone get access to the web server, if you use sql account with limited
rights he still will not be able to hurt your data, but if he get access to
the same machine where is your data he can do everything. The data is the
most critical thing. If you burn your web server it will take few hours to
get the application copied and configured but if your data server is gone
then you must find your last backup and most probably you will lose data,
see that I do not talk that if someone get sensitive data about your
business or clients he can burn your entire business or your reputacy.
If IIS is not critically needed at the SQL Server side - do not install it.
Price for another server is much lower that the risk.
Bojidar Alexandrov

Installing databases to different hard drives.

Can't find anything on how to install to drives other than sys. I'm brand new to Servers and Databases in general and trying to learn. How do I get databases to install on drive partitions other than my main system drive?

Hi,

don′t know if you mean database or instance in your case. Databases can be installed (or created) on medias using the CREATE DATABASE statement using the file destination (more details in the BOL) or with the GUI placing the files whereever on your local disks or SAN you want.

The instance and therefore the server service files can be installed on every drive you want for SQL Server 2000, for SQL Server 2005, there has been (and probably there is even after SP1) the restrictions that the files can only be installed on the system partition.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||That helps I'll have to try and find it. I did mean the Database Files. Not the Server Software. The Help File on my installation doesn't work so I'm having to do alot of digging to find out what to do. When MMC opens for the Help File I get a Page Cannot Be Displayed. I also have this problem with IIS. Since IIS installed first I put the question on a Forum at ASP.net and haven't gotten an answer yet. Does anybody here have an Idea about why my help file doesn't work? I missed something or didn't enable something but I can't find it. Everything else seems to work but the Help File. Or do I need to start another thread about it here? Thanks for the help.|||Hi,

simply get the new books online, or reinstall the help files from the media. I had that once too,that the help files (or just the link) where corrupted.

http://www.microsoft.com/downloads/details.aspx?FamilyID=be6a2c5d-00df-4220-b133-29c1e0b6585f&DisplayLang=en

(it′s the new BOL form April 2006)

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||I uninstalled everything all the way back to IIS I think whatever it was may be OK now. I hope. Thanks.

Installing A Failover Cluster

I have two matched servers, one will be Active and one will be Passive.
The servers have Windows 2000 Advanced Server and I have SQL Server 2000
Enterprise Edition.
My question is, do I also need a box called a Shared Disk Array, or can I
use another server I currently have that has lots of disk space on it?
Correction: I have Windows 2000 Advanced Server
"Vincel2k2" wrote:

> I have two matched servers, one will be Active and one will be Passive.
> The servers have Windows 2000 Advanced Server and I have SQL Server 2000
> Enterprise Edition.
> My question is, do I also need a box called a Shared Disk Array, or can I
> use another server I currently have that has lots of disk space on it?
>
|||You will indeed need shared storage.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Vincel2k2" <Vincel2k2@.discussions.microsoft.com> wrote in message
news:FF446D59-A73C-43EA-9EC2-4B9D03CFD51B@.microsoft.com...[vbcol=seagreen]
> Correction: I have Windows 2000 Advanced Server
> "Vincel2k2" wrote:
|||Hi
You need to get your self a Storage Area Network (SAN) to store your data
on.
For clustering, make sure that your hardware is on the Windows Hardware
Compatibility List (HCL)
Read the documentation on
http://www.microsoft.com/windowsserv...g/default.mspx
to get an understanding.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vincel2k2" <Vincel2k2@.discussions.microsoft.com> wrote in message
news:FF446D59-A73C-43EA-9EC2-4B9D03CFD51B@.microsoft.com...[vbcol=seagreen]
> Correction: I have Windows 2000 Advanced Server
> "Vincel2k2" wrote:
I[vbcol=seagreen]
|||I also have two matched servers with Win2003EntSrv that I would like to
install an active/passive failover cluster of Yukon on. Since this is a lab
environment and I don't have the $$ for a SAN, will it work with a Network
Storage HD? I realize the performance won't be great, but I'm looking for
the experience in how to build/configure the environment.
Any tips?
An alternative question for the lab environment is ... how would you do this
in two VPC? Or would you steer clear?
Thanks
Al
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> You need to get your self a Storage Area Network (SAN) to store your data
> on.
> For clustering, make sure that your hardware is on the Windows Hardware
> Compatibility List (HCL)
> Read the documentation on
> http://www.microsoft.com/windowsserv...g/default.mspx
> to get an understanding.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Vincel2k2" <Vincel2k2@.discussions.microsoft.com> wrote in message
> news:FF446D59-A73C-43EA-9EC2-4B9D03CFD51B@.microsoft.com...
> I
>
>
|||Virtual Server 2005 will work nicely for this test. See
http://www.hands-on-labs.com/microsoft.asp?ID=4477 for the steps
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"al_stark_born" <al_stark_born@.discussions.microsoft.com> wrote in message
news:E579B181-45E6-4DF2-8BCA-E7F1D2DD44C7@.microsoft.com...[vbcol=seagreen]
>I also have two matched servers with Win2003EntSrv that I would like to
> install an active/passive failover cluster of Yukon on. Since this is a
> lab
> environment and I don't have the $$ for a SAN, will it work with a Network
> Storage HD? I realize the performance won't be great, but I'm looking for
> the experience in how to build/configure the environment.
> Any tips?
> An alternative question for the lab environment is ... how would you do
> this
> in two VPC? Or would you steer clear?
> Thanks
> Al
> "Mike Epprecht (SQL MVP)" wrote:
sql

Installed, but can't ping 1433

Any and all help is appreciated as project deadline is approaching...

Background:
- Two servers, 1 running WinXP with all updates and 1 running Win2K3 Standard with all updates.
- Both have SQL Express 2005 June CTP installed
- Both have Visual Studio 2005 Express installed.
- Installation finished w/o any errors.
- Services are running (browser and database)
- TCP/IP and named pipes are enabled

Issue:
Can't ping 127.0.0.1:1433.
OSQL times out without being able to establish a connection
Windows Firewall is OFF.

Seems to be a connectivity issue, but I'm a newbie and can't figure out why I can't talk to the database.

As I said, any and all help is appreciated. Thanks to all in advance.

PM

Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.

Paul

Installed, but can't ping 1433

Any and all help is appreciated as project deadline is approaching...

Background:
- Two servers, 1 running WinXP with all updates and 1 running Win2K3 Standard with all updates.
- Both have SQL Express 2005 June CTP installed
- Both have Visual Studio 2005 Express installed.
- Installation finished w/o any errors.
- Services are running (browser and database)
- TCP/IP and named pipes are enabled

Issue:
Can't ping 127.0.0.1:1433.
OSQL times out without being able to establish a connection
Windows Firewall is OFF.

Seems to be a connectivity issue, but I'm a newbie and can't figure out why I can't talk to the database.

As I said, any and all help is appreciated. Thanks to all in advance.

PM

Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.

Paul

sql