Installing MSDE with VB application

Does anyone have any experience or knowledge what would be best way of installing msde with vb application
I created vb app with msde database , right now app uses sql server, iam planning to move sql database to msde and distribute that with vb app. What would be best approach for distributing and installing those files? Does vb package deployment will do the trick or I should acuire some professional setup program ??
Thanks
RobertRefer to MS website about recent updations on MSDE.

installed ssl-certificate -> SQL-Server locked !

Hello NG,
we just installed a ssl-certificate (created with MS-selfssl) on the IIS of
a win2k-Server and since reboot the SQL-Server on the same machine cannot be
accessed anymore. The Enterprise Manager tells us "SSL Security Error.
ConnectionOpen (SECDoClientHandshake()).."
Meanwhile we deleted the certificate, but the server's still locked. What
can we do?
Greatful for any hint,
MarcMake sure that the "force Protocol encryption" option is removed from both
the
Server Network Utility and the CLient network Utility.
Once you remove the certificate, SQL must be restarted. Just MSSQLServer
service, not the machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin,
But how can we modify the Database's options? They're locked as well.
Are there some command line options? How are they applied?
thanks,
Marc
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> schrieb im Newsbei
trag
news:BtG697KIEHA.3772@.cpmsftngxa06.phx.gbl...
> Make sure that the "force Protocol encryption" option is removed from both
> the
> Server Network Utility and the CLient network Utility.
> Once you remove the certificate, SQL must be restarted. Just MSSQLServer
> service, not the machine.
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||There are no database options that relate to protocol encryption.
Does the server start?
Is the problem only establishing connections from Enterprise Manager?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Meanwhile I checked the two services : "force Protocol encryption" had
already been deactivated for both active protocols (Named Pipes and TCP/IP).
Before, we also removed the certificate. Nothing happened. The SQL-Server is
still locked.
General question : how can we use a ssl-certificate for the web-service
together with a SQL-Server on the same machine? As far as I experienced now,
this is a dangerous experiment if no real MS-Experts are around!? Are there
manuals available?
Still greatful for any hint,
Marc
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> schrieb im Newsbei
trag
news:BtG697KIEHA.3772@.cpmsftngxa06.phx.gbl...
> Make sure that the "force Protocol encryption" option is removed from both
> the
> Server Network Utility and the CLient network Utility.
> Once you remove the certificate, SQL must be restarted. Just MSSQLServer
> service, not the machine.
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||> There are no database options that relate to protocol encryption.
My mistake/misunderstanding - sorry!

> Does the server start?
It looks like. The green arrow shows up.

> Is the problem only establishing connections from Enterprise Manager?
No - all connections (ODBC, MS-Access).
Marc

> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||From previous post:
"General question : how can we use a ssl-certificate for the web-service
together with a SQL-Server on the same machine? As far as I experienced now,
this is a dangerous experiment if no real MS-Experts are around!? Are there
manuals available?"
For SQL 2000 to use protocol encryption, SSL, the server must have a
Certificate issued to the FQDN name of the computer.
This would be the same if you were to setup IIS for SSL using Server
Authentication. So, if IIS and SQL are on the same machine,
then you just need one certificate. You can use the IIS tools to install
the certificate, since SQL doesn't supply any user tools.
I wrote the following two articles. and did the Webcast on setting up SSL
with SQL 2000.
316898 HOW TO: Enable SSL Encryption for SQL Server 2000 with Microsoft
http://support.microsoft.com/?id=316898
276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
Server
http://support.microsoft.com/?id=276553
324777 Support WebCast: Microsoft SQL Server 2000: How to Configure SSL
http://support.microsoft.com/?id=324777
Hope this helps,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I just replied to your earlier posting.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||> I wrote the following two articles. and did the Webcast on setting up SSL
> with SQL 2000.
> 316898 HOW TO: Enable SSL Encryption for SQL Server 2000 with Microsoft
> http://support.microsoft.com/?id=316898
Through this article I found that the certificate had not been deleted
completely. So I deleted the rest, rebooted and had the database back!
Thanks for the Article!
We installed SP3 meanwhile and we still intend to use SSL, se we keep on
experimenting and I hope that the articles will guide us safely ...
Thanks again,
Marc|||Does anyone have any idea how or why this is happening to me all of a
sudden and what to do about it?
Win2000 Server, with SQL Server 2000, IIS, Been running applications and
SQL just fine for a long time and all of a sudden now getting this error
constantly:
[DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security err
or.
ANY help would be greatly appreciated. I cannot find anything on the
net about this.
JWP
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Installation standards

I would like to know if Microsoft publishes SQL Server standards which direct or mandate that the database Transaction Log be created on a Mirrored set. Some no-technical management people where I work are stating that placing Transaction Logs on a Mirro
red set is a Microsoft standard. I am a DBA and have worked with SQL Server since version 4.2 and all versions since and this is news to me. I understand the performance benefits of placing the Trans. Log on the Mirror BUT in our environment, the operat
ing system is also on the Mirror and we have junior level engineers managing the systems who know nothing about SQL Server. Therefore, I feel placing the Transaction Log on the Mirror in our environment would create unneccessary risks; especially since w
e are having no performance problems.
PLEASE!!! I would appreciate the response of anyone who can tell me if placing the Trans. Log on a Mirror is a Microsoft Standard or not. I have always understood Microsoft's statements regarding Mirroring the Trans. Log to be merely suggestions or reco
mmendations not a directive. I do not want upper management sold on accepting what I see as a risk by non-technical people who are stating that placing the database Transaction Log on a Mirrored set is a standard that we have to follow.
Sorry for being so lengthy but I am take my job and protecting data very seriously and this issue is making me lose sleep.
It seems like you understand the implications for this, so the short answer is: "No, this is not a
directive, only a recommendation".
One thing, though: If the part where the data is crashes in any way, you definitely want to get to
your tlog files, as it allow you to backup the log using NO_TRUNCATE. Placing the log with the data
is increased risk exposure in this regard.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SQLDBA_723" <SQLDBA_723@.discussions.microsoft.com> wrote in message
news:7C2CD527-1514-4F9B-90E9-0E118EB2C017@.microsoft.com...
> I would like to know if Microsoft publishes SQL Server standards which direct or mandate that the
database Transaction Log be created on a Mirrored set. Some no-technical management people where I
work are stating that placing Transaction Logs on a Mirrored set is a Microsoft standard. I am a
DBA and have worked with SQL Server since version 4.2 and all versions since and this is news to me.
I understand the performance benefits of placing the Trans. Log on the Mirror BUT in our
environment, the operating system is also on the Mirror and we have junior level engineers managing
the systems who know nothing about SQL Server. Therefore, I feel placing the Transaction Log on the
Mirror in our environment would create unneccessary risks; especially since we are having no
performance problems.
> PLEASE!!! I would appreciate the response of anyone who can tell me if placing the Trans. Log on
a Mirror is a Microsoft Standard or not. I have always understood Microsoft's statements regarding
Mirroring the Trans. Log to be merely suggestions or recommendations not a directive. I do not want
upper management sold on accepting what I see as a risk by non-technical people who are stating that
placing the database Transaction Log on a Mirrored set is a standard that we have to follow.
> Sorry for being so lengthy but I am take my job and protecting data very seriously and this issue
is making me lose sleep.
|||Hi,
[vbcol=seagreen]
Iam not speaking for Microsoft here but just letting you know what
information I have with respect to your concern.Iam not aware about any such
"standard" that Microsoft, has w.r.t SQL2000 setup.All the important things
that you have to take care before SQL2000 setup like required space, MDAC
level,IE level etc are mentioned in the readme.txt file or "help" topics
that accompany the setup CD.Any performance enhancement other than those are
solely left as an exercise to the person who is installing, based on his/her
experience with the same.The PSS team reports to the SQLServer team the
various issues that customers face regularly which often result in poor
server performance, disaster recovery etc.Based on those, Microsoft
occassionally publishes whitepapers for the benefit of SQLServer admins and
users.Here are some:
'SQL Server 2000 Operations Guide'
http://www.microsoft.com/technet/pro...n/sqlops0.mspx
'High Availability Resources'
http://www.microsoft.com/sql/techinf...ailability.asp
[vbcol=seagreen]
making me lose sleep.
Not that it's any of my business, but I couldn't help asking it.What is your
role at this workplace? Based on the above statement, it seems you are a
DBA.If so, why should you let those 'junior level engineers' manage the
SQLServer systems?
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"SQLDBA_723" <SQLDBA_723@.discussions.microsoft.com> wrote in message
news:7C2CD527-1514-4F9B-90E9-0E118EB2C017@.microsoft.com...
> I would like to know if Microsoft publishes SQL Server standards which
direct or mandate that the database Transaction Log be created on a Mirrored
set. Some no-technical management people where I work are stating that
placing Transaction Logs on a Mirrored set is a Microsoft standard. I am a
DBA and have worked with SQL Server since version 4.2 and all versions since
and this is news to me. I understand the performance benefits of placing
the Trans. Log on the Mirror BUT in our environment, the operating system is
also on the Mirror and we have junior level engineers managing the systems
who know nothing about SQL Server. Therefore, I feel placing the
Transaction Log on the Mirror in our environment would create unneccessary
risks; especially since we are having no performance problems.
> PLEASE!!! I would appreciate the response of anyone who can tell me if
placing the Trans. Log on a Mirror is a Microsoft Standard or not. I have
always understood Microsoft's statements regarding Mirroring the Trans. Log
to be merely suggestions or recommendations not a directive. I do not want
upper management sold on accepting what I see as a risk by non-technical
people who are stating that placing the database Transaction Log on a
Mirrored set is a standard that we have to follow.
> Sorry for being so lengthy but I am take my job and protecting data very
seriously and this issue is making me lose sleep.
|||If I may add my 2 cents...
Microsoft does not generally give ANY directives, the world is so varied the
answer to almost any question is 'depends'...
You do not have to do any design on the database structure - There is no MS
directive, but to normalize the database is 1. A Best Practice 2. Highly
recommended
as is mirroring the transaction logs IF you need up to the minute recovery
without loss of data.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"SQLDBA_723" <SQLDBA_723@.discussions.microsoft.com> wrote in message
news:7C2CD527-1514-4F9B-90E9-0E118EB2C017@.microsoft.com...
> I would like to know if Microsoft publishes SQL Server standards which
direct or mandate that the database Transaction Log be created on a Mirrored
set. Some no-technical management people where I work are stating that
placing Transaction Logs on a Mirrored set is a Microsoft standard. I am a
DBA and have worked with SQL Server since version 4.2 and all versions since
and this is news to me. I understand the performance benefits of placing
the Trans. Log on the Mirror BUT in our environment, the operating system is
also on the Mirror and we have junior level engineers managing the systems
who know nothing about SQL Server. Therefore, I feel placing the
Transaction Log on the Mirror in our environment would create unneccessary
risks; especially since we are having no performance problems.
> PLEASE!!! I would appreciate the response of anyone who can tell me if
placing the Trans. Log on a Mirror is a Microsoft Standard or not. I have
always understood Microsoft's statements regarding Mirroring the Trans. Log
to be merely suggestions or recommendations not a directive. I do not want
upper management sold on accepting what I see as a risk by non-technical
people who are stating that placing the database Transaction Log on a
Mirrored set is a standard that we have to follow.
> Sorry for being so lengthy but I am take my job and protecting data very
seriously and this issue is making me lose sleep.

Installation standards

I would like to know if Microsoft publishes SQL Server standards which direct or mandate that the database Transaction Log be created on a Mirrored set. Some no-technical management people where I work are stating that placing Transaction Logs on a Mirrored set is a Microsoft standard. I am a DBA and have worked with SQL Server since version 4.2 and all versions since and this is news to me. I understand the performance benefits of placing the Trans. Log on the Mirror BUT in our environment, the operating system is also on the Mirror and we have junior level engineers managing the systems who know nothing about SQL Server. Therefore, I feel placing the Transaction Log on the Mirror in our environment would create unneccessary risks; especially since we are having no performance problems.
PLEASE!!! I would appreciate the response of anyone who can tell me if placing the Trans. Log on a Mirror is a Microsoft Standard or not. I have always understood Microsoft's statements regarding Mirroring the Trans. Log to be merely suggestions or recommendations not a directive. I do not want upper management sold on accepting what I see as a risk by non-technical people who are stating that placing the database Transaction Log on a Mirrored set is a standard that we have to follow.
Sorry for being so lengthy but I am take my job and protecting data very seriously and this issue is making me lose sleep.It seems like you understand the implications for this, so the short answer is: "No, this is not a
directive, only a recommendation".
One thing, though: If the part where the data is crashes in any way, you definitely want to get to
your tlog files, as it allow you to backup the log using NO_TRUNCATE. Placing the log with the data
is increased risk exposure in this regard.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SQLDBA_723" <SQLDBA_723@.discussions.microsoft.com> wrote in message
news:7C2CD527-1514-4F9B-90E9-0E118EB2C017@.microsoft.com...
> I would like to know if Microsoft publishes SQL Server standards which direct or mandate that the
database Transaction Log be created on a Mirrored set. Some no-technical management people where I
work are stating that placing Transaction Logs on a Mirrored set is a Microsoft standard. I am a
DBA and have worked with SQL Server since version 4.2 and all versions since and this is news to me.
I understand the performance benefits of placing the Trans. Log on the Mirror BUT in our
environment, the operating system is also on the Mirror and we have junior level engineers managing
the systems who know nothing about SQL Server. Therefore, I feel placing the Transaction Log on the
Mirror in our environment would create unneccessary risks; especially since we are having no
performance problems.
> PLEASE!!! I would appreciate the response of anyone who can tell me if placing the Trans. Log on
a Mirror is a Microsoft Standard or not. I have always understood Microsoft's statements regarding
Mirroring the Trans. Log to be merely suggestions or recommendations not a directive. I do not want
upper management sold on accepting what I see as a risk by non-technical people who are stating that
placing the database Transaction Log on a Mirrored set is a standard that we have to follow.
> Sorry for being so lengthy but I am take my job and protecting data very seriously and this issue
is making me lose sleep.|||Hi,
>>that placing Transaction Logs on a Mirrored set is a Microsoft standard.
Iam not speaking for Microsoft here but just letting you know what
information I have with respect to your concern.Iam not aware about any such
"standard" that Microsoft, has w.r.t SQL2000 setup.All the important things
that you have to take care before SQL2000 setup like required space, MDAC
level,IE level etc are mentioned in the readme.txt file or "help" topics
that accompany the setup CD.Any performance enhancement other than those are
solely left as an exercise to the person who is installing, based on his/her
experience with the same.The PSS team reports to the SQLServer team the
various issues that customers face regularly which often result in poor
server performance, disaster recovery etc.Based on those, Microsoft
occassionally publishes whitepapers for the benefit of SQLServer admins and
users.Here are some:
'SQL Server 2000 Operations Guide'
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops0.mspx
'High Availability Resources'
http://www.microsoft.com/sql/techinfo/administration/2000/availability.asp
>> I am take my job and protecting data very seriously and this issue is
making me lose sleep.
Not that it's any of my business, but I couldn't help asking it.What is your
role at this workplace? Based on the above statement, it seems you are a
DBA.If so, why should you let those 'junior level engineers' manage the
SQLServer systems?
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"SQLDBA_723" <SQLDBA_723@.discussions.microsoft.com> wrote in message
news:7C2CD527-1514-4F9B-90E9-0E118EB2C017@.microsoft.com...
> I would like to know if Microsoft publishes SQL Server standards which
direct or mandate that the database Transaction Log be created on a Mirrored
set. Some no-technical management people where I work are stating that
placing Transaction Logs on a Mirrored set is a Microsoft standard. I am a
DBA and have worked with SQL Server since version 4.2 and all versions since
and this is news to me. I understand the performance benefits of placing
the Trans. Log on the Mirror BUT in our environment, the operating system is
also on the Mirror and we have junior level engineers managing the systems
who know nothing about SQL Server. Therefore, I feel placing the
Transaction Log on the Mirror in our environment would create unneccessary
risks; especially since we are having no performance problems.
> PLEASE!!! I would appreciate the response of anyone who can tell me if
placing the Trans. Log on a Mirror is a Microsoft Standard or not. I have
always understood Microsoft's statements regarding Mirroring the Trans. Log
to be merely suggestions or recommendations not a directive. I do not want
upper management sold on accepting what I see as a risk by non-technical
people who are stating that placing the database Transaction Log on a
Mirrored set is a standard that we have to follow.
> Sorry for being so lengthy but I am take my job and protecting data very
seriously and this issue is making me lose sleep.|||If I may add my 2 cents...
Microsoft does not generally give ANY directives, the world is so varied the
answer to almost any question is 'depends'...
You do not have to do any design on the database structure - There is no MS
directive, but to normalize the database is 1. A Best Practice 2. Highly
recommended
as is mirroring the transaction logs IF you need up to the minute recovery
without loss of data.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"SQLDBA_723" <SQLDBA_723@.discussions.microsoft.com> wrote in message
news:7C2CD527-1514-4F9B-90E9-0E118EB2C017@.microsoft.com...
> I would like to know if Microsoft publishes SQL Server standards which
direct or mandate that the database Transaction Log be created on a Mirrored
set. Some no-technical management people where I work are stating that
placing Transaction Logs on a Mirrored set is a Microsoft standard. I am a
DBA and have worked with SQL Server since version 4.2 and all versions since
and this is news to me. I understand the performance benefits of placing
the Trans. Log on the Mirror BUT in our environment, the operating system is
also on the Mirror and we have junior level engineers managing the systems
who know nothing about SQL Server. Therefore, I feel placing the
Transaction Log on the Mirror in our environment would create unneccessary
risks; especially since we are having no performance problems.
> PLEASE!!! I would appreciate the response of anyone who can tell me if
placing the Trans. Log on a Mirror is a Microsoft Standard or not. I have
always understood Microsoft's statements regarding Mirroring the Trans. Log
to be merely suggestions or recommendations not a directive. I do not want
upper management sold on accepting what I see as a risk by non-technical
people who are stating that placing the database Transaction Log on a
Mirrored set is a standard that we have to follow.
> Sorry for being so lengthy but I am take my job and protecting data very
seriously and this issue is making me lose sleep.

Installation standards

I would like to know if Microsoft publishes SQL Server standards which direc
t or mandate that the database Transaction Log be created on a Mirrored set.
Some no-technical management people where I work are stating that placing
Transaction Logs on a Mirro
red set is a Microsoft standard. I am a DBA and have worked with SQL Server
since version 4.2 and all versions since and this is news to me. I underst
and the performance benefits of placing the Trans. Log on the Mirror BUT in
our environment, the operat
ing system is also on the Mirror and we have junior level engineers managing
the systems who know nothing about SQL Server. Therefore, I feel placing t
he Transaction Log on the Mirror in our environment would create unneccessar
y risks; especially since w
e are having no performance problems.
PLEASE!!! I would appreciate the response of anyone who can tell me if plac
ing the Trans. Log on a Mirror is a Microsoft Standard or not. I have alway
s understood Microsoft's statements regarding Mirroring the Trans. Log to be
merely suggestions or reco
mmendations not a directive. I do not want upper management sold on accepti
ng what I see as a risk by non-technical people who are stating that placing
the database Transaction Log on a Mirrored set is a standard that we have t
o follow.
Sorry for being so lengthy but I am take my job and protecting data very ser
iously and this issue is making me lose sleep.It seems like you understand the implications for this, so the short answer
is: "No, this is not a
directive, only a recommendation".
One thing, though: If the part where the data is crashes in any way, you def
initely want to get to
your tlog files, as it allow you to backup the log using NO_TRUNCATE. Placin
g the log with the data
is increased risk exposure in this regard.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"SQLDBA_723" <SQLDBA_723@.discussions.microsoft.com> wrote in message
news:7C2CD527-1514-4F9B-90E9-0E118EB2C017@.microsoft.com...
> I would like to know if Microsoft publishes SQL Server standards which direct or m
andate that the
database Transaction Log be created on a Mirrored set. Some no-technical ma
nagement people where I
work are stating that placing Transaction Logs on a Mirrored set is a Micros
oft standard. I am a
DBA and have worked with SQL Server since version 4.2 and all versions since
and this is news to me.
I understand the performance benefits of placing the Trans. Log on the Mirro
r BUT in our
environment, the operating system is also on the Mirror and we have junior l
evel engineers managing
the systems who know nothing about SQL Server. Therefore, I feel placing th
e Transaction Log on the
Mirror in our environment would create unneccessary risks; especially since
we are having no
performance problems.
> PLEASE!!! I would appreciate the response of anyone who can tell me if placing th
e Trans. Log on
a Mirror is a Microsoft Standard or not. I have always understood Microsoft
's statements regarding
Mirroring the Trans. Log to be merely suggestions or recommendations not a d
irective. I do not want
upper management sold on accepting what I see as a risk by non-technical peo
ple who are stating that
placing the database Transaction Log on a Mirrored set is a standard that we have to follow.

> Sorry for being so lengthy but I am take my job and protecting data very seriously
and this issue
is making me lose sleep.|||Hi,

Iam not speaking for Microsoft here but just letting you know what
information I have with respect to your concern.Iam not aware about any such
"standard" that Microsoft, has w.r.t SQL2000 setup.All the important things
that you have to take care before SQL2000 setup like required space, MDAC
level,IE level etc are mentioned in the readme.txt file or "help" topics
that accompany the setup CD.Any performance enhancement other than those are
solely left as an exercise to the person who is installing, based on his/her
experience with the same.The PSS team reports to the SQLServer team the
various issues that customers face regularly which often result in poor
server performance, disaster recovery etc.Based on those, Microsoft
occassionally publishes whitepapers for the benefit of SQLServer admins and
users.Here are some:
'SQL Server 2000 Operations Guide'
http://www.microsoft.com/technet/pr...in/sqlops0.mspx
'High Availability Resources'
http://www.microsoft.com/sql/techin...vailability.asp
[vbcol=seagreen]
making me lose sleep.
Not that it's any of my business, but I couldn't help asking it.What is your
role at this workplace? Based on the above statement, it seems you are a
DBA.If so, why should you let those 'junior level engineers' manage the
SQLServer systems?
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"SQLDBA_723" <SQLDBA_723@.discussions.microsoft.com> wrote in message
news:7C2CD527-1514-4F9B-90E9-0E118EB2C017@.microsoft.com...[vbcol=seagreen]
> I would like to know if Microsoft publishes SQL Server standards which
direct or mandate that the database Transaction Log be created on a Mirrored
set. Some no-technical management people where I work are stating that
placing Transaction Logs on a Mirrored set is a Microsoft standard. I am a
DBA and have worked with SQL Server since version 4.2 and all versions since
and this is news to me. I understand the performance benefits of placing
the Trans. Log on the Mirror BUT in our environment, the operating system is
also on the Mirror and we have junior level engineers managing the systems
who know nothing about SQL Server. Therefore, I feel placing the
Transaction Log on the Mirror in our environment would create unneccessary
risks; especially since we are having no performance problems.
> PLEASE!!! I would appreciate the response of anyone who can tell me if
placing the Trans. Log on a Mirror is a Microsoft Standard or not. I have
always understood Microsoft's statements regarding Mirroring the Trans. Log
to be merely suggestions or recommendations not a directive. I do not want
upper management sold on accepting what I see as a risk by non-technical
people who are stating that placing the database Transaction Log on a
Mirrored set is a standard that we have to follow.
> Sorry for being so lengthy but I am take my job and protecting data very
seriously and this issue is making me lose sleep.|||If I may add my 2 cents...
Microsoft does not generally give ANY directives, the world is so varied the
answer to almost any question is 'depends'...
You do not have to do any design on the database structure - There is no MS
directive, but to normalize the database is 1. A Best Practice 2. Highly
recommended
as is mirroring the transaction logs IF you need up to the minute recovery
without loss of data.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"SQLDBA_723" <SQLDBA_723@.discussions.microsoft.com> wrote in message
news:7C2CD527-1514-4F9B-90E9-0E118EB2C017@.microsoft.com...
> I would like to know if Microsoft publishes SQL Server standards which
direct or mandate that the database Transaction Log be created on a Mirrored
set. Some no-technical management people where I work are stating that
placing Transaction Logs on a Mirrored set is a Microsoft standard. I am a
DBA and have worked with SQL Server since version 4.2 and all versions since
and this is news to me. I understand the performance benefits of placing
the Trans. Log on the Mirror BUT in our environment, the operating system is
also on the Mirror and we have junior level engineers managing the systems
who know nothing about SQL Server. Therefore, I feel placing the
Transaction Log on the Mirror in our environment would create unneccessary
risks; especially since we are having no performance problems.
> PLEASE!!! I would appreciate the response of anyone who can tell me if
placing the Trans. Log on a Mirror is a Microsoft Standard or not. I have
always understood Microsoft's statements regarding Mirroring the Trans. Log
to be merely suggestions or recommendations not a directive. I do not want
upper management sold on accepting what I see as a risk by non-technical
people who are stating that placing the database Transaction Log on a
Mirrored set is a standard that we have to follow.
> Sorry for being so lengthy but I am take my job and protecting data very
seriously and this issue is making me lose sleep.

Installation is not possible on W2003

I have tried to install SQL 2000 standard on W2003 Web edition. When I click
on "Install Database Server" (Installation pane) a small icon "Created with
DemoShield" appears for few second and than disappears. Then nothing
happend .. :o(
All web services (IIS, FTP, NNTP .) were stopped before installation.
Any tip will be greatly appreciated
VladIf I remember correctly, you cannot install ANY apps on Win2k3 Web =
Edition. This limit is imposed by the OS.
--=20
Keith
"Vlad" <volodimir@.get2net.dk> wrote in message =
news:O9$gL5CDEHA.2308@.tk2msftngp13.phx.gbl...
> I have tried to install SQL 2000 standard on W2003 Web edition. When I =
click
> on "Install Database Server" (Installation pane) a small icon "Created =
with
> DemoShield" appears for few second and than disappears. Then nothing
> happend .. :o(
>=20
> All web services (IIS, FTP, NNTP .) were stopped before installation.
>=20
> Any tip will be greatly appreciated
>=20
> Vlad
>=20
>=20
>=20
>|||You can install MSDE 2000 on the Web Edition but not SQL Server 2000
Standard or Enterprise.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Good to know. Thanks.
--=20
Keith
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message =
news:DsvgOiGDEHA.660@.cpmsftngxa06.phx.gbl...
> You can install MSDE 2000 on the Web Edition but not SQL Server 2000=20
> Standard or Enterprise.
>=20
> Rand
> This posting is provided "as is" with no warranties and confers no =
rights.
>

Installation is not possible on W2003

I have tried to install SQL 2000 standard on W2003 Web edition. When I click
on "Install Database Server" (Installation pane) a small icon "Created with
DemoShield" appears for few second and than disappears. Then nothing
happens .. :o(
All web services (IIS, FTP, NNTP .) were stopped before installation.
Any tip will be greatly appreciated
VladIf I remember correctly, you cannot install ANY apps on Win2k3 Web =
Edition. This limit is imposed by the OS.
--=20
Keith
"Vlad" <volodimir@.get2net.dk> wrote in message =
news:OY%23$L5CDEHA.2308@.tk2msftngp13.phx.gbl...
> I have tried to install SQL 2000 standard on W2003 Web edition. When I =
click
> on "Install Database Server" (Installation pane) a small icon "Created =
with
> DemoShield" appears for few second and than disappears. Then nothing
> happens .. :o(
>=20
> All web services (IIS, FTP, NNTP .) were stopped before installation.
>=20
> Any tip will be greatly appreciated
>=20
> Vlad
>=20
>