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 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!
>
>

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!
>
>

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!
>
>

Ansi Nulls and quoted identified

Hello everyone,

SQL Server 2000. I have a database in which there are several objects
which have ansi nuls and quoted identifier turned ON. Is there a way I
can generate a script which:
(1) Can identify all objects within the database that have those two
properties turned ON and
(2) Change the properties for these objects and turn the ansi nulls and
quoted identifier OFF for those objects.

I am trying to avoid going throuh gazillions of objects and manually
doing this.

Thanks for any help.

Raziq.

*** Sent via Developersdex http://www.developersdex.com ***Are you sure you want to do this? It is STRONGLY recommended that both
these options always be set ON. Changing these options will break
indexed views and other code that uses them. Only use the OFF setting
for legacy code where you don't have another option.

These settings are persisted with views, procs, etc when you create
them. I think the easiest way to change them is to use Enterprise
Manager to script the database, then search and replace in the
resulting script.

--
David Portas
SQL Server MVP
--|||To identify the objects, use something like this:

SELECT name, xtype,
OBJECTPROPERTY(id,'ExecIsAnsiNullsOn'),
OBJECTPROPERTY(id,'ExecIsQuotedIdentOn')
FROM sysobjects WHERE xtype IN ('P','TR','V','IF','FN','TF')

To change these properties, you should re-create those objects using
ALTER PROCEDURE / ALTER VIEW / ALTER FUNCTION.

If you do not want to do this one by one (and if you feel particularly
lucky today, as to change an undocumented column in a system table), I
will give you a hint: bits 30 and 29 (bit mask: 0x60000000) of the
status column in the sysobjects table.

Of course, changing a system table is a bad idea (it may cause data
loss or may prevent an instance of SQL Server from running). Changing
an undocumented column of a system table is an even worse idea !

Razvan|||If you do not want to do this one by one and if you feel particularly
SUICIDAL today...

Razvan, have you actually tested out your implied suggestion? I would
NEVER recommend anyone to attempt to modify system tables directly. In
this case it is completely unnecessary.

--
David Portas
SQL Server MVP
--|||Yes, I have tested it (to turn ON those properties) and found no
side-effects.

Razvan|||Correction: I have found a side-effect:

If the procedure was executed (so the execution plan is in the
procedure cache), the change does not take effect immediately (i.e. the
old execution plan remains in the cache, until the server is restarted
or DBCC FREEPROCCACHE is executed).

However, I do not recommend this method. It is undocumented and,
therefore, not reliable. You should script the objects using Enterprise
Manager and use ALTER PROCEDURE / VIEW / FUNCTION.

Razvan|||>> turn the ansi nulls and quoted identifier OFF for those objects. <<

Why do you wish to destroy portability and data integrity? The only
reasons I can imagine are (1) ignorance of SQL (2) deliberate
sabotage. You ought ot be bringin the database into Standards
confromance, not out of it!!|||The application I am working with is designed to work with objects with
those two options turned off.

Raziq.

*** Sent via Developersdex http://www.developersdex.com ***|||>> The application I am working with is designed to work with objects with those two options turned off. <<

This is like saying that your accounting package believes that 2 + 2 =
5 so you want to change the spreadsheets and the rest of the world.

You need to re-write your code immediately, don't you? Then you need
a data audit to find out what is messed up in the Database, all of your
reports, etc.|||Right. Why don't I rewrite the application code, and then when the
application starts acting up, and we have to call the vendor, and they
say: "sorry, but this is not our code and so we can't help you." I can
tell them no problem, because I have been working on reinventing the
wheel and will be making a killing selling that new wheel and won't need
this DBA job.

One more thing, I don't think leaving the above mentioned options off
amounts to a logical inconsistency i.e. 2+2=5.

*** Sent via Developersdex http://www.developersdex.com ***|||Razvan Socol (rsocol@.gmail.com) writes:
> Yes, I have tested it (to turn ON those properties) and found no
> side-effects.

Hm, if you have a procedure that reads:

CREATE PROCEDURE ill_will AS
PRINT "Hej!"

and it was loaded with QUOTED_IDENTIFIER off, and you change it to ON,
I bet you see have side effects!

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Raziq Shekha (raziq_shekha@.anadarko.com) writes:
> One more thing, I don't think leaving the above mentioned options off
> amounts to a logical inconsistency i.e. 2+2=5.

Oh, you don't know Joe Celko I see. In his world, 2+2=5, running with
ANSI_NULLS off or calling a table row for a record is all equally
wrong.

Then again, what could you expect from someone who thinks that IDENTITY
in SQL Server has something to do with physical location?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||>> Why don't I rewrite the application code, and then when the application starts acting up, and we have to call the vendor, and they say: "sorry, but this is not our code and so we can't help you."<<

