There is a recent news article that indicates that Microsoft has "warned"
its customers about SQL Server 2000 (version not identified) not being
compatible with the XP SP 2.
I went to the MS website and searched everything I could find on the RTM
version of SP2. I found no such warning ... I found "issues" that could
come up if the Firewall is enabled and how to modify the settings so that
you could get to the SQL Server 2000 if there were problems.
I have installed MSDE on an XP Pro machine with all SPs and fixes up to but
not including SP2 and wanted to make sure that I didn't do anything to screw
up our current development processes ... we're in the middle of a large dev
project and didn't want to bring everything to a grinding halt.
Yes, we will install SP2 and test to make sure that our .NET apps will work
under SP2 but I want to do it in a "controlled manner" ... not an
inadvertent shutdown in the middle.
Anyone know of any issues, other than the Firewall, that makes SQL Server
2000 incompatible with XP SP2?
Thanks...
RonHi Ron,
Thanks for using MSDN Managed Newsgroup!
Here are some links showing why it is warned using SQL Server / MSDE with
XP SP2
"some programs may seem not to work. By default, Windows Firewall is
enabled and blocks unsolicited connections to your computer"
Some programs seem to stop working after you install Windows XP Service
Pack 2
http://support.microsoft.com/default.aspx?kbid=842242
--
"After you install Microsoft Windows XP Service Pack 2 on a computer that
is configured as a distributor, if you try to synchronize data from a
subscriber that is configured on a remote computer, you may notice that the
changes that are made in the subscriber database are not updated to the
publisher database."
BUG: The changes in a remote subscriber are not updated to the publisher
for a queued updating replication that uses Message Queuing on a
computer that is running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839278
--
"You may not be able to connect to an instance of SQL Server, and you may
receive one of the following error messages.
[Named Pipes]SQL Server does not exist or access denied.
Unable to connect to server <SQL Server instance name>"
You may not be able to connect to an instance of SQL Server that is
configured to use the Named Pipes server network library on a computer
that is running Windows XP Service Pack 2
http://support.microsoft.com/?id=839269
--
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1"
You may receive a 7391 error message in SQL Server 2000 when you run a
distributed transaction against a linked server after you install Microsoft
Windows XP Service Pack 2
http://support.microsoft.com/?id=839279
--
" the SQL debugging feature in Microsoft Visual Studio .NET 2003 (Visual
Studio .NET) does not work. When you try to debug a SQL Server stored
procedure by using the Step Into Stored Procedure option in the Server
Explorer pane, you may receive the following error message:
Cannot debug stored procedures because the SQL Server database is not setup
correctly or user does not have permission to execute master.sp_sdidebug.
Run SQL Server setup or contact database administrator."
BUG: SQL debugging does not work in Visual Studio .NET after you install
Windows XP Service Pack 2
http://support.microsoft.com/?id=839280
--
"When you install Microsoft SQL Server 2000 or Microsoft SQL Server Desktop
Engine (also known as MSDE 2000) on a computer that is running Microsoft
Windows XP Service Pack 2 (SP2), a message is logged in the application
event log. The message states that the instance of SQL Server or the
instance of MSDE is vulnerable to virus attacks."
A message stating that an instance of SQL Server is vulnerable to virus
attacks is logged in the application event log when you install SQL Server
2000 or MSDE 2000 on a computer that is running Windows XP Service Pack 2
http://support.microsoft.com/?id=841375
--
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1 "
You may receive a 7391 error message in SQLOLEDB when you run a distributed
transaction against a linked server after you install Microsoft Windows XP
Service Pack 2
http://support.microsoft.com/?id=873160
--
Here is another very useful link for you about how to troubleshooting
Windows Firewall settings in Windows XP SP2
Troubleshooting Windows Firewall settings in Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=875357
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hi Ron,
Additionally, I would like to provide five HOW-TO articiles for
configuration SQL Server with XP SP2.
How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/?id=841249
How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/?id=841251
How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server
2000
http://support.microsoft.com/?id=841252
How to enable SQL Server 2000 Reporting Services on Windows XP Service Pack
2
http://support.microsoft.com/?id=841253
How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=842005
How to enable SQL Server 2000 Analysis Services and OLAP Services on
computers that are running Windows XP SP2
http://support.microsoft.com/?id=841256
How to use a script to programmatically open ports for SQL Server to use on
systems that are running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839980
Thank you for your patience and cooperation again. If you have any
questions or concerns, don't hesitate to let me know. We are here to be of
assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thank you very much for both replies. Your replies were both thorough and
very helpful.
I will back the machines up and begin installing SP2 on Saturday.
Hopefully, I will be able to report successful and uneventful installations
on Monday.
Again, many thanks...
Ron
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
> Hi Ron,
> Additionally, I would like to provide five HOW-TO articiles for
> configuration SQL Server with XP SP2.
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> How to enable SQL Server connectivity on Windows XP Service Pack 2
> http://support.microsoft.com/?id=841251
> How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server
> 2000
> http://support.microsoft.com/?id=841252
> How to enable SQL Server 2000 Reporting Services on Windows XP Service
Pack
> 2
> http://support.microsoft.com/?id=841253
> How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=842005
> How to enable SQL Server 2000 Analysis Services and OLAP Services on
> computers that are running Windows XP SP2
> http://support.microsoft.com/?id=841256
> How to use a script to programmatically open ports for SQL Server to use
on
> systems that are running Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839980
> Thank you for your patience and cooperation again. If you have any
> questions or concerns, don't hesitate to let me know. We are here to be of
> assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||If you use Visual Studio.Net to debug SQL Stored Proceedures you'll
want to wait. More details are at
http://support.microsoft.com/?kbid=839280. If anyone knows of a way
around this problem, please let me know.
Ken Kimball [kkimball@.gmail.com]
"Ron Fluegge" <rmflugge@.swbell.net> wrote in message news:<#i24S0HgEHA.904@.TK2MSFTNGP09.phx.
gbl>...
> There is a recent news article that indicates that Microsoft has "warned"
> its customers about SQL Server 2000 (version not identified) not being
> compatible with the XP SP 2.
> I went to the MS website and searched everything I could find on the RTM
> version of SP2. I found no such warning ... I found "issues" that could
> come up if the Firewall is enabled and how to modify the settings so that
> you could get to the SQL Server 2000 if there were problems.
> I have installed MSDE on an XP Pro machine with all SPs and fixes up to bu
t
> not including SP2 and wanted to make sure that I didn't do anything to scr
ew
> up our current development processes ... we're in the middle of a large de
v
> project and didn't want to bring everything to a grinding halt.
> Yes, we will install SP2 and test to make sure that our .NET apps will wor
k
> under SP2 but I want to do it in a "controlled manner" ... not an
> inadvertent shutdown in the middle.
> Anyone know of any issues, other than the Firewall, that makes SQL Server
> 2000 incompatible with XP SP2?
> Thanks...
> Ron|||Ken,
Yes, I was aware of that problem. I do use VS 2003 to develop apps but do
not use SQL Stored Procedures (for a number of reasons specific to our
apps).
I was very surprised to find the number of "issues" related to SQL Server
2000 given that is the current release of MS's SQL Server -- especially
since there is nothing to indicate that patches or fixes are forthcoming.
On the same XP Pro machine, I'm also running Oracle 9i and I'm hoping that
it doesn't come to a crashing halt as well. (These are used for
"development" and not for production databases)
Ron
"Ken Kimball" <kkimball@.gmail.com> wrote in message
news:466a0cb4.0408130512.4468a03a@.posting.google.com...
> If you use Visual Studio.Net to debug SQL Stored Proceedures you'll
> want to wait. More details are at
> http://support.microsoft.com/?kbid=839280. If anyone knows of a way
> around this problem, please let me know.
> Ken Kimball [kkimball@.gmail.com]
> "Ron Fluegge" <rmflugge@.swbell.net> wrote in message
news:<#i24S0HgEHA.904@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
"warned"[vbcol=seagreen]
that[vbcol=seagreen]
but[vbcol=seagreen]
screw[vbcol=seagreen]
dev[vbcol=seagreen]
work[vbcol=seagreen]
Server[vbcol=seagreen]|||You might also check out:
Finally, you should absolutely watch and learn from the webcast titled MSDN
Webcast: SQL Server and Windows XP SP2 - Level 300 available at
S" target="_blank">http://msevents.microsoft.com/CUI/E...e=en-U
S
I found it to be very helpful.
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Ron Fluegge" <rmflugge@.swbell.net> wrote in message
news:e9BEMnPgEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Thank you very much for both replies. Your replies were both thorough and
> very helpful.
> I will back the machines up and begin installing SP2 on Saturday.
> Hopefully, I will be able to report successful and uneventful
installations
> on Monday.
> Again, many thanks...
> Ron
> ""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in mes
sage
> news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
Server[vbcol=seagreen]
> Pack
> on
of[vbcol=seagreen]
rights.[vbcol=seagreen]
>|||Brian,
Will do ... THANKS VERY MUCH!!!
Ron
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:OOHq06UgEHA.1764@.TK2MSFTNGP10.phx.gbl...
> You might also check out:
> Finally, you should absolutely watch and learn from the webcast titled
'MSDN
> Webcast: SQL Server and Windows XP SP2 - Level 300 ' available at
>
http://msevents.microsoft.com/CUI/E...0&Culture=en-USagreen">
>
> I found it to be very helpful.
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Ron Fluegge" <rmflugge@.swbell.net> wrote in message
> news:e9BEMnPgEHA.1972@.TK2MSFTNGP09.phx.gbl...
and[vbcol=seagreen]
> installations
message[vbcol=seagreen]
Server[vbcol=seagreen]
> Server
2[vbcol=seagreen]
use[vbcol=seagreen]
be[vbcol=seagreen]
> of
> rights.
>|||Hi Ron,
If you encounter any questions or concerns when upgrading to Windows XP
Service Pack 2, please feel free to reply here or make a new thread. We
would love to make a follow up until that issue is completely resolved.
Good Luck!
Thank you for your patience and cooperation.
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I just finished the upgrade to SP2 ... on this machine I have both SQL
Server 2000 and Oracle 9i as well as VS 2003 -- it's my development machine.
It all went well without a hitch!!!
Everything is up and running without any problems so far software or
hardware-wise. I have a dual AMD MoBo with RAID controllers and it is
having no problems.
So needless to say, I am a happy camper ...
Ron
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:v7ocVFcgEHA.480@.cpmsftngxa06.phx.gbl...
> Hi Ron,
> If you encounter any questions or concerns when upgrading to Windows XP
> Service Pack 2, please feel free to reply here or make a new thread. We
> would love to make a follow up until that issue is completely resolved.
> Good Luck!
> Thank you for your patience and cooperation.
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
2012年3月8日星期四
Any SQL Server 2000 and XP SP2 issues?
There is a recent news article that indicates that Microsoft has "warned"
its customers about SQL Server 2000 (version not identified) not being
compatible with the XP SP 2.
I went to the MS website and searched everything I could find on the RTM
version of SP2. I found no such warning ... I found "issues" that could
come up if the Firewall is enabled and how to modify the settings so that
you could get to the SQL Server 2000 if there were problems.
I have installed MSDE on an XP Pro machine with all SPs and fixes up to but
not including SP2 and wanted to make sure that I didn't do anything to screw
up our current development processes ... we're in the middle of a large dev
project and didn't want to bring everything to a grinding halt.
Yes, we will install SP2 and test to make sure that our .NET apps will work
under SP2 but I want to do it in a "controlled manner" ... not an
inadvertent shutdown in the middle.
Anyone know of any issues, other than the Firewall, that makes SQL Server
2000 incompatible with XP SP2?
Thanks...
RonHi Ron,
Thanks for using MSDN Managed Newsgroup!
Here are some links showing why it is warned using SQL Server / MSDE with
XP SP2
"some programs may seem not to work. By default, Windows Firewall is
enabled and blocks unsolicited connections to your computer"
Some programs seem to stop working after you install Windows XP Service
Pack 2
http://support.microsoft.com/default.aspx?kbid=842242
--
"After you install Microsoft Windows XP Service Pack 2 on a computer that
is configured as a distributor, if you try to synchronize data from a
subscriber that is configured on a remote computer, you may notice that the
changes that are made in the subscriber database are not updated to the
publisher database."
BUG: The changes in a remote subscriber are not updated to the publisher
for a queued updating replication that uses Message Queuing on a
computer that is running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839278
--
"You may not be able to connect to an instance of SQL Server, and you may
receive one of the following error messages.
[Named Pipes]SQL Server does not exist or access denied.
Unable to connect to server <SQL Server instance name>"
You may not be able to connect to an instance of SQL Server that is
configured to use the Named Pipes server network library on a computer
that is running Windows XP Service Pack 2
http://support.microsoft.com/?id=839269
--
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1"
You may receive a 7391 error message in SQL Server 2000 when you run a
distributed transaction against a linked server after you install Microsoft
Windows XP Service Pack 2
http://support.microsoft.com/?id=839279
--
" the SQL debugging feature in Microsoft Visual Studio .NET 2003 (Visual
Studio .NET) does not work. When you try to debug a SQL Server stored
procedure by using the Step Into Stored Procedure option in the Server
Explorer pane, you may receive the following error message:
Cannot debug stored procedures because the SQL Server database is not setup
correctly or user does not have permission to execute master.sp_sdidebug.
Run SQL Server setup or contact database administrator."
BUG: SQL debugging does not work in Visual Studio .NET after you install
Windows XP Service Pack 2
http://support.microsoft.com/?id=839280
--
"When you install Microsoft SQL Server 2000 or Microsoft SQL Server Desktop
Engine (also known as MSDE 2000) on a computer that is running Microsoft
Windows XP Service Pack 2 (SP2), a message is logged in the application
event log. The message states that the instance of SQL Server or the
instance of MSDE is vulnerable to virus attacks."
A message stating that an instance of SQL Server is vulnerable to virus
attacks is logged in the application event log when you install SQL Server
2000 or MSDE 2000 on a computer that is running Windows XP Service Pack 2
http://support.microsoft.com/?id=841375
--
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1 "
You may receive a 7391 error message in SQLOLEDB when you run a distributed
transaction against a linked server after you install Microsoft Windows XP
Service Pack 2
http://support.microsoft.com/?id=873160
--
Here is another very useful link for you about how to troubleshooting
Windows Firewall settings in Windows XP SP2
Troubleshooting Windows Firewall settings in Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=875357
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hi Ron,
Additionally, I would like to provide five HOW-TO articiles for
configuration SQL Server with XP SP2.
How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/?id=841249
How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/?id=841251
How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server
2000
http://support.microsoft.com/?id=841252
How to enable SQL Server 2000 Reporting Services on Windows XP Service Pack
2
http://support.microsoft.com/?id=841253
How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=842005
How to enable SQL Server 2000 Analysis Services and OLAP Services on
computers that are running Windows XP SP2
http://support.microsoft.com/?id=841256
How to use a script to programmatically open ports for SQL Server to use on
systems that are running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839980
Thank you for your patience and cooperation again. If you have any
questions or concerns, don't hesitate to let me know. We are here to be of
assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thank you very much for both replies. Your replies were both thorough and
very helpful.
I will back the machines up and begin installing SP2 on Saturday.
Hopefully, I will be able to report successful and uneventful installations
on Monday.
Again, many thanks...
Ron
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
> Hi Ron,
> Additionally, I would like to provide five HOW-TO articiles for
> configuration SQL Server with XP SP2.
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> How to enable SQL Server connectivity on Windows XP Service Pack 2
> http://support.microsoft.com/?id=841251
> How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server
> 2000
> http://support.microsoft.com/?id=841252
> How to enable SQL Server 2000 Reporting Services on Windows XP Service
Pack
> 2
> http://support.microsoft.com/?id=841253
> How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=842005
> How to enable SQL Server 2000 Analysis Services and OLAP Services on
> computers that are running Windows XP SP2
> http://support.microsoft.com/?id=841256
> How to use a script to programmatically open ports for SQL Server to use
on
> systems that are running Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839980
> Thank you for your patience and cooperation again. If you have any
> questions or concerns, don't hesitate to let me know. We are here to be of
> assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||If you use Visual Studio.Net to debug SQL Stored Proceedures you'll
want to wait. More details are at
http://support.microsoft.com/?kbid=839280. If anyone knows of a way
around this problem, please let me know.
Ken Kimball [kkimball@.gmail.com]
"Ron Fluegge" <rmflugge@.swbell.net> wrote in message news:<#i24S0HgEHA.904@.TK2MSFTNGP09.phx.gbl>...
> There is a recent news article that indicates that Microsoft has "warned"
> its customers about SQL Server 2000 (version not identified) not being
> compatible with the XP SP 2.
> I went to the MS website and searched everything I could find on the RTM
> version of SP2. I found no such warning ... I found "issues" that could
> come up if the Firewall is enabled and how to modify the settings so that
> you could get to the SQL Server 2000 if there were problems.
> I have installed MSDE on an XP Pro machine with all SPs and fixes up to but
> not including SP2 and wanted to make sure that I didn't do anything to screw
> up our current development processes ... we're in the middle of a large dev
> project and didn't want to bring everything to a grinding halt.
> Yes, we will install SP2 and test to make sure that our .NET apps will work
> under SP2 but I want to do it in a "controlled manner" ... not an
> inadvertent shutdown in the middle.
> Anyone know of any issues, other than the Firewall, that makes SQL Server
> 2000 incompatible with XP SP2?
> Thanks...
> Ron|||Ken,
Yes, I was aware of that problem. I do use VS 2003 to develop apps but do
not use SQL Stored Procedures (for a number of reasons specific to our
apps).
I was very surprised to find the number of "issues" related to SQL Server
2000 given that is the current release of MS's SQL Server -- especially
since there is nothing to indicate that patches or fixes are forthcoming.
On the same XP Pro machine, I'm also running Oracle 9i and I'm hoping that
it doesn't come to a crashing halt as well. (These are used for
"development" and not for production databases)
Ron
"Ken Kimball" <kkimball@.gmail.com> wrote in message
news:466a0cb4.0408130512.4468a03a@.posting.google.com...
> If you use Visual Studio.Net to debug SQL Stored Proceedures you'll
> want to wait. More details are at
> http://support.microsoft.com/?kbid=839280. If anyone knows of a way
> around this problem, please let me know.
> Ken Kimball [kkimball@.gmail.com]
> "Ron Fluegge" <rmflugge@.swbell.net> wrote in message
news:<#i24S0HgEHA.904@.TK2MSFTNGP09.phx.gbl>...
> > There is a recent news article that indicates that Microsoft has
"warned"
> > its customers about SQL Server 2000 (version not identified) not being
> > compatible with the XP SP 2.
> >
> > I went to the MS website and searched everything I could find on the RTM
> > version of SP2. I found no such warning ... I found "issues" that could
> > come up if the Firewall is enabled and how to modify the settings so
that
> > you could get to the SQL Server 2000 if there were problems.
> >
> > I have installed MSDE on an XP Pro machine with all SPs and fixes up to
but
> > not including SP2 and wanted to make sure that I didn't do anything to
screw
> > up our current development processes ... we're in the middle of a large
dev
> > project and didn't want to bring everything to a grinding halt.
> >
> > Yes, we will install SP2 and test to make sure that our .NET apps will
work
> > under SP2 but I want to do it in a "controlled manner" ... not an
> > inadvertent shutdown in the middle.
> >
> > Anyone know of any issues, other than the Firewall, that makes SQL
Server
> > 2000 incompatible with XP SP2?
> >
> > Thanks...
> >
> > Ron|||You might also check out:
Finally, you should absolutely watch and learn from the webcast titled ?MSDN
Webcast: SQL Server and Windows XP SP2 - Level 300 ? available at
http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032253410&Culture=en-US
I found it to be very helpful.
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Ron Fluegge" <rmflugge@.swbell.net> wrote in message
news:e9BEMnPgEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Thank you very much for both replies. Your replies were both thorough and
> very helpful.
> I will back the machines up and begin installing SP2 on Saturday.
> Hopefully, I will be able to report successful and uneventful
installations
> on Monday.
> Again, many thanks...
> Ron
> ""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
> news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
> > Hi Ron,
> >
> > Additionally, I would like to provide five HOW-TO articiles for
> > configuration SQL Server with XP SP2.
> >
> > How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> > http://support.microsoft.com/?id=841249
> >
> > How to enable SQL Server connectivity on Windows XP Service Pack 2
> > http://support.microsoft.com/?id=841251
> >
> > How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
Server
> > 2000
> > http://support.microsoft.com/?id=841252
> >
> > How to enable SQL Server 2000 Reporting Services on Windows XP Service
> Pack
> > 2
> > http://support.microsoft.com/?id=841253
> >
> > How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
> > http://support.microsoft.com/default.aspx?kbid=842005
> >
> > How to enable SQL Server 2000 Analysis Services and OLAP Services on
> > computers that are running Windows XP SP2
> > http://support.microsoft.com/?id=841256
> >
> > How to use a script to programmatically open ports for SQL Server to use
> on
> > systems that are running Windows XP Service Pack 2
> > http://support.microsoft.com/default.aspx?kbid=839980
> >
> > Thank you for your patience and cooperation again. If you have any
> > questions or concerns, don't hesitate to let me know. We are here to be
of
> > assistance!
> >
> >
> > Sincerely yours,
> >
> > Mingqing Cheng
> > Microsoft Developer Community Support
> > ---
> > Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> > This posting is provided "as is" with no warranties and confers no
rights.
> > Please reply to newsgroups only, many thanks!
> >
>|||Brian,
Will do ... THANKS VERY MUCH!!!
Ron
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:OOHq06UgEHA.1764@.TK2MSFTNGP10.phx.gbl...
> You might also check out:
> Finally, you should absolutely watch and learn from the webcast titled
'MSDN
> Webcast: SQL Server and Windows XP SP2 - Level 300 ' available at
>
http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032253410&Culture=en-US
>
> I found it to be very helpful.
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Ron Fluegge" <rmflugge@.swbell.net> wrote in message
> news:e9BEMnPgEHA.1972@.TK2MSFTNGP09.phx.gbl...
> > Thank you very much for both replies. Your replies were both thorough
and
> > very helpful.
> >
> > I will back the machines up and begin installing SP2 on Saturday.
> > Hopefully, I will be able to report successful and uneventful
> installations
> > on Monday.
> >
> > Again, many thanks...
> >
> > Ron
> >
> > ""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in
message
> > news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
> > > Hi Ron,
> > >
> > > Additionally, I would like to provide five HOW-TO articiles for
> > > configuration SQL Server with XP SP2.
> > >
> > > How to configure Windows XP Service Pack 2 (SP2) for use with SQL
Server
> > > http://support.microsoft.com/?id=841249
> > >
> > > How to enable SQL Server connectivity on Windows XP Service Pack 2
> > > http://support.microsoft.com/?id=841251
> > >
> > > How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
> Server
> > > 2000
> > > http://support.microsoft.com/?id=841252
> > >
> > > How to enable SQL Server 2000 Reporting Services on Windows XP Service
> > Pack
> > > 2
> > > http://support.microsoft.com/?id=841253
> > >
> > > How to enable the ISAPI component on SQLXML on Windows XP Service Pack
2
> > > http://support.microsoft.com/default.aspx?kbid=842005
> > >
> > > How to enable SQL Server 2000 Analysis Services and OLAP Services on
> > > computers that are running Windows XP SP2
> > > http://support.microsoft.com/?id=841256
> > >
> > > How to use a script to programmatically open ports for SQL Server to
use
> > on
> > > systems that are running Windows XP Service Pack 2
> > > http://support.microsoft.com/default.aspx?kbid=839980
> > >
> > > Thank you for your patience and cooperation again. If you have any
> > > questions or concerns, don't hesitate to let me know. We are here to
be
> of
> > > assistance!
> > >
> > >
> > > Sincerely yours,
> > >
> > > Mingqing Cheng
> > > Microsoft Developer Community Support
> > > ---
> > > Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> > > This posting is provided "as is" with no warranties and confers no
> rights.
> > > Please reply to newsgroups only, many thanks!
> > >
> >
> >
>|||Hi Ron,
If you encounter any questions or concerns when upgrading to Windows XP
Service Pack 2, please feel free to reply here or make a new thread. We
would love to make a follow up until that issue is completely resolved.
Good Luck!
Thank you for your patience and cooperation.
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I just finished the upgrade to SP2 ... on this machine I have both SQL
Server 2000 and Oracle 9i as well as VS 2003 -- it's my development machine.
It all went well without a hitch!!!
Everything is up and running without any problems so far software or
hardware-wise. I have a dual AMD MoBo with RAID controllers and it is
having no problems.
So needless to say, I am a happy camper ...
Ron
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v7ocVFcgEHA.480@.cpmsftngxa06.phx.gbl...
> Hi Ron,
> If you encounter any questions or concerns when upgrading to Windows XP
> Service Pack 2, please feel free to reply here or make a new thread. We
> would love to make a follow up until that issue is completely resolved.
> Good Luck!
> Thank you for your patience and cooperation.
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
its customers about SQL Server 2000 (version not identified) not being
compatible with the XP SP 2.
I went to the MS website and searched everything I could find on the RTM
version of SP2. I found no such warning ... I found "issues" that could
come up if the Firewall is enabled and how to modify the settings so that
you could get to the SQL Server 2000 if there were problems.
I have installed MSDE on an XP Pro machine with all SPs and fixes up to but
not including SP2 and wanted to make sure that I didn't do anything to screw
up our current development processes ... we're in the middle of a large dev
project and didn't want to bring everything to a grinding halt.
Yes, we will install SP2 and test to make sure that our .NET apps will work
under SP2 but I want to do it in a "controlled manner" ... not an
inadvertent shutdown in the middle.
Anyone know of any issues, other than the Firewall, that makes SQL Server
2000 incompatible with XP SP2?
Thanks...
RonHi Ron,
Thanks for using MSDN Managed Newsgroup!
Here are some links showing why it is warned using SQL Server / MSDE with
XP SP2
"some programs may seem not to work. By default, Windows Firewall is
enabled and blocks unsolicited connections to your computer"
Some programs seem to stop working after you install Windows XP Service
Pack 2
http://support.microsoft.com/default.aspx?kbid=842242
--
"After you install Microsoft Windows XP Service Pack 2 on a computer that
is configured as a distributor, if you try to synchronize data from a
subscriber that is configured on a remote computer, you may notice that the
changes that are made in the subscriber database are not updated to the
publisher database."
BUG: The changes in a remote subscriber are not updated to the publisher
for a queued updating replication that uses Message Queuing on a
computer that is running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839278
--
"You may not be able to connect to an instance of SQL Server, and you may
receive one of the following error messages.
[Named Pipes]SQL Server does not exist or access denied.
Unable to connect to server <SQL Server instance name>"
You may not be able to connect to an instance of SQL Server that is
configured to use the Named Pipes server network library on a computer
that is running Windows XP Service Pack 2
http://support.microsoft.com/?id=839269
--
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1"
You may receive a 7391 error message in SQL Server 2000 when you run a
distributed transaction against a linked server after you install Microsoft
Windows XP Service Pack 2
http://support.microsoft.com/?id=839279
--
" the SQL debugging feature in Microsoft Visual Studio .NET 2003 (Visual
Studio .NET) does not work. When you try to debug a SQL Server stored
procedure by using the Step Into Stored Procedure option in the Server
Explorer pane, you may receive the following error message:
Cannot debug stored procedures because the SQL Server database is not setup
correctly or user does not have permission to execute master.sp_sdidebug.
Run SQL Server setup or contact database administrator."
BUG: SQL debugging does not work in Visual Studio .NET after you install
Windows XP Service Pack 2
http://support.microsoft.com/?id=839280
--
"When you install Microsoft SQL Server 2000 or Microsoft SQL Server Desktop
Engine (also known as MSDE 2000) on a computer that is running Microsoft
Windows XP Service Pack 2 (SP2), a message is logged in the application
event log. The message states that the instance of SQL Server or the
instance of MSDE is vulnerable to virus attacks."
A message stating that an instance of SQL Server is vulnerable to virus
attacks is logged in the application event log when you install SQL Server
2000 or MSDE 2000 on a computer that is running Windows XP Service Pack 2
http://support.microsoft.com/?id=841375
--
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1 "
You may receive a 7391 error message in SQLOLEDB when you run a distributed
transaction against a linked server after you install Microsoft Windows XP
Service Pack 2
http://support.microsoft.com/?id=873160
--
Here is another very useful link for you about how to troubleshooting
Windows Firewall settings in Windows XP SP2
Troubleshooting Windows Firewall settings in Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=875357
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Hi Ron,
Additionally, I would like to provide five HOW-TO articiles for
configuration SQL Server with XP SP2.
How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/?id=841249
How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/?id=841251
How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server
2000
http://support.microsoft.com/?id=841252
How to enable SQL Server 2000 Reporting Services on Windows XP Service Pack
2
http://support.microsoft.com/?id=841253
How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=842005
How to enable SQL Server 2000 Analysis Services and OLAP Services on
computers that are running Windows XP SP2
http://support.microsoft.com/?id=841256
How to use a script to programmatically open ports for SQL Server to use on
systems that are running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839980
Thank you for your patience and cooperation again. If you have any
questions or concerns, don't hesitate to let me know. We are here to be of
assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thank you very much for both replies. Your replies were both thorough and
very helpful.
I will back the machines up and begin installing SP2 on Saturday.
Hopefully, I will be able to report successful and uneventful installations
on Monday.
Again, many thanks...
Ron
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
> Hi Ron,
> Additionally, I would like to provide five HOW-TO articiles for
> configuration SQL Server with XP SP2.
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> How to enable SQL Server connectivity on Windows XP Service Pack 2
> http://support.microsoft.com/?id=841251
> How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server
> 2000
> http://support.microsoft.com/?id=841252
> How to enable SQL Server 2000 Reporting Services on Windows XP Service
Pack
> 2
> http://support.microsoft.com/?id=841253
> How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=842005
> How to enable SQL Server 2000 Analysis Services and OLAP Services on
> computers that are running Windows XP SP2
> http://support.microsoft.com/?id=841256
> How to use a script to programmatically open ports for SQL Server to use
on
> systems that are running Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839980
> Thank you for your patience and cooperation again. If you have any
> questions or concerns, don't hesitate to let me know. We are here to be of
> assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||If you use Visual Studio.Net to debug SQL Stored Proceedures you'll
want to wait. More details are at
http://support.microsoft.com/?kbid=839280. If anyone knows of a way
around this problem, please let me know.
Ken Kimball [kkimball@.gmail.com]
"Ron Fluegge" <rmflugge@.swbell.net> wrote in message news:<#i24S0HgEHA.904@.TK2MSFTNGP09.phx.gbl>...
> There is a recent news article that indicates that Microsoft has "warned"
> its customers about SQL Server 2000 (version not identified) not being
> compatible with the XP SP 2.
> I went to the MS website and searched everything I could find on the RTM
> version of SP2. I found no such warning ... I found "issues" that could
> come up if the Firewall is enabled and how to modify the settings so that
> you could get to the SQL Server 2000 if there were problems.
> I have installed MSDE on an XP Pro machine with all SPs and fixes up to but
> not including SP2 and wanted to make sure that I didn't do anything to screw
> up our current development processes ... we're in the middle of a large dev
> project and didn't want to bring everything to a grinding halt.
> Yes, we will install SP2 and test to make sure that our .NET apps will work
> under SP2 but I want to do it in a "controlled manner" ... not an
> inadvertent shutdown in the middle.
> Anyone know of any issues, other than the Firewall, that makes SQL Server
> 2000 incompatible with XP SP2?
> Thanks...
> Ron|||Ken,
Yes, I was aware of that problem. I do use VS 2003 to develop apps but do
not use SQL Stored Procedures (for a number of reasons specific to our
apps).
I was very surprised to find the number of "issues" related to SQL Server
2000 given that is the current release of MS's SQL Server -- especially
since there is nothing to indicate that patches or fixes are forthcoming.
On the same XP Pro machine, I'm also running Oracle 9i and I'm hoping that
it doesn't come to a crashing halt as well. (These are used for
"development" and not for production databases)
Ron
"Ken Kimball" <kkimball@.gmail.com> wrote in message
news:466a0cb4.0408130512.4468a03a@.posting.google.com...
> If you use Visual Studio.Net to debug SQL Stored Proceedures you'll
> want to wait. More details are at
> http://support.microsoft.com/?kbid=839280. If anyone knows of a way
> around this problem, please let me know.
> Ken Kimball [kkimball@.gmail.com]
> "Ron Fluegge" <rmflugge@.swbell.net> wrote in message
news:<#i24S0HgEHA.904@.TK2MSFTNGP09.phx.gbl>...
> > There is a recent news article that indicates that Microsoft has
"warned"
> > its customers about SQL Server 2000 (version not identified) not being
> > compatible with the XP SP 2.
> >
> > I went to the MS website and searched everything I could find on the RTM
> > version of SP2. I found no such warning ... I found "issues" that could
> > come up if the Firewall is enabled and how to modify the settings so
that
> > you could get to the SQL Server 2000 if there were problems.
> >
> > I have installed MSDE on an XP Pro machine with all SPs and fixes up to
but
> > not including SP2 and wanted to make sure that I didn't do anything to
screw
> > up our current development processes ... we're in the middle of a large
dev
> > project and didn't want to bring everything to a grinding halt.
> >
> > Yes, we will install SP2 and test to make sure that our .NET apps will
work
> > under SP2 but I want to do it in a "controlled manner" ... not an
> > inadvertent shutdown in the middle.
> >
> > Anyone know of any issues, other than the Firewall, that makes SQL
Server
> > 2000 incompatible with XP SP2?
> >
> > Thanks...
> >
> > Ron|||You might also check out:
Finally, you should absolutely watch and learn from the webcast titled ?MSDN
Webcast: SQL Server and Windows XP SP2 - Level 300 ? available at
http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032253410&Culture=en-US
I found it to be very helpful.
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Ron Fluegge" <rmflugge@.swbell.net> wrote in message
news:e9BEMnPgEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Thank you very much for both replies. Your replies were both thorough and
> very helpful.
> I will back the machines up and begin installing SP2 on Saturday.
> Hopefully, I will be able to report successful and uneventful
installations
> on Monday.
> Again, many thanks...
> Ron
> ""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
> news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
> > Hi Ron,
> >
> > Additionally, I would like to provide five HOW-TO articiles for
> > configuration SQL Server with XP SP2.
> >
> > How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> > http://support.microsoft.com/?id=841249
> >
> > How to enable SQL Server connectivity on Windows XP Service Pack 2
> > http://support.microsoft.com/?id=841251
> >
> > How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
Server
> > 2000
> > http://support.microsoft.com/?id=841252
> >
> > How to enable SQL Server 2000 Reporting Services on Windows XP Service
> Pack
> > 2
> > http://support.microsoft.com/?id=841253
> >
> > How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
> > http://support.microsoft.com/default.aspx?kbid=842005
> >
> > How to enable SQL Server 2000 Analysis Services and OLAP Services on
> > computers that are running Windows XP SP2
> > http://support.microsoft.com/?id=841256
> >
> > How to use a script to programmatically open ports for SQL Server to use
> on
> > systems that are running Windows XP Service Pack 2
> > http://support.microsoft.com/default.aspx?kbid=839980
> >
> > Thank you for your patience and cooperation again. If you have any
> > questions or concerns, don't hesitate to let me know. We are here to be
of
> > assistance!
> >
> >
> > Sincerely yours,
> >
> > Mingqing Cheng
> > Microsoft Developer Community Support
> > ---
> > Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> > This posting is provided "as is" with no warranties and confers no
rights.
> > Please reply to newsgroups only, many thanks!
> >
>|||Brian,
Will do ... THANKS VERY MUCH!!!
Ron
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:OOHq06UgEHA.1764@.TK2MSFTNGP10.phx.gbl...
> You might also check out:
> Finally, you should absolutely watch and learn from the webcast titled
'MSDN
> Webcast: SQL Server and Windows XP SP2 - Level 300 ' available at
>
http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032253410&Culture=en-US
>
> I found it to be very helpful.
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Ron Fluegge" <rmflugge@.swbell.net> wrote in message
> news:e9BEMnPgEHA.1972@.TK2MSFTNGP09.phx.gbl...
> > Thank you very much for both replies. Your replies were both thorough
and
> > very helpful.
> >
> > I will back the machines up and begin installing SP2 on Saturday.
> > Hopefully, I will be able to report successful and uneventful
> installations
> > on Monday.
> >
> > Again, many thanks...
> >
> > Ron
> >
> > ""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in
message
> > news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
> > > Hi Ron,
> > >
> > > Additionally, I would like to provide five HOW-TO articiles for
> > > configuration SQL Server with XP SP2.
> > >
> > > How to configure Windows XP Service Pack 2 (SP2) for use with SQL
Server
> > > http://support.microsoft.com/?id=841249
> > >
> > > How to enable SQL Server connectivity on Windows XP Service Pack 2
> > > http://support.microsoft.com/?id=841251
> > >
> > > How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
> Server
> > > 2000
> > > http://support.microsoft.com/?id=841252
> > >
> > > How to enable SQL Server 2000 Reporting Services on Windows XP Service
> > Pack
> > > 2
> > > http://support.microsoft.com/?id=841253
> > >
> > > How to enable the ISAPI component on SQLXML on Windows XP Service Pack
2
> > > http://support.microsoft.com/default.aspx?kbid=842005
> > >
> > > How to enable SQL Server 2000 Analysis Services and OLAP Services on
> > > computers that are running Windows XP SP2
> > > http://support.microsoft.com/?id=841256
> > >
> > > How to use a script to programmatically open ports for SQL Server to
use
> > on
> > > systems that are running Windows XP Service Pack 2
> > > http://support.microsoft.com/default.aspx?kbid=839980
> > >
> > > Thank you for your patience and cooperation again. If you have any
> > > questions or concerns, don't hesitate to let me know. We are here to
be
> of
> > > assistance!
> > >
> > >
> > > Sincerely yours,
> > >
> > > Mingqing Cheng
> > > Microsoft Developer Community Support
> > > ---
> > > Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> > > This posting is provided "as is" with no warranties and confers no
> rights.
> > > Please reply to newsgroups only, many thanks!
> > >
> >
> >
>|||Hi Ron,
If you encounter any questions or concerns when upgrading to Windows XP
Service Pack 2, please feel free to reply here or make a new thread. We
would love to make a follow up until that issue is completely resolved.
Good Luck!
Thank you for your patience and cooperation.
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I just finished the upgrade to SP2 ... on this machine I have both SQL
Server 2000 and Oracle 9i as well as VS 2003 -- it's my development machine.
It all went well without a hitch!!!
Everything is up and running without any problems so far software or
hardware-wise. I have a dual AMD MoBo with RAID controllers and it is
having no problems.
So needless to say, I am a happy camper ...
Ron
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v7ocVFcgEHA.480@.cpmsftngxa06.phx.gbl...
> Hi Ron,
> If you encounter any questions or concerns when upgrading to Windows XP
> Service Pack 2, please feel free to reply here or make a new thread. We
> would love to make a follow up until that issue is completely resolved.
> Good Luck!
> Thank you for your patience and cooperation.
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
Any SQL Server 2000 and XP SP2 issues?
There is a recent news article that indicates that Microsoft has "warned"
its customers about SQL Server 2000 (version not identified) not being
compatible with the XP SP 2.
I went to the MS website and searched everything I could find on the RTM
version of SP2. I found no such warning ... I found "issues" that could
come up if the Firewall is enabled and how to modify the settings so that
you could get to the SQL Server 2000 if there were problems.
I have installed MSDE on an XP Pro machine with all SPs and fixes up to but
not including SP2 and wanted to make sure that I didn't do anything to screw
up our current development processes ... we're in the middle of a large dev
project and didn't want to bring everything to a grinding halt.
Yes, we will install SP2 and test to make sure that our .NET apps will work
under SP2 but I want to do it in a "controlled manner" ... not an
inadvertent shutdown in the middle.
Anyone know of any issues, other than the Firewall, that makes SQL Server
2000 incompatible with XP SP2?
Thanks...
Ron
Hi Ron,
Thanks for using MSDN Managed Newsgroup!
Here are some links showing why it is warned using SQL Server / MSDE with
XP SP2
"some programs may seem not to work. By default, Windows Firewall is
enabled and blocks unsolicited connections to your computer"
Some programs seem to stop working after you install Windows XP Service
Pack 2
http://support.microsoft.com/default.aspx?kbid=842242
"After you install Microsoft Windows XP Service Pack 2 on a computer that
is configured as a distributor, if you try to synchronize data from a
subscriber that is configured on a remote computer, you may notice that the
changes that are made in the subscriber database are not updated to the
publisher database."
BUG: The changes in a remote subscriber are not updated to the publisher
for a queued updating replication that uses Message Queuing on a
computer that is running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839278
"You may not be able to connect to an instance of SQL Server, and you may
receive one of the following error messages.
[Named Pipes]SQL Server does not exist or access denied.
Unable to connect to server <SQL Server instance name>"
You may not be able to connect to an instance of SQL Server that is
configured to use the Named Pipes server network library on a computer
that is running Windows XP Service Pack 2
http://support.microsoft.com/?id=839269
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1"
You may receive a 7391 error message in SQL Server 2000 when you run a
distributed transaction against a linked server after you install Microsoft
Windows XP Service Pack 2
http://support.microsoft.com/?id=839279
" the SQL debugging feature in Microsoft Visual Studio .NET 2003 (Visual
Studio .NET) does not work. When you try to debug a SQL Server stored
procedure by using the Step Into Stored Procedure option in the Server
Explorer pane, you may receive the following error message:
Cannot debug stored procedures because the SQL Server database is not setup
correctly or user does not have permission to execute master.sp_sdidebug.
Run SQL Server setup or contact database administrator."
BUG: SQL debugging does not work in Visual Studio .NET after you install
Windows XP Service Pack 2
http://support.microsoft.com/?id=839280
"When you install Microsoft SQL Server 2000 or Microsoft SQL Server Desktop
Engine (also known as MSDE 2000) on a computer that is running Microsoft
Windows XP Service Pack 2 (SP2), a message is logged in the application
event log. The message states that the instance of SQL Server or the
instance of MSDE is vulnerable to virus attacks."
A message stating that an instance of SQL Server is vulnerable to virus
attacks is logged in the application event log when you install SQL Server
2000 or MSDE 2000 on a computer that is running Windows XP Service Pack 2
http://support.microsoft.com/?id=841375
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1 "
You may receive a 7391 error message in SQLOLEDB when you run a distributed
transaction against a linked server after you install Microsoft Windows XP
Service Pack 2
http://support.microsoft.com/?id=873160
Here is another very useful link for you about how to troubleshooting
Windows Firewall settings in Windows XP SP2
Troubleshooting Windows Firewall settings in Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=875357
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Hi Ron,
Additionally, I would like to provide five HOW-TO articiles for
configuration SQL Server with XP SP2.
How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/?id=841249
How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/?id=841251
How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server
2000
http://support.microsoft.com/?id=841252
How to enable SQL Server 2000 Reporting Services on Windows XP Service Pack
2
http://support.microsoft.com/?id=841253
How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=842005
How to enable SQL Server 2000 Analysis Services and OLAP Services on
computers that are running Windows XP SP2
http://support.microsoft.com/?id=841256
How to use a script to programmatically open ports for SQL Server to use on
systems that are running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839980
Thank you for your patience and cooperation again. If you have any
questions or concerns, don't hesitate to let me know. We are here to be of
assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Thank you very much for both replies. Your replies were both thorough and
very helpful.
I will back the machines up and begin installing SP2 on Saturday.
Hopefully, I will be able to report successful and uneventful installations
on Monday.
Again, many thanks...
Ron
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
> Hi Ron,
> Additionally, I would like to provide five HOW-TO articiles for
> configuration SQL Server with XP SP2.
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> How to enable SQL Server connectivity on Windows XP Service Pack 2
> http://support.microsoft.com/?id=841251
> How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server
> 2000
> http://support.microsoft.com/?id=841252
> How to enable SQL Server 2000 Reporting Services on Windows XP Service
Pack
> 2
> http://support.microsoft.com/?id=841253
> How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=842005
> How to enable SQL Server 2000 Analysis Services and OLAP Services on
> computers that are running Windows XP SP2
> http://support.microsoft.com/?id=841256
> How to use a script to programmatically open ports for SQL Server to use
on
> systems that are running Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839980
> Thank you for your patience and cooperation again. If you have any
> questions or concerns, don't hesitate to let me know. We are here to be of
> assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||If you use Visual Studio.Net to debug SQL Stored Proceedures you'll
want to wait. More details are at
http://support.microsoft.com/?kbid=839280. If anyone knows of a way
around this problem, please let me know.
Ken Kimball [kkimball@.gmail.com]
"Ron Fluegge" <rmflugge@.swbell.net> wrote in message news:<#i24S0HgEHA.904@.TK2MSFTNGP09.phx.gbl>...
> There is a recent news article that indicates that Microsoft has "warned"
> its customers about SQL Server 2000 (version not identified) not being
> compatible with the XP SP 2.
> I went to the MS website and searched everything I could find on the RTM
> version of SP2. I found no such warning ... I found "issues" that could
> come up if the Firewall is enabled and how to modify the settings so that
> you could get to the SQL Server 2000 if there were problems.
> I have installed MSDE on an XP Pro machine with all SPs and fixes up to but
> not including SP2 and wanted to make sure that I didn't do anything to screw
> up our current development processes ... we're in the middle of a large dev
> project and didn't want to bring everything to a grinding halt.
> Yes, we will install SP2 and test to make sure that our .NET apps will work
> under SP2 but I want to do it in a "controlled manner" ... not an
> inadvertent shutdown in the middle.
> Anyone know of any issues, other than the Firewall, that makes SQL Server
> 2000 incompatible with XP SP2?
> Thanks...
> Ron
|||Ken,
Yes, I was aware of that problem. I do use VS 2003 to develop apps but do
not use SQL Stored Procedures (for a number of reasons specific to our
apps).
I was very surprised to find the number of "issues" related to SQL Server
2000 given that is the current release of MS's SQL Server -- especially
since there is nothing to indicate that patches or fixes are forthcoming.
On the same XP Pro machine, I'm also running Oracle 9i and I'm hoping that
it doesn't come to a crashing halt as well. (These are used for
"development" and not for production databases)
Ron
"Ken Kimball" <kkimball@.gmail.com> wrote in message
news:466a0cb4.0408130512.4468a03a@.posting.google.c om...
> If you use Visual Studio.Net to debug SQL Stored Proceedures you'll
> want to wait. More details are at
> http://support.microsoft.com/?kbid=839280. If anyone knows of a way
> around this problem, please let me know.
> Ken Kimball [kkimball@.gmail.com]
> "Ron Fluegge" <rmflugge@.swbell.net> wrote in message
news:<#i24S0HgEHA.904@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
"warned"[vbcol=seagreen]
that[vbcol=seagreen]
but[vbcol=seagreen]
screw[vbcol=seagreen]
dev[vbcol=seagreen]
work[vbcol=seagreen]
Server[vbcol=seagreen]
|||You might also check out:
Finally, you should absolutely watch and learn from the webcast titled MSDN
Webcast: SQL Server and Windows XP SP2 - Level 300 available at
http://msevents.microsoft.com/CUI/Ev...&Culture=en-US
I found it to be very helpful.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Ron Fluegge" <rmflugge@.swbell.net> wrote in message
news:e9BEMnPgEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Thank you very much for both replies. Your replies were both thorough and
> very helpful.
> I will back the machines up and begin installing SP2 on Saturday.
> Hopefully, I will be able to report successful and uneventful
installations[vbcol=seagreen]
> on Monday.
> Again, many thanks...
> Ron
> ""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
> news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
Server[vbcol=seagreen]
> Pack
> on
of[vbcol=seagreen]
rights.
>
|||Brian,
Will do ... THANKS VERY MUCH!!!
Ron
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:OOHq06UgEHA.1764@.TK2MSFTNGP10.phx.gbl...
> You might also check out:
> Finally, you should absolutely watch and learn from the webcast titled
'MSDN
> Webcast: SQL Server and Windows XP SP2 - Level 300 ' available at
>
http://msevents.microsoft.com/CUI/Ev...&Culture=en-US[vbcol=seagreen]
>
> I found it to be very helpful.
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Ron Fluegge" <rmflugge@.swbell.net> wrote in message
> news:e9BEMnPgEHA.1972@.TK2MSFTNGP09.phx.gbl...
and[vbcol=seagreen]
> installations
message[vbcol=seagreen]
Server[vbcol=seagreen]
> Server
2[vbcol=seagreen]
use[vbcol=seagreen]
be
> of
> rights.
>
|||Hi Ron,
If you encounter any questions or concerns when upgrading to Windows XP
Service Pack 2, please feel free to reply here or make a new thread. We
would love to make a follow up until that issue is completely resolved.
Good Luck!
Thank you for your patience and cooperation.
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I just finished the upgrade to SP2 ... on this machine I have both SQL
Server 2000 and Oracle 9i as well as VS 2003 -- it's my development machine.
It all went well without a hitch!!!
Everything is up and running without any problems so far software or
hardware-wise. I have a dual AMD MoBo with RAID controllers and it is
having no problems.
So needless to say, I am a happy camper ...
Ron
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v7ocVFcgEHA.480@.cpmsftngxa06.phx.gbl...
> Hi Ron,
> If you encounter any questions or concerns when upgrading to Windows XP
> Service Pack 2, please feel free to reply here or make a new thread. We
> would love to make a follow up until that issue is completely resolved.
> Good Luck!
> Thank you for your patience and cooperation.
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
its customers about SQL Server 2000 (version not identified) not being
compatible with the XP SP 2.
I went to the MS website and searched everything I could find on the RTM
version of SP2. I found no such warning ... I found "issues" that could
come up if the Firewall is enabled and how to modify the settings so that
you could get to the SQL Server 2000 if there were problems.
I have installed MSDE on an XP Pro machine with all SPs and fixes up to but
not including SP2 and wanted to make sure that I didn't do anything to screw
up our current development processes ... we're in the middle of a large dev
project and didn't want to bring everything to a grinding halt.
Yes, we will install SP2 and test to make sure that our .NET apps will work
under SP2 but I want to do it in a "controlled manner" ... not an
inadvertent shutdown in the middle.
Anyone know of any issues, other than the Firewall, that makes SQL Server
2000 incompatible with XP SP2?
Thanks...
Ron
Hi Ron,
Thanks for using MSDN Managed Newsgroup!
Here are some links showing why it is warned using SQL Server / MSDE with
XP SP2
"some programs may seem not to work. By default, Windows Firewall is
enabled and blocks unsolicited connections to your computer"
Some programs seem to stop working after you install Windows XP Service
Pack 2
http://support.microsoft.com/default.aspx?kbid=842242
"After you install Microsoft Windows XP Service Pack 2 on a computer that
is configured as a distributor, if you try to synchronize data from a
subscriber that is configured on a remote computer, you may notice that the
changes that are made in the subscriber database are not updated to the
publisher database."
BUG: The changes in a remote subscriber are not updated to the publisher
for a queued updating replication that uses Message Queuing on a
computer that is running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839278
"You may not be able to connect to an instance of SQL Server, and you may
receive one of the following error messages.
[Named Pipes]SQL Server does not exist or access denied.
Unable to connect to server <SQL Server instance name>"
You may not be able to connect to an instance of SQL Server that is
configured to use the Named Pipes server network library on a computer
that is running Windows XP Service Pack 2
http://support.microsoft.com/?id=839269
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1"
You may receive a 7391 error message in SQL Server 2000 when you run a
distributed transaction against a linked server after you install Microsoft
Windows XP Service Pack 2
http://support.microsoft.com/?id=839279
" the SQL debugging feature in Microsoft Visual Studio .NET 2003 (Visual
Studio .NET) does not work. When you try to debug a SQL Server stored
procedure by using the Step Into Stored Procedure option in the Server
Explorer pane, you may receive the following error message:
Cannot debug stored procedures because the SQL Server database is not setup
correctly or user does not have permission to execute master.sp_sdidebug.
Run SQL Server setup or contact database administrator."
BUG: SQL debugging does not work in Visual Studio .NET after you install
Windows XP Service Pack 2
http://support.microsoft.com/?id=839280
"When you install Microsoft SQL Server 2000 or Microsoft SQL Server Desktop
Engine (also known as MSDE 2000) on a computer that is running Microsoft
Windows XP Service Pack 2 (SP2), a message is logged in the application
event log. The message states that the instance of SQL Server or the
instance of MSDE is vulnerable to virus attacks."
A message stating that an instance of SQL Server is vulnerable to virus
attacks is logged in the application event log when you install SQL Server
2000 or MSDE 2000 on a computer that is running Windows XP Service Pack 2
http://support.microsoft.com/?id=841375
"When you run a distributed transaction against an instance of SQL Server,
you may receive an error message that is similar to the following:
Server: Msg 7391, Level 16, State 1, Line 1 "
You may receive a 7391 error message in SQLOLEDB when you run a distributed
transaction against a linked server after you install Microsoft Windows XP
Service Pack 2
http://support.microsoft.com/?id=873160
Here is another very useful link for you about how to troubleshooting
Windows Firewall settings in Windows XP SP2
Troubleshooting Windows Firewall settings in Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=875357
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Hi Ron,
Additionally, I would like to provide five HOW-TO articiles for
configuration SQL Server with XP SP2.
How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
http://support.microsoft.com/?id=841249
How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/?id=841251
How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server
2000
http://support.microsoft.com/?id=841252
How to enable SQL Server 2000 Reporting Services on Windows XP Service Pack
2
http://support.microsoft.com/?id=841253
How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=842005
How to enable SQL Server 2000 Analysis Services and OLAP Services on
computers that are running Windows XP SP2
http://support.microsoft.com/?id=841256
How to use a script to programmatically open ports for SQL Server to use on
systems that are running Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?kbid=839980
Thank you for your patience and cooperation again. If you have any
questions or concerns, don't hesitate to let me know. We are here to be of
assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||Thank you very much for both replies. Your replies were both thorough and
very helpful.
I will back the machines up and begin installing SP2 on Saturday.
Hopefully, I will be able to report successful and uneventful installations
on Monday.
Again, many thanks...
Ron
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
> Hi Ron,
> Additionally, I would like to provide five HOW-TO articiles for
> configuration SQL Server with XP SP2.
> How to configure Windows XP Service Pack 2 (SP2) for use with SQL Server
> http://support.microsoft.com/?id=841249
> How to enable SQL Server connectivity on Windows XP Service Pack 2
> http://support.microsoft.com/?id=841251
> How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server
> 2000
> http://support.microsoft.com/?id=841252
> How to enable SQL Server 2000 Reporting Services on Windows XP Service
Pack
> 2
> http://support.microsoft.com/?id=841253
> How to enable the ISAPI component on SQLXML on Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=842005
> How to enable SQL Server 2000 Analysis Services and OLAP Services on
> computers that are running Windows XP SP2
> http://support.microsoft.com/?id=841256
> How to use a script to programmatically open ports for SQL Server to use
on
> systems that are running Windows XP Service Pack 2
> http://support.microsoft.com/default.aspx?kbid=839980
> Thank you for your patience and cooperation again. If you have any
> questions or concerns, don't hesitate to let me know. We are here to be of
> assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||If you use Visual Studio.Net to debug SQL Stored Proceedures you'll
want to wait. More details are at
http://support.microsoft.com/?kbid=839280. If anyone knows of a way
around this problem, please let me know.
Ken Kimball [kkimball@.gmail.com]
"Ron Fluegge" <rmflugge@.swbell.net> wrote in message news:<#i24S0HgEHA.904@.TK2MSFTNGP09.phx.gbl>...
> There is a recent news article that indicates that Microsoft has "warned"
> its customers about SQL Server 2000 (version not identified) not being
> compatible with the XP SP 2.
> I went to the MS website and searched everything I could find on the RTM
> version of SP2. I found no such warning ... I found "issues" that could
> come up if the Firewall is enabled and how to modify the settings so that
> you could get to the SQL Server 2000 if there were problems.
> I have installed MSDE on an XP Pro machine with all SPs and fixes up to but
> not including SP2 and wanted to make sure that I didn't do anything to screw
> up our current development processes ... we're in the middle of a large dev
> project and didn't want to bring everything to a grinding halt.
> Yes, we will install SP2 and test to make sure that our .NET apps will work
> under SP2 but I want to do it in a "controlled manner" ... not an
> inadvertent shutdown in the middle.
> Anyone know of any issues, other than the Firewall, that makes SQL Server
> 2000 incompatible with XP SP2?
> Thanks...
> Ron
|||Ken,
Yes, I was aware of that problem. I do use VS 2003 to develop apps but do
not use SQL Stored Procedures (for a number of reasons specific to our
apps).
I was very surprised to find the number of "issues" related to SQL Server
2000 given that is the current release of MS's SQL Server -- especially
since there is nothing to indicate that patches or fixes are forthcoming.
On the same XP Pro machine, I'm also running Oracle 9i and I'm hoping that
it doesn't come to a crashing halt as well. (These are used for
"development" and not for production databases)
Ron
"Ken Kimball" <kkimball@.gmail.com> wrote in message
news:466a0cb4.0408130512.4468a03a@.posting.google.c om...
> If you use Visual Studio.Net to debug SQL Stored Proceedures you'll
> want to wait. More details are at
> http://support.microsoft.com/?kbid=839280. If anyone knows of a way
> around this problem, please let me know.
> Ken Kimball [kkimball@.gmail.com]
> "Ron Fluegge" <rmflugge@.swbell.net> wrote in message
news:<#i24S0HgEHA.904@.TK2MSFTNGP09.phx.gbl>...[vbcol=seagreen]
"warned"[vbcol=seagreen]
that[vbcol=seagreen]
but[vbcol=seagreen]
screw[vbcol=seagreen]
dev[vbcol=seagreen]
work[vbcol=seagreen]
Server[vbcol=seagreen]
|||You might also check out:
Finally, you should absolutely watch and learn from the webcast titled MSDN
Webcast: SQL Server and Windows XP SP2 - Level 300 available at
http://msevents.microsoft.com/CUI/Ev...&Culture=en-US
I found it to be very helpful.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Ron Fluegge" <rmflugge@.swbell.net> wrote in message
news:e9BEMnPgEHA.1972@.TK2MSFTNGP09.phx.gbl...
> Thank you very much for both replies. Your replies were both thorough and
> very helpful.
> I will back the machines up and begin installing SP2 on Saturday.
> Hopefully, I will be able to report successful and uneventful
installations[vbcol=seagreen]
> on Monday.
> Again, many thanks...
> Ron
> ""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
> news:g5WOYOOgEHA.3356@.cpmsftngxa06.phx.gbl...
Server[vbcol=seagreen]
> Pack
> on
of[vbcol=seagreen]
rights.
>
|||Brian,
Will do ... THANKS VERY MUCH!!!
Ron
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:OOHq06UgEHA.1764@.TK2MSFTNGP10.phx.gbl...
> You might also check out:
> Finally, you should absolutely watch and learn from the webcast titled
'MSDN
> Webcast: SQL Server and Windows XP SP2 - Level 300 ' available at
>
http://msevents.microsoft.com/CUI/Ev...&Culture=en-US[vbcol=seagreen]
>
> I found it to be very helpful.
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "Ron Fluegge" <rmflugge@.swbell.net> wrote in message
> news:e9BEMnPgEHA.1972@.TK2MSFTNGP09.phx.gbl...
and[vbcol=seagreen]
> installations
message[vbcol=seagreen]
Server[vbcol=seagreen]
> Server
2[vbcol=seagreen]
use[vbcol=seagreen]
be
> of
> rights.
>
|||Hi Ron,
If you encounter any questions or concerns when upgrading to Windows XP
Service Pack 2, please feel free to reply here or make a new thread. We
would love to make a follow up until that issue is completely resolved.
Good Luck!
Thank you for your patience and cooperation.
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I just finished the upgrade to SP2 ... on this machine I have both SQL
Server 2000 and Oracle 9i as well as VS 2003 -- it's my development machine.
It all went well without a hitch!!!
Everything is up and running without any problems so far software or
hardware-wise. I have a dual AMD MoBo with RAID controllers and it is
having no problems.
So needless to say, I am a happy camper ...
Ron
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:v7ocVFcgEHA.480@.cpmsftngxa06.phx.gbl...
> Hi Ron,
> If you encounter any questions or concerns when upgrading to Windows XP
> Service Pack 2, please feel free to reply here or make a new thread. We
> would love to make a follow up until that issue is completely resolved.
> Good Luck!
> Thank you for your patience and cooperation.
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
>
2012年2月25日星期六
Any known issues with AWE and Windows 2003
Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
it. Does anyone know more or a KB article ?I am not sure, but we are currently experinceing performance issues
since going to SP1. See my post in this group, Too Much RAM SQL Server
2000?|||Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one just
hit us pretty good:
http://support.microsoft.com/defaul...kb;en-us;899599
Darian Miller
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||Hi
Darian, how busy was your SQL Server to have this problem?
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/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> hit us pretty good:
> http://support.microsoft.com/defaul...kb;en-us;899599
> Darian Miller
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>|||Here are a few:
http://support.microsoft.com/defaul...kb;en-us;895575
http://support.microsoft.com/defaul...kb;en-us;838765
Adrian
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/defaul...kb;en-us;895575
> http://support.microsoft.com/defaul...kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes[vbcol=seagreen]
>|||Actually, a PAE fix for Win2K3 has also been released as part of a Security
Hotfix Critical Update:
Microsoft Security Bulletin MS04-032
Security Update for Microsoft Windows (840987)
http://www.microsoft.com/technet/se...n/ms04-032.mspx
Sincerely,
Anthony Thomas
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/defaul...kb;en-us;895575
> http://support.microsoft.com/defaul...kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes[vbcol=seagreen]
>|||The issues with w2k3 at very small compared to NT 4.0 and w2k.
We found that most of the 'issues' with w2k3 are NT 4.0 MCSE's not
understanding security.
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/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
> So with all these issues with Win2K3, what does MS have to say ? Do
> companies move forward on Win2K3 ?
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> fixes
>
it. Does anyone know more or a KB article ?I am not sure, but we are currently experinceing performance issues
since going to SP1. See my post in this group, Too Much RAM SQL Server
2000?|||Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one just
hit us pretty good:
http://support.microsoft.com/defaul...kb;en-us;899599
Darian Miller
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||Hi
Darian, how busy was your SQL Server to have this problem?
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/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> hit us pretty good:
> http://support.microsoft.com/defaul...kb;en-us;899599
> Darian Miller
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>|||Here are a few:
http://support.microsoft.com/defaul...kb;en-us;895575
http://support.microsoft.com/defaul...kb;en-us;838765
Adrian
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/defaul...kb;en-us;895575
> http://support.microsoft.com/defaul...kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes[vbcol=seagreen]
>|||Actually, a PAE fix for Win2K3 has also been released as part of a Security
Hotfix Critical Update:
Microsoft Security Bulletin MS04-032
Security Update for Microsoft Windows (840987)
http://www.microsoft.com/technet/se...n/ms04-032.mspx
Sincerely,
Anthony Thomas
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/defaul...kb;en-us;895575
> http://support.microsoft.com/defaul...kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes[vbcol=seagreen]
>|||The issues with w2k3 at very small compared to NT 4.0 and w2k.
We found that most of the 'issues' with w2k3 are NT 4.0 MCSE's not
understanding security.
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/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
> So with all these issues with Win2K3, what does MS have to say ? Do
> companies move forward on Win2K3 ?
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> fixes
>
Any known issues with AWE and Windows 2003
Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
it. Does anyone know more or a KB article ?I am not sure, but we are currently experinceing performance issues
since going to SP1. See my post in this group, Too Much RAM SQL Server
2000?|||Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one just
hit us pretty good:
http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
Darian Miller
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||Hi
Darian, how busy was your SQL Server to have this problem?
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/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> hit us pretty good:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> Darian Miller
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
>> fixes
>> it. Does anyone know more or a KB article ?
>>
>|||We're still documenting the deal, but the 'security feature' actually seems
to cause a lot of increased traffic due to the many retry attempts. (We're
in the 3-500 batch requests/second range normally.)
Basically it appears that the client makes a successful connection to the
server and the connection is immediately forcibly dropped by the server
causing "General Network Error" on DBNETLIB ConnectionWrite (send())
The errors were coming in what we thought was fairly randomly but apparently
was based on peak levels set by this security feature. If the server thinks
the source is attempting a denial of service attack then it decides to drop
the network traffic, without notice of any kind (no event logging.) What I
would think it should do is if it thinks a source is attempting a denial of
service, then it should block all packets from the source, not just a few of
the peak ones, and it should document that it has automatically stepped in
to "save the day"... Much more difficult to track down they way it is
currently implemented. We were on the phone with Microsoft for over 8 hours
over the past two days on this particular problem and they didn't come
across the solution - we had to find it and tell them about it.
If you have SQL Server on a Windows 2003 Server with SP1, then I'd suggest
setting the registry setting referenced in the knowledge based article,
especially since it's highly likely that your SQL Server is protected from
outside connections to begin with.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Add DWORD: SynAttackProtect, value 0
I'm mainly just venting...but it's ludicrous to have this sort of 'feature'
implemented the way it is. Security needs to be a focus, but goodness sakes
you need to have some common sense about it. What's the point of dropping
'some' packets if it's a suspected DOS attack? They might have their
reasons, but there is no reason to not have a log entry stating that they
intentionally dropped network traffic. A simple "Suspected
denial-of-service attack detected, taking corrective action" would have
saved many hours of work.
Time for a drink! :)
Darian Miller
darian
@.
darianmiller
.com
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23EMfUSHbFHA.720@.TK2MSFTNGP15.phx.gbl...
> Hi
> Darian, how busy was your SQL Server to have this problem?
> 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/
> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> > just
> > hit us pretty good:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> >
> > Darian Miller
> >
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> >> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
> >> fixes
> >> it. Does anyone know more or a KB article ?
> >>
> >>
> >
> >
>|||Here are a few:
http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
Adrian
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||Hi
Very interesting. Thanks for sharing this, I think you have saved many
people a lot of time.
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/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:%23A65roHbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> We're still documenting the deal, but the 'security feature' actually
> seems
> to cause a lot of increased traffic due to the many retry attempts.
> (We're
> in the 3-500 batch requests/second range normally.)
> Basically it appears that the client makes a successful connection to the
> server and the connection is immediately forcibly dropped by the server
> causing "General Network Error" on DBNETLIB ConnectionWrite (send())
> The errors were coming in what we thought was fairly randomly but
> apparently
> was based on peak levels set by this security feature. If the server
> thinks
> the source is attempting a denial of service attack then it decides to
> drop
> the network traffic, without notice of any kind (no event logging.) What
> I
> would think it should do is if it thinks a source is attempting a denial
> of
> service, then it should block all packets from the source, not just a few
> of
> the peak ones, and it should document that it has automatically stepped in
> to "save the day"... Much more difficult to track down they way it is
> currently implemented. We were on the phone with Microsoft for over 8
> hours
> over the past two days on this particular problem and they didn't come
> across the solution - we had to find it and tell them about it.
> If you have SQL Server on a Windows 2003 Server with SP1, then I'd suggest
> setting the registry setting referenced in the knowledge based article,
> especially since it's highly likely that your SQL Server is protected from
> outside connections to begin with.
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> Add DWORD: SynAttackProtect, value 0
> I'm mainly just venting...but it's ludicrous to have this sort of
> 'feature'
> implemented the way it is. Security needs to be a focus, but goodness
> sakes
> you need to have some common sense about it. What's the point of dropping
> 'some' packets if it's a suspected DOS attack? They might have their
> reasons, but there is no reason to not have a log entry stating that they
> intentionally dropped network traffic. A simple "Suspected
> denial-of-service attack detected, taking corrective action" would have
> saved many hours of work.
> Time for a drink! :)
> Darian Miller
>
> darian
> @.
> darianmiller
> .com
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23EMfUSHbFHA.720@.TK2MSFTNGP15.phx.gbl...
>> Hi
>> Darian, how busy was your SQL Server to have this problem?
>> 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/
>> "Darian Miller" <darianmiller@.online.nospam> wrote in message
>> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
>> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
>> > just
>> > hit us pretty good:
>> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
>> >
>> > Darian Miller
>> >
>> >
>> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
>> > news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>> >> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
>> >> fixes
>> >> it. Does anyone know more or a KB article ?
>> >>
>> >>
>> >
>> >
>>
>|||"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
just
> hit us pretty good:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
Thanks for that tip. We have a high-volume SQL instance where we're seeing
behavior similar to what the KB article describes. We're not running with
any OS service pack, but we do apply the monthly patches. I wonder if the
DOS-preventing "security feature" has been included in any of those.|||Yes, I believe it has been included in a security fix. If you've seen these
messages, apply the registry setting and they go away immediately after a
restart.
"Karen Collins" <kcollins5@.tampabay.rr.com> wrote in message
news:eL3p4TNbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> > hit us pretty good:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
>
> Thanks for that tip. We have a high-volume SQL instance where we're
seeing
> behavior similar to what the KB article describes. We're not running with
> any OS service pack, but we do apply the monthly patches. I wonder if the
> DOS-preventing "security feature" has been included in any of those.
>|||I hope so!
Darian
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ehVr8SLbFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Hi
> Very interesting. Thanks for sharing this, I think you have saved many
> people a lot of time.
> 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/
> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> news:%23A65roHbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> > We're still documenting the deal, but the 'security feature' actually
> > seems
> > to cause a lot of increased traffic due to the many retry attempts.
> > (We're
> > in the 3-500 batch requests/second range normally.)
> >
> > Basically it appears that the client makes a successful connection to
the
> > server and the connection is immediately forcibly dropped by the server
> > causing "General Network Error" on DBNETLIB ConnectionWrite (send())
> >
> > The errors were coming in what we thought was fairly randomly but
> > apparently
> > was based on peak levels set by this security feature. If the server
> > thinks
> > the source is attempting a denial of service attack then it decides to
> > drop
> > the network traffic, without notice of any kind (no event logging.)
What
> > I
> > would think it should do is if it thinks a source is attempting a denial
> > of
> > service, then it should block all packets from the source, not just a
few
> > of
> > the peak ones, and it should document that it has automatically stepped
in
> > to "save the day"... Much more difficult to track down they way it is
> > currently implemented. We were on the phone with Microsoft for over 8
> > hours
> > over the past two days on this particular problem and they didn't come
> > across the solution - we had to find it and tell them about it.
> >
> > If you have SQL Server on a Windows 2003 Server with SP1, then I'd
suggest
> > setting the registry setting referenced in the knowledge based article,
> > especially since it's highly likely that your SQL Server is protected
from
> > outside connections to begin with.
> >
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> > Add DWORD: SynAttackProtect, value 0
> >
> > I'm mainly just venting...but it's ludicrous to have this sort of
> > 'feature'
> > implemented the way it is. Security needs to be a focus, but goodness
> > sakes
> > you need to have some common sense about it. What's the point of
dropping
> > 'some' packets if it's a suspected DOS attack? They might have their
> > reasons, but there is no reason to not have a log entry stating that
they
> > intentionally dropped network traffic. A simple "Suspected
> > denial-of-service attack detected, taking corrective action" would have
> > saved many hours of work.
> >
> > Time for a drink! :)
> >
> > Darian Miller
> >
> >
> >
> > darian
> > @.
> > darianmiller
> > .com
> >
> > "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> > news:%23EMfUSHbFHA.720@.TK2MSFTNGP15.phx.gbl...
> >> Hi
> >>
> >> Darian, how busy was your SQL Server to have this problem?
> >>
> >> 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/
> >>
> >> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> >> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> >> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this
one
> >> > just
> >> > hit us pretty good:
> >> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> >> >
> >> > Darian Miller
> >> >
> >> >
> >> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> >> > news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> >> >> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
> >> >> fixes
> >> >> it. Does anyone know more or a KB article ?
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>|||So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
> http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> > Heard there are issues with AWE and Windows 2003 and SP1 for Windows
fixes
> > it. Does anyone know more or a KB article ?
> >
> >
>|||Actually, a PAE fix for Win2K3 has also been released as part of a Security
Hotfix Critical Update:
Microsoft Security Bulletin MS04-032
Security Update for Microsoft Windows (840987)
http://www.microsoft.com/technet/security/bulletin/ms04-032.mspx
Sincerely,
Anthony Thomas
--
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
> http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> > Heard there are issues with AWE and Windows 2003 and SP1 for Windows
fixes
> > it. Does anyone know more or a KB article ?
> >
> >
>|||The issues with w2k3 at very small compared to NT 4.0 and w2k.
We found that most of the 'issues' with w2k3 are NT 4.0 MCSE's not
understanding security.
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/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
> So with all these issues with Win2K3, what does MS have to say ? Do
> companies move forward on Win2K3 ?
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
>> Here are a few:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
>> Adrian
>>
>> "Hassan" <fatima_ja@.hotmail.com> wrote in message
>> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>> > Heard there are issues with AWE and Windows 2003 and SP1 for Windows
> fixes
>> > it. Does anyone know more or a KB article ?
>> >
>> >
>>
>
it. Does anyone know more or a KB article ?I am not sure, but we are currently experinceing performance issues
since going to SP1. See my post in this group, Too Much RAM SQL Server
2000?|||Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one just
hit us pretty good:
http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
Darian Miller
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||Hi
Darian, how busy was your SQL Server to have this problem?
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/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> hit us pretty good:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> Darian Miller
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
>> fixes
>> it. Does anyone know more or a KB article ?
>>
>|||We're still documenting the deal, but the 'security feature' actually seems
to cause a lot of increased traffic due to the many retry attempts. (We're
in the 3-500 batch requests/second range normally.)
Basically it appears that the client makes a successful connection to the
server and the connection is immediately forcibly dropped by the server
causing "General Network Error" on DBNETLIB ConnectionWrite (send())
The errors were coming in what we thought was fairly randomly but apparently
was based on peak levels set by this security feature. If the server thinks
the source is attempting a denial of service attack then it decides to drop
the network traffic, without notice of any kind (no event logging.) What I
would think it should do is if it thinks a source is attempting a denial of
service, then it should block all packets from the source, not just a few of
the peak ones, and it should document that it has automatically stepped in
to "save the day"... Much more difficult to track down they way it is
currently implemented. We were on the phone with Microsoft for over 8 hours
over the past two days on this particular problem and they didn't come
across the solution - we had to find it and tell them about it.
If you have SQL Server on a Windows 2003 Server with SP1, then I'd suggest
setting the registry setting referenced in the knowledge based article,
especially since it's highly likely that your SQL Server is protected from
outside connections to begin with.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Add DWORD: SynAttackProtect, value 0
I'm mainly just venting...but it's ludicrous to have this sort of 'feature'
implemented the way it is. Security needs to be a focus, but goodness sakes
you need to have some common sense about it. What's the point of dropping
'some' packets if it's a suspected DOS attack? They might have their
reasons, but there is no reason to not have a log entry stating that they
intentionally dropped network traffic. A simple "Suspected
denial-of-service attack detected, taking corrective action" would have
saved many hours of work.
Time for a drink! :)
Darian Miller
darian
@.
darianmiller
.com
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23EMfUSHbFHA.720@.TK2MSFTNGP15.phx.gbl...
> Hi
> Darian, how busy was your SQL Server to have this problem?
> 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/
> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> > just
> > hit us pretty good:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> >
> > Darian Miller
> >
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> >> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
> >> fixes
> >> it. Does anyone know more or a KB article ?
> >>
> >>
> >
> >
>|||Here are a few:
http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
Adrian
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||Hi
Very interesting. Thanks for sharing this, I think you have saved many
people a lot of time.
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/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:%23A65roHbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> We're still documenting the deal, but the 'security feature' actually
> seems
> to cause a lot of increased traffic due to the many retry attempts.
> (We're
> in the 3-500 batch requests/second range normally.)
> Basically it appears that the client makes a successful connection to the
> server and the connection is immediately forcibly dropped by the server
> causing "General Network Error" on DBNETLIB ConnectionWrite (send())
> The errors were coming in what we thought was fairly randomly but
> apparently
> was based on peak levels set by this security feature. If the server
> thinks
> the source is attempting a denial of service attack then it decides to
> drop
> the network traffic, without notice of any kind (no event logging.) What
> I
> would think it should do is if it thinks a source is attempting a denial
> of
> service, then it should block all packets from the source, not just a few
> of
> the peak ones, and it should document that it has automatically stepped in
> to "save the day"... Much more difficult to track down they way it is
> currently implemented. We were on the phone with Microsoft for over 8
> hours
> over the past two days on this particular problem and they didn't come
> across the solution - we had to find it and tell them about it.
> If you have SQL Server on a Windows 2003 Server with SP1, then I'd suggest
> setting the registry setting referenced in the knowledge based article,
> especially since it's highly likely that your SQL Server is protected from
> outside connections to begin with.
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> Add DWORD: SynAttackProtect, value 0
> I'm mainly just venting...but it's ludicrous to have this sort of
> 'feature'
> implemented the way it is. Security needs to be a focus, but goodness
> sakes
> you need to have some common sense about it. What's the point of dropping
> 'some' packets if it's a suspected DOS attack? They might have their
> reasons, but there is no reason to not have a log entry stating that they
> intentionally dropped network traffic. A simple "Suspected
> denial-of-service attack detected, taking corrective action" would have
> saved many hours of work.
> Time for a drink! :)
> Darian Miller
>
> darian
> @.
> darianmiller
> .com
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23EMfUSHbFHA.720@.TK2MSFTNGP15.phx.gbl...
>> Hi
>> Darian, how busy was your SQL Server to have this problem?
>> 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/
>> "Darian Miller" <darianmiller@.online.nospam> wrote in message
>> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
>> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
>> > just
>> > hit us pretty good:
>> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
>> >
>> > Darian Miller
>> >
>> >
>> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
>> > news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>> >> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
>> >> fixes
>> >> it. Does anyone know more or a KB article ?
>> >>
>> >>
>> >
>> >
>>
>|||"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
just
> hit us pretty good:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
Thanks for that tip. We have a high-volume SQL instance where we're seeing
behavior similar to what the KB article describes. We're not running with
any OS service pack, but we do apply the monthly patches. I wonder if the
DOS-preventing "security feature" has been included in any of those.|||Yes, I believe it has been included in a security fix. If you've seen these
messages, apply the registry setting and they go away immediately after a
restart.
"Karen Collins" <kcollins5@.tampabay.rr.com> wrote in message
news:eL3p4TNbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> > hit us pretty good:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
>
> Thanks for that tip. We have a high-volume SQL instance where we're
seeing
> behavior similar to what the KB article describes. We're not running with
> any OS service pack, but we do apply the monthly patches. I wonder if the
> DOS-preventing "security feature" has been included in any of those.
>|||I hope so!
Darian
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ehVr8SLbFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Hi
> Very interesting. Thanks for sharing this, I think you have saved many
> people a lot of time.
> 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/
> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> news:%23A65roHbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> > We're still documenting the deal, but the 'security feature' actually
> > seems
> > to cause a lot of increased traffic due to the many retry attempts.
> > (We're
> > in the 3-500 batch requests/second range normally.)
> >
> > Basically it appears that the client makes a successful connection to
the
> > server and the connection is immediately forcibly dropped by the server
> > causing "General Network Error" on DBNETLIB ConnectionWrite (send())
> >
> > The errors were coming in what we thought was fairly randomly but
> > apparently
> > was based on peak levels set by this security feature. If the server
> > thinks
> > the source is attempting a denial of service attack then it decides to
> > drop
> > the network traffic, without notice of any kind (no event logging.)
What
> > I
> > would think it should do is if it thinks a source is attempting a denial
> > of
> > service, then it should block all packets from the source, not just a
few
> > of
> > the peak ones, and it should document that it has automatically stepped
in
> > to "save the day"... Much more difficult to track down they way it is
> > currently implemented. We were on the phone with Microsoft for over 8
> > hours
> > over the past two days on this particular problem and they didn't come
> > across the solution - we had to find it and tell them about it.
> >
> > If you have SQL Server on a Windows 2003 Server with SP1, then I'd
suggest
> > setting the registry setting referenced in the knowledge based article,
> > especially since it's highly likely that your SQL Server is protected
from
> > outside connections to begin with.
> >
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> > Add DWORD: SynAttackProtect, value 0
> >
> > I'm mainly just venting...but it's ludicrous to have this sort of
> > 'feature'
> > implemented the way it is. Security needs to be a focus, but goodness
> > sakes
> > you need to have some common sense about it. What's the point of
dropping
> > 'some' packets if it's a suspected DOS attack? They might have their
> > reasons, but there is no reason to not have a log entry stating that
they
> > intentionally dropped network traffic. A simple "Suspected
> > denial-of-service attack detected, taking corrective action" would have
> > saved many hours of work.
> >
> > Time for a drink! :)
> >
> > Darian Miller
> >
> >
> >
> > darian
> > @.
> > darianmiller
> > .com
> >
> > "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> > news:%23EMfUSHbFHA.720@.TK2MSFTNGP15.phx.gbl...
> >> Hi
> >>
> >> Darian, how busy was your SQL Server to have this problem?
> >>
> >> 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/
> >>
> >> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> >> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> >> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this
one
> >> > just
> >> > hit us pretty good:
> >> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> >> >
> >> > Darian Miller
> >> >
> >> >
> >> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> >> > news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> >> >> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
> >> >> fixes
> >> >> it. Does anyone know more or a KB article ?
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>|||So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
> http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> > Heard there are issues with AWE and Windows 2003 and SP1 for Windows
fixes
> > it. Does anyone know more or a KB article ?
> >
> >
>|||Actually, a PAE fix for Win2K3 has also been released as part of a Security
Hotfix Critical Update:
Microsoft Security Bulletin MS04-032
Security Update for Microsoft Windows (840987)
http://www.microsoft.com/technet/security/bulletin/ms04-032.mspx
Sincerely,
Anthony Thomas
--
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
> http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> > Heard there are issues with AWE and Windows 2003 and SP1 for Windows
fixes
> > it. Does anyone know more or a KB article ?
> >
> >
>|||The issues with w2k3 at very small compared to NT 4.0 and w2k.
We found that most of the 'issues' with w2k3 are NT 4.0 MCSE's not
understanding security.
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/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
> So with all these issues with Win2K3, what does MS have to say ? Do
> companies move forward on Win2K3 ?
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
>> Here are a few:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
>> Adrian
>>
>> "Hassan" <fatima_ja@.hotmail.com> wrote in message
>> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>> > Heard there are issues with AWE and Windows 2003 and SP1 for Windows
> fixes
>> > it. Does anyone know more or a KB article ?
>> >
>> >
>>
>
Any known issues with AWE and Windows 2003
Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
it. Does anyone know more or a KB article ?
I am not sure, but we are currently experinceing performance issues
since going to SP1. See my post in this group, Too Much RAM SQL Server
2000?
|||Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one just
hit us pretty good:
http://support.microsoft.com/default...b;en-us;899599
Darian Miller
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>
|||Hi
Darian, how busy was your SQL Server to have this problem?
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/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> hit us pretty good:
> http://support.microsoft.com/default...b;en-us;899599
> Darian Miller
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>
|||Here are a few:
http://support.microsoft.com/default...b;en-us;895575
http://support.microsoft.com/default...b;en-us;838765
Adrian
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>
|||So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...[vbcol=seagreen]
> Here are a few:
> http://support.microsoft.com/default...b;en-us;895575
> http://support.microsoft.com/default...b;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes
>
|||Actually, a PAE fix for Win2K3 has also been released as part of a Security
Hotfix Critical Update:
Microsoft Security Bulletin MS04-032
Security Update for Microsoft Windows (840987)
http://www.microsoft.com/technet/sec.../ms04-032.mspx
Sincerely,
Anthony Thomas
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...[vbcol=seagreen]
> Here are a few:
> http://support.microsoft.com/default...b;en-us;895575
> http://support.microsoft.com/default...b;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes
>
|||The issues with w2k3 at very small compared to NT 4.0 and w2k.
We found that most of the 'issues' with w2k3 are NT 4.0 MCSE's not
understanding security.
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/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
> So with all these issues with Win2K3, what does MS have to say ? Do
> companies move forward on Win2K3 ?
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> fixes
>
it. Does anyone know more or a KB article ?
I am not sure, but we are currently experinceing performance issues
since going to SP1. See my post in this group, Too Much RAM SQL Server
2000?
|||Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one just
hit us pretty good:
http://support.microsoft.com/default...b;en-us;899599
Darian Miller
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>
|||Hi
Darian, how busy was your SQL Server to have this problem?
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/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> hit us pretty good:
> http://support.microsoft.com/default...b;en-us;899599
> Darian Miller
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>
|||Here are a few:
http://support.microsoft.com/default...b;en-us;895575
http://support.microsoft.com/default...b;en-us;838765
Adrian
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>
|||So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...[vbcol=seagreen]
> Here are a few:
> http://support.microsoft.com/default...b;en-us;895575
> http://support.microsoft.com/default...b;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes
>
|||Actually, a PAE fix for Win2K3 has also been released as part of a Security
Hotfix Critical Update:
Microsoft Security Bulletin MS04-032
Security Update for Microsoft Windows (840987)
http://www.microsoft.com/technet/sec.../ms04-032.mspx
Sincerely,
Anthony Thomas
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...[vbcol=seagreen]
> Here are a few:
> http://support.microsoft.com/default...b;en-us;895575
> http://support.microsoft.com/default...b;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes
>
|||The issues with w2k3 at very small compared to NT 4.0 and w2k.
We found that most of the 'issues' with w2k3 are NT 4.0 MCSE's not
understanding security.
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/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
> So with all these issues with Win2K3, what does MS have to say ? Do
> companies move forward on Win2K3 ?
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> fixes
>
Any issues with using Noton Ghost with SQL Server?
I seem to recall from reading an article that there are issues with backing
up hard drives with Norton Ghost with SQL Server or MSDE installed.
However, I can't seem to find the KB article. Can someone confirm this with
resource articles?
Thanks in advance.The issue is most likely if your trying to do this while SQL Server is
running. If it's not running I don't see why you couldn't ghost it but that
is not a very efficient way to backup sql server.
--
Andrew J. Kelly
SQL Server MVP
"wym" <wym@.sympatico.ca> wrote in message
news:Doxub.9670$iT4.1045873@.news20.bellglobal.com...
> I seem to recall from reading an article that there are issues with
backing
> up hard drives with Norton Ghost with SQL Server or MSDE installed.
> However, I can't seem to find the KB article. Can someone confirm this
with
> resource articles?
> Thanks in advance.
>|||Thank you for the reply. Actually, the question came up because our
application uses MSDE 2000 and it is set to autostart when OS starts. When
customers backup with with Ghost, I doubt they will turn off MSDE (they will
have to search for it since SQL Server Service Manager is not in the tray).
If they reinstall the image, will there be any issues with MSDE or the
databases?
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OvHVoHjrDHA.2408@.tk2msftngp13.phx.gbl...
> The issue is most likely if your trying to do this while SQL Server is
> running. If it's not running I don't see why you couldn't ghost it but
that
> is not a very efficient way to backup sql server.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "wym" <wym@.sympatico.ca> wrote in message
> news:Doxub.9670$iT4.1045873@.news20.bellglobal.com...
> > I seem to recall from reading an article that there are issues with
> backing
> > up hard drives with Norton Ghost with SQL Server or MSDE installed.
> > However, I can't seem to find the KB article. Can someone confirm this
> with
> > resource articles?
> >
> > Thanks in advance.
> >
> >
>|||You can't guarantee a consistent database by backing up at the file level
when sql server is running. I would look into writing some simple BACKUP
and RESTORE scripts. They work the same on MSDE as they do on any edition
and are the correct way to backup the databases.
--
Andrew J. Kelly
SQL Server MVP
"wym" <wym@.sympatico.ca> wrote in message
news:HKzub.10072$iT4.1118306@.news20.bellglobal.com...
> Thank you for the reply. Actually, the question came up because our
> application uses MSDE 2000 and it is set to autostart when OS starts.
When
> customers backup with with Ghost, I doubt they will turn off MSDE (they
will
> have to search for it since SQL Server Service Manager is not in the
tray).
> If they reinstall the image, will there be any issues with MSDE or the
> databases?
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:OvHVoHjrDHA.2408@.tk2msftngp13.phx.gbl...
> > The issue is most likely if your trying to do this while SQL Server is
> > running. If it's not running I don't see why you couldn't ghost it but
> that
> > is not a very efficient way to backup sql server.
> >
> > --
> >
> > Andrew J. Kelly
> > SQL Server MVP
> >
> >
> > "wym" <wym@.sympatico.ca> wrote in message
> > news:Doxub.9670$iT4.1045873@.news20.bellglobal.com...
> > > I seem to recall from reading an article that there are issues with
> > backing
> > > up hard drives with Norton Ghost with SQL Server or MSDE installed.
> > > However, I can't seem to find the KB article. Can someone confirm
this
> > with
> > > resource articles?
> > >
> > > Thanks in advance.
> > >
> > >
> >
> >
>
up hard drives with Norton Ghost with SQL Server or MSDE installed.
However, I can't seem to find the KB article. Can someone confirm this with
resource articles?
Thanks in advance.The issue is most likely if your trying to do this while SQL Server is
running. If it's not running I don't see why you couldn't ghost it but that
is not a very efficient way to backup sql server.
--
Andrew J. Kelly
SQL Server MVP
"wym" <wym@.sympatico.ca> wrote in message
news:Doxub.9670$iT4.1045873@.news20.bellglobal.com...
> I seem to recall from reading an article that there are issues with
backing
> up hard drives with Norton Ghost with SQL Server or MSDE installed.
> However, I can't seem to find the KB article. Can someone confirm this
with
> resource articles?
> Thanks in advance.
>|||Thank you for the reply. Actually, the question came up because our
application uses MSDE 2000 and it is set to autostart when OS starts. When
customers backup with with Ghost, I doubt they will turn off MSDE (they will
have to search for it since SQL Server Service Manager is not in the tray).
If they reinstall the image, will there be any issues with MSDE or the
databases?
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OvHVoHjrDHA.2408@.tk2msftngp13.phx.gbl...
> The issue is most likely if your trying to do this while SQL Server is
> running. If it's not running I don't see why you couldn't ghost it but
that
> is not a very efficient way to backup sql server.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "wym" <wym@.sympatico.ca> wrote in message
> news:Doxub.9670$iT4.1045873@.news20.bellglobal.com...
> > I seem to recall from reading an article that there are issues with
> backing
> > up hard drives with Norton Ghost with SQL Server or MSDE installed.
> > However, I can't seem to find the KB article. Can someone confirm this
> with
> > resource articles?
> >
> > Thanks in advance.
> >
> >
>|||You can't guarantee a consistent database by backing up at the file level
when sql server is running. I would look into writing some simple BACKUP
and RESTORE scripts. They work the same on MSDE as they do on any edition
and are the correct way to backup the databases.
--
Andrew J. Kelly
SQL Server MVP
"wym" <wym@.sympatico.ca> wrote in message
news:HKzub.10072$iT4.1118306@.news20.bellglobal.com...
> Thank you for the reply. Actually, the question came up because our
> application uses MSDE 2000 and it is set to autostart when OS starts.
When
> customers backup with with Ghost, I doubt they will turn off MSDE (they
will
> have to search for it since SQL Server Service Manager is not in the
tray).
> If they reinstall the image, will there be any issues with MSDE or the
> databases?
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:OvHVoHjrDHA.2408@.tk2msftngp13.phx.gbl...
> > The issue is most likely if your trying to do this while SQL Server is
> > running. If it's not running I don't see why you couldn't ghost it but
> that
> > is not a very efficient way to backup sql server.
> >
> > --
> >
> > Andrew J. Kelly
> > SQL Server MVP
> >
> >
> > "wym" <wym@.sympatico.ca> wrote in message
> > news:Doxub.9670$iT4.1045873@.news20.bellglobal.com...
> > > I seem to recall from reading an article that there are issues with
> > backing
> > > up hard drives with Norton Ghost with SQL Server or MSDE installed.
> > > However, I can't seem to find the KB article. Can someone confirm
this
> > with
> > > resource articles?
> > >
> > > Thanks in advance.
> > >
> > >
> >
> >
>
2012年2月13日星期一
any article regarding differences between SQL2K and Yukon
any article regarding differences between SQL2K and YukonThere is almost none public info on Yukon yet, as those who has access to it are under
non-disclosure agreements. Your best bet it probably to search the net and try to find out what has
"leaked" until now.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:upjwehGgDHA.944@.TK2MSFTNGP11.phx.gbl...
>|||Of the information that has been made public, the biggest change appears to
be the ability to write stored procs, UDF's and triggers using any .NET
language. This could potentially alter, drastically, how coding is done at
the database level. T-SQL is also being beefed up significantly.
J.R.
Largo SQL Tools
The Finest Collection of SQL Tools Available
http://www.largosqltools.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:upjwehGgDHA.944@.TK2MSFTNGP11.phx.gbl...
>|||> language. This could potentially alter, drastically, how coding is done
at
> the database level.
I guess the key is 'could potentially'. Some other DBMSs have introduced
similar features. As far as I can tell from working with DBAs of those
products, the database level coding doesn't seem to have been altered that
drastically. Perhaps, it's just the DBA crowd I hang out with :-)
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Largo SQL Tools" <nospam@.yahoo.com> wrote in message
news:u0jRvfHgDHA.3616@.TK2MSFTNGP11.phx.gbl...
> Of the information that has been made public, the biggest change appears
to
> be the ability to write stored procs, UDF's and triggers using any .NET
> language. This could potentially alter, drastically, how coding is done
at
> the database level. T-SQL is also being beefed up significantly.
> J.R.
> Largo SQL Tools
> The Finest Collection of SQL Tools Available
> http://www.largosqltools.com
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:upjwehGgDHA.944@.TK2MSFTNGP11.phx.gbl...
> >
> >
>
non-disclosure agreements. Your best bet it probably to search the net and try to find out what has
"leaked" until now.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:upjwehGgDHA.944@.TK2MSFTNGP11.phx.gbl...
>|||Of the information that has been made public, the biggest change appears to
be the ability to write stored procs, UDF's and triggers using any .NET
language. This could potentially alter, drastically, how coding is done at
the database level. T-SQL is also being beefed up significantly.
J.R.
Largo SQL Tools
The Finest Collection of SQL Tools Available
http://www.largosqltools.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:upjwehGgDHA.944@.TK2MSFTNGP11.phx.gbl...
>|||> language. This could potentially alter, drastically, how coding is done
at
> the database level.
I guess the key is 'could potentially'. Some other DBMSs have introduced
similar features. As far as I can tell from working with DBAs of those
products, the database level coding doesn't seem to have been altered that
drastically. Perhaps, it's just the DBA crowd I hang out with :-)
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Largo SQL Tools" <nospam@.yahoo.com> wrote in message
news:u0jRvfHgDHA.3616@.TK2MSFTNGP11.phx.gbl...
> Of the information that has been made public, the biggest change appears
to
> be the ability to write stored procs, UDF's and triggers using any .NET
> language. This could potentially alter, drastically, how coding is done
at
> the database level. T-SQL is also being beefed up significantly.
> J.R.
> Largo SQL Tools
> The Finest Collection of SQL Tools Available
> http://www.largosqltools.com
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:upjwehGgDHA.944@.TK2MSFTNGP11.phx.gbl...
> >
> >
>
Any article about Analysis Service
Hi,
Have there articles about the difference between Analysis Servcie 2000 and
2005?ad wrote:
> Hi,
> Have there articles about the difference between Analysis Servcie 2000 and
> 2005?
You can start here:
http://www.microsoft.com/sql/solutions/bi/default.mspx
--
David Portas
SQL Server MVP
--
Have there articles about the difference between Analysis Servcie 2000 and
2005?ad wrote:
> Hi,
> Have there articles about the difference between Analysis Servcie 2000 and
> 2005?
You can start here:
http://www.microsoft.com/sql/solutions/bi/default.mspx
--
David Portas
SQL Server MVP
--
Any article about Analysis Service
Hi,
Have there articles about the difference between Analysis Servcie 2000 and
2005?
ad wrote:
> Hi,
> Have there articles about the difference between Analysis Servcie 2000 and
> 2005?
You can start here:
http://www.microsoft.com/sql/solutions/bi/default.mspx
David Portas
SQL Server MVP
Have there articles about the difference between Analysis Servcie 2000 and
2005?
ad wrote:
> Hi,
> Have there articles about the difference between Analysis Servcie 2000 and
> 2005?
You can start here:
http://www.microsoft.com/sql/solutions/bi/default.mspx
David Portas
SQL Server MVP
Any article about Analysis Service
Hi,
Have there articles about the difference between Analysis Servcie 2000 and
2005?ad wrote:
> Hi,
> Have there articles about the difference between Analysis Servcie 2000 and
> 2005?
You can start here:
http://www.microsoft.com/sql/solutions/bi/default.mspx
David Portas
SQL Server MVP
--
Have there articles about the difference between Analysis Servcie 2000 and
2005?ad wrote:
> Hi,
> Have there articles about the difference between Analysis Servcie 2000 and
> 2005?
You can start here:
http://www.microsoft.com/sql/solutions/bi/default.mspx
David Portas
SQL Server MVP
--
2012年2月11日星期六
ANSI-Style Joins & Old-Style Joins!
I came across an article which states the differences between
ANSI-style JOINs & old-style JOINs. This was one among them:
---
The ANSI-style JOIN supports query constructions which the old-style
JOIN syntax does not support.
---
What does the above mean especially the term "query constructions"?
Thanks,
ArpanOne example is that the old-style syntax only directly supports joins
based on equality. In the ANSI syntax we can write:
SELECT *
FROM A
LEFT OUTER JOIN B
ON A.col1 BETWEEN B.col2 AND B.col3
To do that without the OUTER JOIN operator would require an inner join
and a UNION.
David Portas
SQL Server MVP
--|||The *= syntax was equality only and a table could appear only once as
eitehr preserved or unpreserved. Google aroudn for one of my olds
postings on how the outer works|||On 30 Jul 2005 01:38:32 -0700, Arpan wrote:
>I came across an article which states the differences between
>ANSI-style JOINs & old-style JOINs. This was one among them:
>---
>The ANSI-style JOIN supports query constructions which the old-style
>JOIN syntax does not support.
>---
>What does the above mean especially the term "query constructions"?
>Thanks,
>Arpan
Hi Arpan,
In addition to the answers provided by David and Celko, here are two
more examples:
1. The ANSI-style permits you to write
SELECT something
FROM A
LEFT OUTER JOIN B
ON B.col1 = A.col1
AND B.col2 IS NULL
or
SELECT something
FROM A
LEFT OUTER JOIN B
ON B.col1 = A.col1
WHERE B.col2 IS NULL
And the results of these two are quite different. With the old-style
joins, they'd be the same:
SELECT something
FROM A, B
WHERE B.col1 =* A.col1
AND B.col2 IS NULL
And which of the two possible result sets you'd get depends on how the
programmers decided to implement this. From what I've heard, Oracle's
result set would be different from SQL Server's.
2. FULL OUTER JOIN. This is not available in old-style.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)
ANSI-style JOINs & old-style JOINs. This was one among them:
---
The ANSI-style JOIN supports query constructions which the old-style
JOIN syntax does not support.
---
What does the above mean especially the term "query constructions"?
Thanks,
ArpanOne example is that the old-style syntax only directly supports joins
based on equality. In the ANSI syntax we can write:
SELECT *
FROM A
LEFT OUTER JOIN B
ON A.col1 BETWEEN B.col2 AND B.col3
To do that without the OUTER JOIN operator would require an inner join
and a UNION.
David Portas
SQL Server MVP
--|||The *= syntax was equality only and a table could appear only once as
eitehr preserved or unpreserved. Google aroudn for one of my olds
postings on how the outer works|||On 30 Jul 2005 01:38:32 -0700, Arpan wrote:
>I came across an article which states the differences between
>ANSI-style JOINs & old-style JOINs. This was one among them:
>---
>The ANSI-style JOIN supports query constructions which the old-style
>JOIN syntax does not support.
>---
>What does the above mean especially the term "query constructions"?
>Thanks,
>Arpan
Hi Arpan,
In addition to the answers provided by David and Celko, here are two
more examples:
1. The ANSI-style permits you to write
SELECT something
FROM A
LEFT OUTER JOIN B
ON B.col1 = A.col1
AND B.col2 IS NULL
or
SELECT something
FROM A
LEFT OUTER JOIN B
ON B.col1 = A.col1
WHERE B.col2 IS NULL
And the results of these two are quite different. With the old-style
joins, they'd be the same:
SELECT something
FROM A, B
WHERE B.col1 =* A.col1
AND B.col2 IS NULL
And which of the two possible result sets you'd get depends on how the
programmers decided to implement this. From what I've heard, Oracle's
result set would be different from SQL Server's.
2. FULL OUTER JOIN. This is not available in old-style.
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)
订阅：
博文 (Atom)