显示标签为“customers”的博文。显示所有博文
显示标签为“customers”的博文。显示所有博文

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

2012年2月18日星期六

Any help?

I am having a issue with a customers server. the specs are:
2003 server
sql 6.5
log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb

In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.

The past day or so these errors are showing up:

Any help?

Event Type:Error
Event Source:MSSQLServer
Event Category:(2)
Event ID:17060
Date:8/4/2006
Time:7:51:20 AM
User:N/A
Computer:AUX-SERVER
Description:
The description for Event ID ( 17060 ) in Source ( MSSQLServer ) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve this
description; see Help and Support for details. The following
information is part of the event: Error : 701, Severity: 17, State: 2,
There is insufficient system memory to run this query..
Data:
0000: bd 02 00 00 11 00 00 00 ......
0008: 00 00 00 00 07 00 00 00 ......
0010: 6d 61 73 74 65 72 00 master.tommy2 (tommy2@.ptd.net) writes:

Quote:

Originally Posted by

I am having a issue with a customers server. the specs are:
2003 server
sql 6.5


SQL 6.5 on SQL 2003? I didn't even think that was possible. Has the
OS been upgraded from Win 2000?

Quote:

Originally Posted by

log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb
>
In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.


Try running this from a query window:

sp_spaceused syslogs, true

I would be interested in seeing the output, at least if the problem
persists. It could also be interested in seeing the output from sp_helpdb.

Quote:

Originally Posted by

The past day or so these errors are showing up:
>
Any help?
>...
There is insufficient system memory to run this query..


That could be about anything. Have you checked the SQL Server Errorlog?

Don't know what experience you have of SQL 6.5, but in case you don't
know: this is a very different architecture from later releases.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||This database used to run on NT 4.0 6 months ago. They moved it to a
win2003 server. It ran fine since being moved up till last week.

Erland Sommarskog wrote:

Quote:

Originally Posted by

tommy2 (tommy2@.ptd.net) writes:

Quote:

Originally Posted by

I am having a issue with a customers server. the specs are:
2003 server
sql 6.5


>
SQL 6.5 on SQL 2003? I didn't even think that was possible. Has the
OS been upgraded from Win 2000?
>

Quote:

Originally Posted by

log file size is 1998MB (customer increased this 2 times this week) Log
space avail:600mb

In EM i try and truncate the log file... but the free space never
increases. Also there is no maint. plan on this database. When I try
and create one it advises against creating one with databases over
400MB.


>
Try running this from a query window:
>
sp_spaceused syslogs, true
>
I would be interested in seeing the output, at least if the problem
persists. It could also be interested in seeing the output from sp_helpdb.
>

Quote:

Originally Posted by

The past day or so these errors are showing up:

Any help?
...
There is insufficient system memory to run this query..


>
That could be about anything. Have you checked the SQL Server Errorlog?
>
Don't know what experience you have of SQL 6.5, but in case you don't
know: this is a very different architecture from later releases.
>
>
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
>
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

|||tommy2 (tommy2@.ptd.net) writes:

Quote:

Originally Posted by

This database used to run on NT 4.0 6 months ago. They moved it to a
win2003 server. It ran fine since being moved up till last week.


Wonder if that was just pure luck? I happened to look at
http://www.microsoft.com/sql/howtobuy/sqlonvista.mspx today. It does
not talk about 6.5 on Win2003...

Anyway, if their transaction log grows in size, there is some activity
going on, but what I cannot say from a distance. Did you try running
any of:

Quote:

Originally Posted by

Quote:

Originally Posted by

>Try running this from a query window:
>>
> sp_spaceused syslogs, true
>>
>I would be interested in seeing the output, at least if the problem
>persists. It could also be interested in seeing the output from
>sp_helpdb.


--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Any harm in adding a primary key...

after my table has been created and populated with data?
I have an identity column (named 'CID') on my customers table. This
value is often used in my queries and I'd like to take advantage of a
clustered
index (since none currently exist on the table).
Will making this column a primary key have any adverse effects? There are
currently 3,000 rows in the table and it's 10 columns wide."Eric" <Eric@.discussions.microsoft.com> wrote in message
news:D344667A-6AF7-42E1-B907-8C0C945D6C2E@.microsoft.com...
> after my table has been created and populated with data?
> I have an identity column (named 'CID') on my customers table. This
> value is often used in my queries and I'd like to take advantage of a
> clustered
> index (since none currently exist on the table).
> Will making this column a primary key have any adverse effects? There are
> currently 3,000 rows in the table and it's 10 columns wide.
1. Why wasn't the table created with a PK in place already.
2. Just because you make it a primary key, doesn't make it a clustered
index. When you create a Primary Key in SQL Server it will choose Clustered
by default, but it could be non-clustered if you tell it to.
So to answer your question, you could just as easily create a clustered
index on that CID column as create a Primary key on it. Should it be the
Primary Key? <shrug> Who knows, you didn't post DDL, so it's hard to say.
Since it is not a PK, I will assume that you are not using FK constraints
either. This could be a very serious issue in your database. The PK and FK
constraints are there to ensure the relational integrity of your data. If
you have your customers table as described above, and an Orders table.
Without these constraints, there is really nothing stopping someone from
adding Orders to your database that don't map to any Customer, or delete
Customers who may have orders pending for shipment.
You should really finish modelling your system and include the PK and FK
constraints, and any other constraints necessary to ensure the various
integreties of your system (entity integrity, relational integrity and
domain integrity).
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||1) I have no idea as I did not design the db.
2) I wanted to take advantage of using a clustered index.
I understand the importance of using the PK/FK for integrity. We are
planning a db redesign in the near future, but for the time being, I just
wanted to add the clustered index via a PK for performance purposes.
"Rick Sawtell" wrote:

> "Eric" <Eric@.discussions.microsoft.com> wrote in message
> news:D344667A-6AF7-42E1-B907-8C0C945D6C2E@.microsoft.com...
>
> 1. Why wasn't the table created with a PK in place already.
> 2. Just because you make it a primary key, doesn't make it a clustered
> index. When you create a Primary Key in SQL Server it will choose Cluster
ed
> by default, but it could be non-clustered if you tell it to.
>
> So to answer your question, you could just as easily create a clustered
> index on that CID column as create a Primary key on it. Should it be the
> Primary Key? <shrug> Who knows, you didn't post DDL, so it's hard to say
.
> Since it is not a PK, I will assume that you are not using FK constraints
> either. This could be a very serious issue in your database. The PK and
FK
> constraints are there to ensure the relational integrity of your data. I
f
> you have your customers table as described above, and an Orders table.
> Without these constraints, there is really nothing stopping someone from
> adding Orders to your database that don't map to any Customer, or delete
> Customers who may have orders pending for shipment.
> You should really finish modelling your system and include the PK and FK
> constraints, and any other constraints necessary to ensure the various
> integreties of your system (entity integrity, relational integrity and
> domain integrity).
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>|||"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:7585798D-DD21-4D84-9135-A21EB8F786DA@.microsoft.com...
> 1) I have no idea as I did not design the db.
> 2) I wanted to take advantage of using a clustered index.
> I understand the importance of using the PK/FK for integrity. We are
> planning a db redesign in the near future, but for the time being, I just
> wanted to add the clustered index via a PK for performance purposes.
> "Rick Sawtell" wrote:
>
Then by all means create a PK and specify Clustered.
ALTER TABLE dbo.Customers
ADD CONSTRAINT PK_Customers_CID
PRIMARY KEY CLUSTERED (CID)
To get even better performance, you should also create indexes on what will
eventually be your FK columns, so if you had an Orders table, you might do
the following.
CREATE NONCLUSTERED INDEX IX_Orders_CID ON dbo.Customers (CID)
Rick Sawtell
MCT, MCSD, MCDBA|||Eric wrote:
> 1) I have no idea as I did not design the db.
> 2) I wanted to take advantage of using a clustered index.
> I understand the importance of using the PK/FK for integrity. We are
> planning a db redesign in the near future, but for the time being, I just
> wanted to add the clustered index via a PK for performance purposes.
> "Rick Sawtell" wrote:
>
Your question is whether adding the cluster key could do any harm. If
your database is this weakly designed then I wouldn't take anything for
granted. Maybe they left out an ORDER BY on a cursor somewhere and
adding an extra index would cause some logic to fail. Test, test, test.
David Portas
SQL Server MVP
--|||David:
If you could please clarify the effect a cursor may have w/an omitted 'order
by' cluase. I'm using a cursor in only one instance on my db. I would like
to add a clustered index to one of my tables (Company.ID) but this table is
in fact included in my cursor statement. Appreciate your input.
"David Portas" wrote:

> Eric wrote:
> Your question is whether adding the cluster key could do any harm. If
> your database is this weakly designed then I wouldn't take anything for
> granted. Maybe they left out an ORDER BY on a cursor somewhere and
> adding an extra index would cause some logic to fail. Test, test, test.
> --
> David Portas
> SQL Server MVP
> --
>|||I'm not David, but:
Some developer seems to think that the order of rows returned from a SELECT
statement can be
determined by having a certain index in place, or some other physical attrib
ute of the table. That
is not true. The only way to guarantee that the result from a SELECT stateme
nt is ordered in any
certain way is to have ORDER BY. This is not exclusive to cursor operations,
btw.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:29804387-5EF8-434A-8BFA-D05A1303CBAE@.microsoft.com...
> David:
> If you could please clarify the effect a cursor may have w/an omitted 'ord
er
> by' cluase. I'm using a cursor in only one instance on my db. I would li
ke
> to add a clustered index to one of my tables (Company.ID) but this table i
s
> in fact included in my cursor statement. Appreciate your input.
> "David Portas" wrote:
>|||Eric wrote:
> David:
> If you could please clarify the effect a cursor may have w/an omitted 'ord
er
> by' cluase. I'm using a cursor in only one instance on my db. I would li
ke
> to add a clustered index to one of my tables (Company.ID) but this table i
s
> in fact included in my cursor statement. Appreciate your input.
> "David Portas" wrote:
>
If you write cursor code without specifying ORDER BY in the DECLARE
statement and if that cursor uses logic that assumes a particular
ordering to the data then it may break at some point if the execution
plan changes. This is made more likely if you create or drop indexes -
i.e. the assumed order of the cursor may change. Always specify ORDER
BY if the ordering is important to you.
If you avoid cursors and stick to set-based code you'll avoid this
potential problem. Most cursors are unnecessary and are written by
people who don't know SQL well enough to do any better.
David Portas
SQL Server MVP
--|||If CID is unique (and it must be unique since it is an identity column), and
there are no natural key candidates, then do make it the primary key. Every
table needs a primary key of some type.
http://www.aspfaq.com/show.asp?id=2504
Also, 3000 rows x 10 columns is practically nothing, and if it's being hit
frequently, SQL Server is probably keeping a complete in the buffer cache
anyway and reducing the need to read it from disk. It would not benefit from
a clustered index (although it wouldn't hurt).
http://msdn.microsoft.com/library/d...br />
1zu4.asp
http://msdn.microsoft.com/library/d...br />
3339.asp
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:D344667A-6AF7-42E1-B907-8C0C945D6C2E@.microsoft.com...
> after my table has been created and populated with data?
> I have an identity column (named 'CID') on my customers table. This
> value is often used in my queries and I'd like to take advantage of a
> clustered
> index (since none currently exist on the table).
> Will making this column a primary key have any adverse effects? There are
> currently 3,000 rows in the table and it's 10 columns wide.|||On Wed, 28 Dec 2005 08:25:05 -0800, "Eric"
<Eric@.discussions.microsoft.com> wrote:
>after my table has been created and populated with data?
No harm.

>I have an identity column (named 'CID') on my customers table. This
>value is often used in my queries and I'd like to take advantage of a
>clustered index (since none currently exist on the table).
PK is one thing, clustering is an option.
Alternatively clustering is one thing, PK is another.
But if you want to do both at once, go ahead.
Are there any other existing indexes? Creating a clustered index does
mean rewriting the table and rebuilding the other indexes.

>Will making this column a primary key have any adverse effects?
Only that it will then enforce uniqueness, can't have null values,
just the standard behaviors of a PK.

>There are
>currently 3,000 rows in the table and it's 10 columns wide.
Extremely modest by modern standards.
J.

2012年2月13日星期一

Any backup vendor can provide?

Some of my customers ask for backup their databases, mainly MSSQL & MS Exchange.
I search for any of backup vendor; there are 2 choices, service provider and software publisher. Service provider eliminates my technical support on backing up my clients databases:cool: ; software publisher offer a chance for me to create new business line:rolleyes: .
What would your gurus prefer and why?
Any admirable company you can name?I back up MSSQL using MSSQL backup procedures.
MS Exchange is not a database server, so I don't know the best way to back it up.|||Thanks blindman.
How about the servers are Windows-based, some are Linux-based?|||As Blindman says, the easiest and best way to back up SQL databases is by using the built-in backup utilities that come with SQL Server.

Your server support team might want to include SQL Server boxes as part of their backup routine, in which case there are various applications that typically use an Agent to backup SQL Server databases either at a database or filesystem level, e.g. Veritas, Legato, Litespeed.

Bottom line; you as a DBA should be in charge of your database backups.

Lempster|||I have the same issue. However, FreeBSD adds to my heterogeneous environment.|||I was sourcing for such a solution earlier. I gathered info from other forums and identified some data backup solutions targeting ISPs and web hosting businesses like ours. Heres a list which Ive evaluated:

1. NovaNet (www.novastor.com)
2. Ahsay (www.ahsay.com)
3. Storgrid (www.vembu.com)
4. RBS (www.remote-backup.com)

Only Storegrid and Ahsay are multi-platform. I was lured into NovaNet with its attractive look. However, once I tested it on my server, I was disappointed with its instability. RBS is another piece of crappy software.

In the end I went with Ahsay and was pretty satisfied with it. Back up and restore worked as it says on the tin.