It is already acting up and you need to replace it ASAP. Read a nice
article at CIO magazine's website entitled "Bound to Fail" about the
falure of a legacy system that everyone could see and nobody wanted to
change.

If you are in the United States, where we have 1 lawyer for every 400
people, you should be suing this vendor.

>> I don't think leaving the above mentioned options off amounts to a logical inconsistency i.e. 2+2=5.<<

I guess that you are smarter than ANSI, smarter than ISO, smarter than
any other SQL product staff, etc. Do you exchange data with other SQL
products? Do you move data from one table to another within the system
itself? Do you plan on doing these things later? Do you want to have
a Data Warehouse someday?|||--CELKO-- (jcelko212@.earthlink.net) writes:
> It is already acting up and you need to replace it ASAP. Read a nice
> article at CIO magazine's website entitled "Bound to Fail" about the
> falure of a legacy system that everyone could see and nobody wanted to
> change.
> If you are in the United States, where we have 1 lawyer for every 400
> people, you should be suing this vendor.

So the system I work with has ANSI_NULLS off as well. I don't hear of
any customers suing us... As for why we have it, well, this is a system
that started its life in 1992, when SQL Server had nothing else to
offer.

>>> I don't think leaving the above mentioned options off amounts to a
>>> logical inconsistency i.e. 2+2=5.<<
> I guess that you are smarter than ANSI, smarter than ISO, smarter than
> any other SQL product staff, etc.

Please take your insults somewhere else. Raziq has an application, and
provided the settings which are appropriate for the system, the
application performs his job, and he is happy with it.

One thing I can tell: he is smarter than you are, because he knows what
he can change with his system and you don't.

> Do you exchange data with other SQL products? Do you move data from one
> table to another within the system itself? Do you plan on doing these
> things later? Do you want to have a Data Warehouse someday?

And how would any of that be affected by the fact that the application
internally uses NULL in the wrong way, or quotes it string literals with
" instead '?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||>> And how would any of that be affected by the fact that the application
internally uses NULL in the wrong way, or quotes it string literals
with
" instead '? <<

IN() predicates will not work right when data is moved to the DW or to
a table with the right settings. Some of the other calculations can be
wrong.

Code will reference a column and not a literal when it is moved. My
favorite was "date" versus 'date' in one system I had to audit where
the poorly names column was a string.

Since 80% or mroe of the cost of an application is in maintaining it,
you want it to be immediately undestood by the next guy to take over
the job. Things as minor as inconsistent naming conventions can add
8-12% to the cost. What do you think that syntax that changes from
place within the application will cost?|||Thank you Erland Sommarskog. I guess Celko does not realize that there
is life outside a database and IT. Celko, you might want to look up the
following words:

1) Dating
2) dancing
3) relaxing
4) taking it easy
5) anal

And no, don't look these words up on IT.com.

Asif.

*** Sent via Developersdex http://www.developersdex.com ***|||>> Why do you wish to destroy portability and data integrity? The only
reasons I can imagine are (1) ignorance of SQL (2) deliberate
sabotage. <<

an excerpt from Real Life Databases 100 (as opposed to theoretical
databases in a perfect world):
Most software vendors discourage portability, and the reason is
obvious: they want to retain their customers, so they don't want to
make porting out of their products easy.|||--CELKO-- (jcelko212@.earthlink.net) writes:
> IN() predicates will not work right when data is moved to the DW or to
> a table with the right settings. Some of the other calculations can be
> wrong.

Presumably the DW is another database. And very likely in Analysis
Services. What the ANSI_NULLS setting is in the source system is
irrelevant.

> Code will reference a column and not a literal when it is moved. My
> favorite was "date" versus 'date' in one system I had to audit where
> the poorly names column was a string.

We already knows the answer to that one: vendor mandates which setting
that should be used.

By the same reasoning, you should never denote your tables as "Order
Details" in the code, but use [Order Details], because the code may be
loaded with QUOTED_IDENTIFIER off. (And, alas, this is the default with OSQL
and Enterprise Manager.)

> Since 80% or mroe of the cost of an application is in maintaining it,
> you want it to be immediately undestood by the next guy to take over
> the job. Things as minor as inconsistent naming conventions can add
> 8-12% to the cost. What do you think that syntax that changes from
> place within the application will cost?

That's Raziq's vendor's problem. Assume that they started to write
their application in 1992, like we did. Then " to quote strings was
a fair game in SQL Server. Guess what it would cost them to fix that?
Compare that with mandating the application to be installed with
QUOTED_IDENTIFIER off.

As it happens, our source code also uses both " and ' to delimit strings.
However, I've augmented our load tool to take replace all " with '. But
that is not really a trivial operation, and I have full understanding
for those who prefer to leave it as it is.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp