RE: help with emergency--sql server 2000 sp4
- From: c676228 <bettys@xxxxxxxxxxxxxxxx>
- Date: Mon, 18 Sep 2006 09:51:02 -0700
Hi everyone
I don't really know what happened after they applied sp4 to my sql server
2000.
I told my myself, I need to take a look at my testing database, I suddenly I
found out that my live data get into my testing database and that tell me why
some my production program gives invalid object error messge. You can image
what will happen when you have production code running against testing
database.
So I look at the ODBC set up and the original DSN is pointing to testing
database instance instead of my origianl set up --> production database.
We have two database instances on our server. I guess they were not aware of
it. One is testing server(MSDE), one is production server(sql server 2000),
after the service pack is applied, something happened, I still don't know
they manually did it, or system set up?
Thank you all for providing your idea.
--
Betty
"Charles Wang[MSFT]" wrote:
Dear Betty,.
My understanding of your issue is:
Your ASP program failed to execute DML operations on your SQL Server after
the SP4 installed, though it had been working for five years. The
connection driver was DSN and query in QA worked fine. Also, you want to
know Microsoft emergency call.
If I have misunderstood, please let me know.
You can contact Microsoft Product Support Services (PSS) via telephone so
that a dedicated Support Professional can assist you recover the server in
a more efficient manner. Please be advised that contacting phone support
will be a charged call.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Also, I would like to give you some suggestions here before you make a call
to PSS.
1. Check if the user permissions changed after the SP4 installed. Ensure
the SQL login user is a dbo (database owner) .
2. Check if some error information existed in SQL error logs (C:\Program
files\Microsoft SQL Server\MSSQL\LOG).
3. Check if the default database in DSN is correct; I recommend that you
recreate the DSN data source and try again.
If you have any other questions or concerns, please feel free to let me
know. It's my pleasure to be of assistance.
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
- Follow-Ups:
- RE: help with emergency--sql server 2000 sp4
- From: Charles Wang[MSFT]
- RE: help with emergency--sql server 2000 sp4
- References:
- help with emergency--sql server 2000 sp4
- From: c676228
- RE: help with emergency--sql server 2000 sp4
- From: Charles Wang[MSFT]
- help with emergency--sql server 2000 sp4
- Prev by Date: RE: help with emergency--sql server 2000 sp4
- Next by Date: Table Problems with Access Linked to SQL Server 2005
- Previous by thread: RE: help with emergency--sql server 2000 sp4
- Next by thread: RE: help with emergency--sql server 2000 sp4
- Index(es):
Relevant Pages
|