Hi All
We have a database with approx. 460 tables linked to a foreign key (UserID)
in a table called Users. After installing SQL SP4, when trying to delete an
unreferenced entry in the Users table (even using Enterprise Manager), we get
the following error: "[Microsoft][ODBC SQL Server Driver][SQL Server]Internal
Query Processor Error: The query processor encountered an unexpected error
during execution."
Using the same database on a SP3a SQL server, it works fine.
Thanks in advance
Johan Fourie
Hi,
Johan Fourie,
Did u restarted ur sql services after installation of sp4.
hope this help
from
killer
|||Hi Johan,
Thanks for your post.
From your descriptions, I understood you SELECT statements will report the
error message after applied SP4. If I have misunderstood your concern,
please feel free to point it out.
Based on my knowledge, SQL Server SP4 should fix a related error message.
Please refer the KB for more detailed information.
FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries to
Compile a Plan for a Complex Query
http://support.microsoft.com/kb/818729
Is it possible for you to reproduce it on Northwind database? Would you
please generate a sample table, with which I could reproduct it on my side?
Any more error logs on your side? I understand the information may be
sensitive to you, my direct email address is v-mingqc@.online.microsoft.com
(please remember to remove "online" before click SEND as it's only for
SPAM), you may send the sample script file to me directly and I will keep
secure.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Yes, we did many reboots since the upgrade to SP4
Thanks
Johan Fourie
"doller" wrote:
> Hi,
> Johan Fourie,
> Did u restarted ur sql services after installation of sp4.
> hope this help
> from
> killer
>
|||Hi Michael
Ok, from SQL Query Analyzer the following command "DELETE FROM Users WHERE
UserID = 19" returns the following error: "Server: Msg 8630, Level 17, State
34, Line 1
Internal Query Processor Error: The query processor encountered an
unexpected error during execution."
I do not think it would be possible to simulate this problem on the
Northwind database as you need many FK links to the affected table. As you
can see, it is actually not a complex query, but SQL must determine whether
the entry being deleted is in use by one of the FK relationships (>460)
Thanks and much appreciated
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your post.
> From your descriptions, I understood you SELECT statements will report the
> error message after applied SP4. If I have misunderstood your concern,
> please feel free to point it out.
> Based on my knowledge, SQL Server SP4 should fix a related error message.
> Please refer the KB for more detailed information.
> FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries to
> Compile a Plan for a Complex Query
> http://support.microsoft.com/kb/818729
> Is it possible for you to reproduce it on Northwind database? Would you
> please generate a sample table, with which I could reproduct it on my side?
> Any more error logs on your side? I understand the information may be
> sensitive to you, my direct email address is v-mingqc@.online.microsoft.com
> (please remember to remove "online" before click SEND as it's only for
> SPAM), you may send the sample script file to me directly and I will keep
> secure.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Johan,
Thanks for the quick response.
It is very strange the SP4 enroll this new error message. I would like to
check it further. Is it possible for you to send me sample tables or sample
databases? (mdb file or the scripts with your tables)
I understand the information must be sensitive to you. Alternatively, to
efficiently troubleshoot a this issue, we recommend that you contact
Microsoft Customer Service and Support and open a support incident and work
with a dedicated Support Professional.
Please be advised that contacting phone support will be a charged call.
However, if it turn out to be a bug in SP4 then charges are usually
refunded or waived.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default...S;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael
Thanks for the quick response. We took the database again to a SP3a SQL
server and it works fine there, must be a SP4 problem. I'll be sending you
the database via e-mail shortly. Please treat the data and structure of the
database as very sensitive. Hope to hear from you soon.
Regards and many thanks.
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for the quick response.
> It is very strange the SP4 enroll this new error message. I would like to
> check it further. Is it possible for you to send me sample tables or sample
> databases? (mdb file or the scripts with your tables)
> I understand the information must be sensitive to you. Alternatively, to
> efficiently troubleshoot a this issue, we recommend that you contact
> Microsoft Customer Service and Support and open a support incident and work
> with a dedicated Support Professional.
> Please be advised that contacting phone support will be a charged call.
> However, if it turn out to be a bug in SP4 then charges are usually
> refunded or waived.
> To obtain the phone numbers for specific technology request please take a
> look at the web site listed below.
> http://support.microsoft.com/default...S;PHONENUMBERS
> If you are outside the US please see http://support.microsoft.com for
> regional support phone numbers.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Johan,
Thanks for your kindly sending me the database files.
After looking into the execution plan, I believe this is a known issue of
SQL Server service pack 4.
Since we add stack overflow checks in SP4, it raise this new problem. For
now, we do not have a pretty workaround for this issue.
However, if you want to apply SP4 and this issue has big business impact to
you. I would like to recommand you opening a grace case with Microsoft
Customer Service and Support (CSS). Please understand that we could not
share you the QFE request in the newsgroup.
Please be advised that contacting phone support will be a charged call.
However, if the support engineer confirmed this is a bug and no other
support then charges are usually refunded or waived.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default...S;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
You could share the information below with the CSS support engineer
Bug# SQL Server 8.0 20000179
I do apologized for this new known issue that caused to you and thanks so
much for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael
Thanks. Is there a quick fix available for this problem? We've advised all
our customers to go to SP4 (when it was released) and they wont be happy if
we tell them to go back to SP3a (as they all have this problem). Can you also
supply us with the KB number for this problem. Would it be possible for you
to send the QFE via e-mail to me?
Thanks in advance.
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your kindly sending me the database files.
> After looking into the execution plan, I believe this is a known issue of
> SQL Server service pack 4.
> Since we add stack overflow checks in SP4, it raise this new problem. For
> now, we do not have a pretty workaround for this issue.
> However, if you want to apply SP4 and this issue has big business impact to
> you. I would like to recommand you opening a grace case with Microsoft
> Customer Service and Support (CSS). Please understand that we could not
> share you the QFE request in the newsgroup.
> Please be advised that contacting phone support will be a charged call.
> However, if the support engineer confirmed this is a bug and no other
> support then charges are usually refunded or waived.
> To obtain the phone numbers for specific technology request please take a
> look at the web site listed below.
> http://support.microsoft.com/default...S;PHONENUMBERS
> If you are outside the US please see http://support.microsoft.com for
> regional support phone numbers.
> You could share the information below with the CSS support engineer
> Bug# SQL Server 8.0 20000179
> I do apologized for this new known issue that caused to you and thanks so
> much for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Johan,
Thanks for your update.
Unfortunately, I am so sorry to say that there is temporarily no public
Knowledge Base articles and document describing this issue. This issue only
occurs in SQL Server 2000 SP4, SQL Server 2000 SP3 and SQL Server 2005 do
not have this issue.
Unfortunately, I am unable to process the delivery of QFEs via email
directly. However, you should be able to quickly get this QFE by opening
the grace case with CSS.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label approx. Show all posts
Showing posts with label approx. Show all posts
Friday, March 30, 2012
Query Processor Error after SP4
Hi All
We have a database with approx. 460 tables linked to a foreign key (UserID)
in a table called Users. After installing SQL SP4, when trying to delete an
unreferenced entry in the Users table (even using Enterprise Manager), we ge
t
the following error: "[Microsoft][ODBC SQL Server Driver][SQL Se
rver]Internal
Query Processor Error: The query processor encountered an unexpected error
during execution."
Using the same database on a SP3a SQL server, it works fine.
Thanks in advance
--
Johan FourieHi,
Johan Fourie,
Did u restarted ur sql services after installation of sp4.
hope this help
from
killer|||Hi Johan,
Thanks for your post.
From your descriptions, I understood you SELECT statements will report the
error message after applied SP4. If I have misunderstood your concern,
please feel free to point it out.
Based on my knowledge, SQL Server SP4 should fix a related error message.
Please refer the KB for more detailed information.
FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries to
Compile a Plan for a Complex Query
http://support.microsoft.com/kb/818729
Is it possible for you to reproduce it on Northwind database? Would you
please generate a sample table, with which I could reproduct it on my side?
Any more error logs on your side? I understand the information may be
sensitive to you, my direct email address is v-mingqc@.online.microsoft.com
(please remember to remove "online" before click SEND as it's only for
SPAM), you may send the sample script file to me directly and I will keep
secure.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Yes, we did many reboots since the upgrade to SP4
Thanks
--
Johan Fourie
"doller" wrote:
> Hi,
> Johan Fourie,
> Did u restarted ur sql services after installation of sp4.
> hope this help
> from
> killer
>|||Hi Michael
Ok, from SQL Query Analyzer the following command "DELETE FROM Users WHERE
UserID = 19" returns the following error: "Server: Msg 8630, Level 17, State
34, Line 1
Internal Query Processor Error: The query processor encountered an
unexpected error during execution."
I do not think it would be possible to simulate this problem on the
Northwind database as you need many FK links to the affected table. As you
can see, it is actually not a complex query, but SQL must determine whether
the entry being deleted is in use by one of the FK relationships (>460)
Thanks and much appreciated
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your post.
> From your descriptions, I understood you SELECT statements will report the
> error message after applied SP4. If I have misunderstood your concern,
> please feel free to point it out.
> Based on my knowledge, SQL Server SP4 should fix a related error message.
> Please refer the KB for more detailed information.
> FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries t
o
> Compile a Plan for a Complex Query
> http://support.microsoft.com/kb/818729
> Is it possible for you to reproduce it on Northwind database? Would you
> please generate a sample table, with which I could reproduct it on my side
?
> Any more error logs on your side? I understand the information may be
> sensitive to you, my direct email address is v-mingqc@.online.microsoft.com
> (please remember to remove "online" before click SEND as it's only for
> SPAM), you may send the sample script file to me directly and I will keep
> secure.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Johan,
Thanks for the quick response.
It is very strange the SP4 enroll this new error message. I would like to
check it further. Is it possible for you to send me sample tables or sample
databases? (mdb file or the scripts with your tables)
I understand the information must be sensitive to you. Alternatively, to
efficiently troubleshoot a this issue, we recommend that you contact
Microsoft Customer Service and Support and open a support incident and work
with a dedicated Support Professional.
Please be advised that contacting phone support will be a charged call.
However, if it turn out to be a bug in SP4 then charges are usually
refunded or waived.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/defaul...US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
Thanks for the quick response. We took the database again to a SP3a SQL
server and it works fine there, must be a SP4 problem. I'll be sending you
the database via e-mail shortly. Please treat the data and structure of the
database as very sensitive. Hope to hear from you soon.
Regards and many thanks.
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for the quick response.
> It is very strange the SP4 enroll this new error message. I would like to
> check it further. Is it possible for you to send me sample tables or sampl
e
> databases? (mdb file or the scripts with your tables)
> I understand the information must be sensitive to you. Alternatively, to
> efficiently troubleshoot a this issue, we recommend that you contact
> Microsoft Customer Service and Support and open a support incident and wor
k
> with a dedicated Support Professional.
> Please be advised that contacting phone support will be a charged call.
> However, if it turn out to be a bug in SP4 then charges are usually
> refunded or waived.
> To obtain the phone numbers for specific technology request please take a
> look at the web site listed below.
> http://support.microsoft.com/defaul...US;PHONENUMBERS
> If you are outside the US please see http://support.microsoft.com for
> regional support phone numbers.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Johan,
Thanks for your kindly sending me the database files.
After looking into the execution plan, I believe this is a known issue of
SQL Server service pack 4.
Since we add stack overflow checks in SP4, it raise this new problem. For
now, we do not have a pretty workaround for this issue.
However, if you want to apply SP4 and this issue has big business impact to
you. I would like to recommand you opening a grace case with Microsoft
Customer Service and Support (CSS). Please understand that we could not
share you the QFE request in the newsgroup.
Please be advised that contacting phone support will be a charged call.
However, if the support engineer confirmed this is a bug and no other
support then charges are usually refunded or waived.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/defaul...US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
You could share the information below with the CSS support engineer
Bug# SQL Server 8.0 20000179
I do apologized for this new known issue that caused to you and thanks so
much for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
Thanks. Is there a quick fix available for this problem? We've advised all
our customers to go to SP4 (when it was released) and they wont be happy if
we tell them to go back to SP3a (as they all have this problem). Can you als
o
supply us with the KB number for this problem. Would it be possible for you
to send the QFE via e-mail to me?
Thanks in advance.
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your kindly sending me the database files.
> After looking into the execution plan, I believe this is a known issue of
> SQL Server service pack 4.
> Since we add stack overflow checks in SP4, it raise this new problem. For
> now, we do not have a pretty workaround for this issue.
> However, if you want to apply SP4 and this issue has big business impact t
o
> you. I would like to recommand you opening a grace case with Microsoft
> Customer Service and Support (CSS). Please understand that we could not
> share you the QFE request in the newsgroup.
> Please be advised that contacting phone support will be a charged call.
> However, if the support engineer confirmed this is a bug and no other
> support then charges are usually refunded or waived.
> To obtain the phone numbers for specific technology request please take a
> look at the web site listed below.
> http://support.microsoft.com/defaul...US;PHONENUMBERS
> If you are outside the US please see http://support.microsoft.com for
> regional support phone numbers.
> You could share the information below with the CSS support engineer
> Bug# SQL Server 8.0 20000179
> I do apologized for this new known issue that caused to you and thanks so
> much for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Johan,
Thanks for your update.
Unfortunately, I am so sorry to say that there is temporarily no public
Knowledge Base articles and document describing this issue. This issue only
occurs in SQL Server 2000 SP4, SQL Server 2000 SP3 and SQL Server 2005 do
not have this issue.
Unfortunately, I am unable to process the delivery of QFEs via email
directly. However, you should be able to quickly get this QFE by opening
the grace case with CSS.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
We have a database with approx. 460 tables linked to a foreign key (UserID)
in a table called Users. After installing SQL SP4, when trying to delete an
unreferenced entry in the Users table (even using Enterprise Manager), we ge
t
the following error: "[Microsoft][ODBC SQL Server Driver][SQL Se
rver]Internal
Query Processor Error: The query processor encountered an unexpected error
during execution."
Using the same database on a SP3a SQL server, it works fine.
Thanks in advance
--
Johan FourieHi,
Johan Fourie,
Did u restarted ur sql services after installation of sp4.
hope this help
from
killer|||Hi Johan,
Thanks for your post.
From your descriptions, I understood you SELECT statements will report the
error message after applied SP4. If I have misunderstood your concern,
please feel free to point it out.
Based on my knowledge, SQL Server SP4 should fix a related error message.
Please refer the KB for more detailed information.
FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries to
Compile a Plan for a Complex Query
http://support.microsoft.com/kb/818729
Is it possible for you to reproduce it on Northwind database? Would you
please generate a sample table, with which I could reproduct it on my side?
Any more error logs on your side? I understand the information may be
sensitive to you, my direct email address is v-mingqc@.online.microsoft.com
(please remember to remove "online" before click SEND as it's only for
SPAM), you may send the sample script file to me directly and I will keep
secure.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Yes, we did many reboots since the upgrade to SP4
Thanks
--
Johan Fourie
"doller" wrote:
> Hi,
> Johan Fourie,
> Did u restarted ur sql services after installation of sp4.
> hope this help
> from
> killer
>|||Hi Michael
Ok, from SQL Query Analyzer the following command "DELETE FROM Users WHERE
UserID = 19" returns the following error: "Server: Msg 8630, Level 17, State
34, Line 1
Internal Query Processor Error: The query processor encountered an
unexpected error during execution."
I do not think it would be possible to simulate this problem on the
Northwind database as you need many FK links to the affected table. As you
can see, it is actually not a complex query, but SQL must determine whether
the entry being deleted is in use by one of the FK relationships (>460)
Thanks and much appreciated
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your post.
> From your descriptions, I understood you SELECT statements will report the
> error message after applied SP4. If I have misunderstood your concern,
> please feel free to point it out.
> Based on my knowledge, SQL Server SP4 should fix a related error message.
> Please refer the KB for more detailed information.
> FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries t
o
> Compile a Plan for a Complex Query
> http://support.microsoft.com/kb/818729
> Is it possible for you to reproduce it on Northwind database? Would you
> please generate a sample table, with which I could reproduct it on my side
?
> Any more error logs on your side? I understand the information may be
> sensitive to you, my direct email address is v-mingqc@.online.microsoft.com
> (please remember to remove "online" before click SEND as it's only for
> SPAM), you may send the sample script file to me directly and I will keep
> secure.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Johan,
Thanks for the quick response.
It is very strange the SP4 enroll this new error message. I would like to
check it further. Is it possible for you to send me sample tables or sample
databases? (mdb file or the scripts with your tables)
I understand the information must be sensitive to you. Alternatively, to
efficiently troubleshoot a this issue, we recommend that you contact
Microsoft Customer Service and Support and open a support incident and work
with a dedicated Support Professional.
Please be advised that contacting phone support will be a charged call.
However, if it turn out to be a bug in SP4 then charges are usually
refunded or waived.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/defaul...US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
Thanks for the quick response. We took the database again to a SP3a SQL
server and it works fine there, must be a SP4 problem. I'll be sending you
the database via e-mail shortly. Please treat the data and structure of the
database as very sensitive. Hope to hear from you soon.
Regards and many thanks.
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for the quick response.
> It is very strange the SP4 enroll this new error message. I would like to
> check it further. Is it possible for you to send me sample tables or sampl
e
> databases? (mdb file or the scripts with your tables)
> I understand the information must be sensitive to you. Alternatively, to
> efficiently troubleshoot a this issue, we recommend that you contact
> Microsoft Customer Service and Support and open a support incident and wor
k
> with a dedicated Support Professional.
> Please be advised that contacting phone support will be a charged call.
> However, if it turn out to be a bug in SP4 then charges are usually
> refunded or waived.
> To obtain the phone numbers for specific technology request please take a
> look at the web site listed below.
> http://support.microsoft.com/defaul...US;PHONENUMBERS
> If you are outside the US please see http://support.microsoft.com for
> regional support phone numbers.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Johan,
Thanks for your kindly sending me the database files.
After looking into the execution plan, I believe this is a known issue of
SQL Server service pack 4.
Since we add stack overflow checks in SP4, it raise this new problem. For
now, we do not have a pretty workaround for this issue.
However, if you want to apply SP4 and this issue has big business impact to
you. I would like to recommand you opening a grace case with Microsoft
Customer Service and Support (CSS). Please understand that we could not
share you the QFE request in the newsgroup.
Please be advised that contacting phone support will be a charged call.
However, if the support engineer confirmed this is a bug and no other
support then charges are usually refunded or waived.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/defaul...US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
You could share the information below with the CSS support engineer
Bug# SQL Server 8.0 20000179
I do apologized for this new known issue that caused to you and thanks so
much for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
Thanks. Is there a quick fix available for this problem? We've advised all
our customers to go to SP4 (when it was released) and they wont be happy if
we tell them to go back to SP3a (as they all have this problem). Can you als
o
supply us with the KB number for this problem. Would it be possible for you
to send the QFE via e-mail to me?
Thanks in advance.
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your kindly sending me the database files.
> After looking into the execution plan, I believe this is a known issue of
> SQL Server service pack 4.
> Since we add stack overflow checks in SP4, it raise this new problem. For
> now, we do not have a pretty workaround for this issue.
> However, if you want to apply SP4 and this issue has big business impact t
o
> you. I would like to recommand you opening a grace case with Microsoft
> Customer Service and Support (CSS). Please understand that we could not
> share you the QFE request in the newsgroup.
> Please be advised that contacting phone support will be a charged call.
> However, if the support engineer confirmed this is a bug and no other
> support then charges are usually refunded or waived.
> To obtain the phone numbers for specific technology request please take a
> look at the web site listed below.
> http://support.microsoft.com/defaul...US;PHONENUMBERS
> If you are outside the US please see http://support.microsoft.com for
> regional support phone numbers.
> You could share the information below with the CSS support engineer
> Bug# SQL Server 8.0 20000179
> I do apologized for this new known issue that caused to you and thanks so
> much for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Johan,
Thanks for your update.
Unfortunately, I am so sorry to say that there is temporarily no public
Knowledge Base articles and document describing this issue. This issue only
occurs in SQL Server 2000 SP4, SQL Server 2000 SP3 and SQL Server 2005 do
not have this issue.
Unfortunately, I am unable to process the delivery of QFEs via email
directly. However, you should be able to quickly get this QFE by opening
the grace case with CSS.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Query Processor Error after SP4
Hi All
We have a database with approx. 460 tables linked to a foreign key (UserID)
in a table called Users. After installing SQL SP4, when trying to delete an
unreferenced entry in the Users table (even using Enterprise Manager), we get
the following error: "[Microsoft][ODBC SQL Server Driver][SQL Server]Internal
Query Processor Error: The query processor encountered an unexpected error
during execution."
Using the same database on a SP3a SQL server, it works fine.
Thanks in advance
--
Johan FourieHi,
Johan Fourie,
Did u restarted ur sql services after installation of sp4.
hope this help
from
killer|||Hi Johan,
Thanks for your post.
From your descriptions, I understood you SELECT statements will report the
error message after applied SP4. If I have misunderstood your concern,
please feel free to point it out.
Based on my knowledge, SQL Server SP4 should fix a related error message.
Please refer the KB for more detailed information.
FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries to
Compile a Plan for a Complex Query
http://support.microsoft.com/kb/818729
Is it possible for you to reproduce it on Northwind database? Would you
please generate a sample table, with which I could reproduct it on my side?
Any more error logs on your side? I understand the information may be
sensitive to you, my direct email address is v-mingqc@.online.microsoft.com
(please remember to remove "online" before click SEND as it's only for
SPAM), you may send the sample script file to me directly and I will keep
secure.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Yes, we did many reboots since the upgrade to SP4
Thanks
--
Johan Fourie
"doller" wrote:
> Hi,
> Johan Fourie,
> Did u restarted ur sql services after installation of sp4.
> hope this help
> from
> killer
>|||Hi Michael
Ok, from SQL Query Analyzer the following command "DELETE FROM Users WHERE
UserID = 19" returns the following error: "Server: Msg 8630, Level 17, State
34, Line 1
Internal Query Processor Error: The query processor encountered an
unexpected error during execution."
I do not think it would be possible to simulate this problem on the
Northwind database as you need many FK links to the affected table. As you
can see, it is actually not a complex query, but SQL must determine whether
the entry being deleted is in use by one of the FK relationships (>460)
Thanks and much appreciated
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your post.
> From your descriptions, I understood you SELECT statements will report the
> error message after applied SP4. If I have misunderstood your concern,
> please feel free to point it out.
> Based on my knowledge, SQL Server SP4 should fix a related error message.
> Please refer the KB for more detailed information.
> FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries to
> Compile a Plan for a Complex Query
> http://support.microsoft.com/kb/818729
> Is it possible for you to reproduce it on Northwind database? Would you
> please generate a sample table, with which I could reproduct it on my side?
> Any more error logs on your side? I understand the information may be
> sensitive to you, my direct email address is v-mingqc@.online.microsoft.com
> (please remember to remove "online" before click SEND as it's only for
> SPAM), you may send the sample script file to me directly and I will keep
> secure.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Johan,
Thanks for the quick response.
It is very strange the SP4 enroll this new error message. I would like to
check it further. Is it possible for you to send me sample tables or sample
databases? (mdb file or the scripts with your tables)
I understand the information must be sensitive to you. Alternatively, to
efficiently troubleshoot a this issue, we recommend that you contact
Microsoft Customer Service and Support and open a support incident and work
with a dedicated Support Professional.
Please be advised that contacting phone support will be a charged call.
However, if it turn out to be a bug in SP4 then charges are usually
refunded or waived.
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.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
Thanks for the quick response. We took the database again to a SP3a SQL
server and it works fine there, must be a SP4 problem. I'll be sending you
the database via e-mail shortly. Please treat the data and structure of the
database as very sensitive. Hope to hear from you soon.
Regards and many thanks.
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for the quick response.
> It is very strange the SP4 enroll this new error message. I would like to
> check it further. Is it possible for you to send me sample tables or sample
> databases? (mdb file or the scripts with your tables)
> I understand the information must be sensitive to you. Alternatively, to
> efficiently troubleshoot a this issue, we recommend that you contact
> Microsoft Customer Service and Support and open a support incident and work
> with a dedicated Support Professional.
> Please be advised that contacting phone support will be a charged call.
> However, if it turn out to be a bug in SP4 then charges are usually
> refunded or waived.
> 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.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Johan,
Thanks for your kindly sending me the database files.
After looking into the execution plan, I believe this is a known issue of
SQL Server service pack 4.
Since we add stack overflow checks in SP4, it raise this new problem. For
now, we do not have a pretty workaround for this issue.
However, if you want to apply SP4 and this issue has big business impact to
you. I would like to recommand you opening a grace case with Microsoft
Customer Service and Support (CSS). Please understand that we could not
share you the QFE request in the newsgroup.
Please be advised that contacting phone support will be a charged call.
However, if the support engineer confirmed this is a bug and no other
support then charges are usually refunded or waived.
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.
You could share the information below with the CSS support engineer
Bug# SQL Server 8.0 20000179
I do apologized for this new known issue that caused to you and thanks so
much for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
Thanks. Is there a quick fix available for this problem? We've advised all
our customers to go to SP4 (when it was released) and they wont be happy if
we tell them to go back to SP3a (as they all have this problem). Can you also
supply us with the KB number for this problem. Would it be possible for you
to send the QFE via e-mail to me?
Thanks in advance.
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your kindly sending me the database files.
> After looking into the execution plan, I believe this is a known issue of
> SQL Server service pack 4.
> Since we add stack overflow checks in SP4, it raise this new problem. For
> now, we do not have a pretty workaround for this issue.
> However, if you want to apply SP4 and this issue has big business impact to
> you. I would like to recommand you opening a grace case with Microsoft
> Customer Service and Support (CSS). Please understand that we could not
> share you the QFE request in the newsgroup.
> Please be advised that contacting phone support will be a charged call.
> However, if the support engineer confirmed this is a bug and no other
> support then charges are usually refunded or waived.
> 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.
> You could share the information below with the CSS support engineer
> Bug# SQL Server 8.0 20000179
> I do apologized for this new known issue that caused to you and thanks so
> much for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Johan,
Thanks for your update.
Unfortunately, I am so sorry to say that there is temporarily no public
Knowledge Base articles and document describing this issue. This issue only
occurs in SQL Server 2000 SP4, SQL Server 2000 SP3 and SQL Server 2005 do
not have this issue.
Unfortunately, I am unable to process the delivery of QFEs via email
directly. However, you should be able to quickly get this QFE by opening
the grace case with CSS.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks. I'll open a case with CSS.
Regards.
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your update.
> Unfortunately, I am so sorry to say that there is temporarily no public
> Knowledge Base articles and document describing this issue. This issue only
> occurs in SQL Server 2000 SP4, SQL Server 2000 SP3 and SQL Server 2005 do
> not have this issue.
> Unfortunately, I am unable to process the delivery of QFEs via email
> directly. However, you should be able to quickly get this QFE by opening
> the grace case with CSS.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Johan,
Thanks for your cooperation.
I just wanted to follow up to let you know that the Support Engineer that
you are working with in CSS has contacted me directly to let me know that
the hotfix I recommended is not currently available to the public. I
apologize that I was not previously aware of this situation.
Please continue to work with the CSS Support Engineer for a workaround or
resolution to your issue.
Again, I am sorry that I was unaware that this hotfix is not available to
the public.
Thank you for your patience and cooperation.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
We have a database with approx. 460 tables linked to a foreign key (UserID)
in a table called Users. After installing SQL SP4, when trying to delete an
unreferenced entry in the Users table (even using Enterprise Manager), we get
the following error: "[Microsoft][ODBC SQL Server Driver][SQL Server]Internal
Query Processor Error: The query processor encountered an unexpected error
during execution."
Using the same database on a SP3a SQL server, it works fine.
Thanks in advance
--
Johan FourieHi,
Johan Fourie,
Did u restarted ur sql services after installation of sp4.
hope this help
from
killer|||Hi Johan,
Thanks for your post.
From your descriptions, I understood you SELECT statements will report the
error message after applied SP4. If I have misunderstood your concern,
please feel free to point it out.
Based on my knowledge, SQL Server SP4 should fix a related error message.
Please refer the KB for more detailed information.
FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries to
Compile a Plan for a Complex Query
http://support.microsoft.com/kb/818729
Is it possible for you to reproduce it on Northwind database? Would you
please generate a sample table, with which I could reproduct it on my side?
Any more error logs on your side? I understand the information may be
sensitive to you, my direct email address is v-mingqc@.online.microsoft.com
(please remember to remove "online" before click SEND as it's only for
SPAM), you may send the sample script file to me directly and I will keep
secure.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Yes, we did many reboots since the upgrade to SP4
Thanks
--
Johan Fourie
"doller" wrote:
> Hi,
> Johan Fourie,
> Did u restarted ur sql services after installation of sp4.
> hope this help
> from
> killer
>|||Hi Michael
Ok, from SQL Query Analyzer the following command "DELETE FROM Users WHERE
UserID = 19" returns the following error: "Server: Msg 8630, Level 17, State
34, Line 1
Internal Query Processor Error: The query processor encountered an
unexpected error during execution."
I do not think it would be possible to simulate this problem on the
Northwind database as you need many FK links to the affected table. As you
can see, it is actually not a complex query, but SQL must determine whether
the entry being deleted is in use by one of the FK relationships (>460)
Thanks and much appreciated
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your post.
> From your descriptions, I understood you SELECT statements will report the
> error message after applied SP4. If I have misunderstood your concern,
> please feel free to point it out.
> Based on my knowledge, SQL Server SP4 should fix a related error message.
> Please refer the KB for more detailed information.
> FIX: Internal Query Processor Error 8623 When Microsoft SQL Server Tries to
> Compile a Plan for a Complex Query
> http://support.microsoft.com/kb/818729
> Is it possible for you to reproduce it on Northwind database? Would you
> please generate a sample table, with which I could reproduct it on my side?
> Any more error logs on your side? I understand the information may be
> sensitive to you, my direct email address is v-mingqc@.online.microsoft.com
> (please remember to remove "online" before click SEND as it's only for
> SPAM), you may send the sample script file to me directly and I will keep
> secure.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Johan,
Thanks for the quick response.
It is very strange the SP4 enroll this new error message. I would like to
check it further. Is it possible for you to send me sample tables or sample
databases? (mdb file or the scripts with your tables)
I understand the information must be sensitive to you. Alternatively, to
efficiently troubleshoot a this issue, we recommend that you contact
Microsoft Customer Service and Support and open a support incident and work
with a dedicated Support Professional.
Please be advised that contacting phone support will be a charged call.
However, if it turn out to be a bug in SP4 then charges are usually
refunded or waived.
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.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
Thanks for the quick response. We took the database again to a SP3a SQL
server and it works fine there, must be a SP4 problem. I'll be sending you
the database via e-mail shortly. Please treat the data and structure of the
database as very sensitive. Hope to hear from you soon.
Regards and many thanks.
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for the quick response.
> It is very strange the SP4 enroll this new error message. I would like to
> check it further. Is it possible for you to send me sample tables or sample
> databases? (mdb file or the scripts with your tables)
> I understand the information must be sensitive to you. Alternatively, to
> efficiently troubleshoot a this issue, we recommend that you contact
> Microsoft Customer Service and Support and open a support incident and work
> with a dedicated Support Professional.
> Please be advised that contacting phone support will be a charged call.
> However, if it turn out to be a bug in SP4 then charges are usually
> refunded or waived.
> 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.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Johan,
Thanks for your kindly sending me the database files.
After looking into the execution plan, I believe this is a known issue of
SQL Server service pack 4.
Since we add stack overflow checks in SP4, it raise this new problem. For
now, we do not have a pretty workaround for this issue.
However, if you want to apply SP4 and this issue has big business impact to
you. I would like to recommand you opening a grace case with Microsoft
Customer Service and Support (CSS). Please understand that we could not
share you the QFE request in the newsgroup.
Please be advised that contacting phone support will be a charged call.
However, if the support engineer confirmed this is a bug and no other
support then charges are usually refunded or waived.
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.
You could share the information below with the CSS support engineer
Bug# SQL Server 8.0 20000179
I do apologized for this new known issue that caused to you and thanks so
much for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael
Thanks. Is there a quick fix available for this problem? We've advised all
our customers to go to SP4 (when it was released) and they wont be happy if
we tell them to go back to SP3a (as they all have this problem). Can you also
supply us with the KB number for this problem. Would it be possible for you
to send the QFE via e-mail to me?
Thanks in advance.
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your kindly sending me the database files.
> After looking into the execution plan, I believe this is a known issue of
> SQL Server service pack 4.
> Since we add stack overflow checks in SP4, it raise this new problem. For
> now, we do not have a pretty workaround for this issue.
> However, if you want to apply SP4 and this issue has big business impact to
> you. I would like to recommand you opening a grace case with Microsoft
> Customer Service and Support (CSS). Please understand that we could not
> share you the QFE request in the newsgroup.
> Please be advised that contacting phone support will be a charged call.
> However, if the support engineer confirmed this is a bug and no other
> support then charges are usually refunded or waived.
> 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.
> You could share the information below with the CSS support engineer
> Bug# SQL Server 8.0 20000179
> I do apologized for this new known issue that caused to you and thanks so
> much for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Johan,
Thanks for your update.
Unfortunately, I am so sorry to say that there is temporarily no public
Knowledge Base articles and document describing this issue. This issue only
occurs in SQL Server 2000 SP4, SQL Server 2000 SP3 and SQL Server 2005 do
not have this issue.
Unfortunately, I am unable to process the delivery of QFEs via email
directly. However, you should be able to quickly get this QFE by opening
the grace case with CSS.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks. I'll open a case with CSS.
Regards.
--
Johan Fourie
"Michael Cheng [MSFT]" wrote:
> Hi Johan,
> Thanks for your update.
> Unfortunately, I am so sorry to say that there is temporarily no public
> Knowledge Base articles and document describing this issue. This issue only
> occurs in SQL Server 2000 SP4, SQL Server 2000 SP3 and SQL Server 2005 do
> not have this issue.
> Unfortunately, I am unable to process the delivery of QFEs via email
> directly. However, you should be able to quickly get this QFE by opening
> the grace case with CSS.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Johan,
Thanks for your cooperation.
I just wanted to follow up to let you know that the Support Engineer that
you are working with in CSS has contacted me directly to let me know that
the hotfix I recommended is not currently available to the public. I
apologize that I was not previously aware of this situation.
Please continue to work with the CSS Support Engineer for a workaround or
resolution to your issue.
Again, I am sorry that I was unaware that this hotfix is not available to
the public.
Thank you for your patience and cooperation.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Tuesday, March 20, 2012
Query Performance
Hi,
I have a query which takes approx 45 sec to execute in Query Analyzer but it
takes more than 60 min to execute in MSRS. What is the reason for it and how
to improve it's performance ?
ThanksHi push:
Could you show us the query?
--
Scott
http://www.OdeToCode.com
On Fri, 20 Aug 2004 02:37:01 -0700, "push"
<push@.discussions.microsoft.com> wrote:
>Hi,
>I have a query which takes approx 45 sec to execute in Query Analyzer but it
>takes more than 60 min to execute in MSRS. What is the reason for it and how
>to improve it's performance ?
>Thanks|||push wrote:
> I have a query which takes approx 45 sec to execute in Query Analyzer but it
> takes more than 60 min to execute in MSRS. What is the reason for it and how
> to improve it's performance ?
I would first try and pinpoint where the time is being taken. Looking
at the ExecutionLog in the Report Server catalog database would tell you
the total row count and how the total report rendering time divides up
between data retrieval, internal processing, and format-specific
rendering. Could you post these numbers as well as a brief description
of the hardware you're running this on? An example query would be nice
as well.
--
Thanks.
Donovan R. Smith
Software Test Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
I have a query which takes approx 45 sec to execute in Query Analyzer but it
takes more than 60 min to execute in MSRS. What is the reason for it and how
to improve it's performance ?
ThanksHi push:
Could you show us the query?
--
Scott
http://www.OdeToCode.com
On Fri, 20 Aug 2004 02:37:01 -0700, "push"
<push@.discussions.microsoft.com> wrote:
>Hi,
>I have a query which takes approx 45 sec to execute in Query Analyzer but it
>takes more than 60 min to execute in MSRS. What is the reason for it and how
>to improve it's performance ?
>Thanks|||push wrote:
> I have a query which takes approx 45 sec to execute in Query Analyzer but it
> takes more than 60 min to execute in MSRS. What is the reason for it and how
> to improve it's performance ?
I would first try and pinpoint where the time is being taken. Looking
at the ExecutionLog in the Report Server catalog database would tell you
the total row count and how the total report rendering time divides up
between data retrieval, internal processing, and format-specific
rendering. Could you post these numbers as well as a brief description
of the hardware you're running this on? An example query would be nice
as well.
--
Thanks.
Donovan R. Smith
Software Test Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
Monday, March 12, 2012
Query Parallelism (maxdop)
I have 4 processor SQL server. When I run this query in query analyzer
(two table joins with w
ly aggregation approx 500,000 rows each) ...
it takes only 7 seconds... when I run it in a stored procedure... it
takes about 60 minutes. I dont see parallelism in the execution plan of
SP... I have already tried hint maxdop... it did'nt work... Im not
sure what I might be running into'
Any help is greatly appreciated...Google "parameter sniffing".
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"zomer" <noneee@.gmail.com> wrote in message
news:1145384015.190289.310680@.e56g2000cwe.googlegroups.com...
I have 4 processor SQL server. When I run this query in query analyzer
(two table joins with wly aggregation approx 500,000 rows each) ...
it takes only 7 seconds... when I run it in a stored procedure... it
takes about 60 minutes. I dont see parallelism in the execution plan of
SP... I have already tried hint maxdop... it did'nt work... Im not
sure what I might be running into'
Any help is greatly appreciated...|||Try using WITH RECOMPILE on your stored procedure just as an initial test.
It may be getting a less than optimal execution plan. See
http://www.dbtalk.net/microsoft-pub...ter-203396.html
for some thoughts.
I'm running into some similar issues with ADO taking ludicrously long while
Query Analyzer goes quickly. Haven't tracked down the exact cause yet,
though it appears many other people have had the same issue.
Mike
"zomer" <noneee@.gmail.com> wrote in message
news:1145384015.190289.310680@.e56g2000cwe.googlegroups.com...
>I have 4 processor SQL server. When I run this query in query analyzer
> (two table joins with wly aggregation approx 500,000 rows each) ...
> it takes only 7 seconds... when I run it in a stored procedure... it
> takes about 60 minutes. I dont see parallelism in the execution plan of
> SP... I have already tried hint maxdop... it did'nt work... Im not
> sure what I might be running into'
> Any help is greatly appreciated...
>|||Tom -
Are there other things besides the parameter sniffing that could cause the
performance difference?
I'm running into a similar problem, except here's what's happening:
1. I have SQL Profiler on in production.
2. I catch the "slow" procedure
3. Immediately I copy and paste the text into Query Analyzer and execute the
query on the same production server -- and it executes quickly.
Same parameters. Same execution plan I would think (I'm not seeing any
recompiles). The parameter sniffing discussion made sense but it doesn't
seem to fit this scenario since the procedure is already compiled and I'm
executing it with the same paramters that made it run slow from the app.
Thanks for any help,
Mike
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:ucLVCUxYGHA.3880@.TK2MSFTNGP04.phx.gbl...
> Google "parameter sniffing".
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> "zomer" <noneee@.gmail.com> wrote in message
> news:1145384015.190289.310680@.e56g2000cwe.googlegroups.com...
> I have 4 processor SQL server. When I run this query in query analyzer
> (two table joins with wly aggregation approx 500,000 rows each) ...
> it takes only 7 seconds... when I run it in a stored procedure... it
> takes about 60 minutes. I dont see parallelism in the execution plan of
> SP... I have already tried hint maxdop... it did'nt work... Im not
> sure what I might be running into'
> Any help is greatly appreciated...
>|||I'd take a close look at the Execution Plan for each (sproc and QA runs) -
sounds like it's not using an index somewhere along the line.
HTH
"zomer" wrote:
> I have 4 processor SQL server. When I run this query in query analyzer
> (two table joins with wly aggregation approx 500,000 rows each) ...
> it takes only 7 seconds... when I run it in a stored procedure... it
> takes about 60 minutes. I dont see parallelism in the execution plan of
> SP... I have already tried hint maxdop... it did'nt work... Im not
> sure what I might be running into'
> Any help is greatly appreciated...
>|||More info for my previous post: When I profiled SP:Stmt Starting and
SP:StmtEnding, the application executed query showed the length of the
SELECT statements as being lengthened (there are multiple result sets
returned). ALL of the indivdual SELECTs were propotionally slower.
To me this seems to be some type of interaction problem between ADO and SQL
Server, not a SQL Server performance issue. The ADO client uses client side
cursors. This brings up the question: Can slow response on the
SQLOLEDB/ADO driver side affect duration times in SQL Profiler ?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:ucLVCUxYGHA.3880@.TK2MSFTNGP04.phx.gbl...
> Google "parameter sniffing".
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> "zomer" <noneee@.gmail.com> wrote in message
> news:1145384015.190289.310680@.e56g2000cwe.googlegroups.com...
> I have 4 processor SQL server. When I run this query in query analyzer
> (two table joins with wly aggregation approx 500,000 rows each) ...
> it takes only 7 seconds... when I run it in a stored procedure... it
> takes about 60 minutes. I dont see parallelism in the execution plan of
> SP... I have already tried hint maxdop... it did'nt work... Im not
> sure what I might be running into'
> Any help is greatly appreciated...
>|||I think what you're seeing is data and/or plan caching - and that's by
design. When a query first enters SQL Server, a plan is created and cached.
This takes time. Upon subsequent execution, the original plan is (likely)
used, and this goes faster. However, any data that were read by the
just-executed query are likely now in data cache. Thus, the next time the
query is run, it's getting the data from cache - not from disk. The more
RAM you have, the bigger the cache you have - and the faster (in most cases)
that SQL Server will run.
If you want a pure apples to apples comparison, run the following before
each test:
DBCC FREEPROCCACHE
DBCC DROPCLEANBUFFERS
This flushes the proc and data caches, respectively. Now, you get a fresh
plan - and you get your data from disk. A subsequent run without running
these DBCC's should go significantly faster.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Jansen" <mjansen_nntp@.mail.com> wrote in message
news:uTK$ihxYGHA.1192@.TK2MSFTNGP03.phx.gbl...
Tom -
Are there other things besides the parameter sniffing that could cause the
performance difference?
I'm running into a similar problem, except here's what's happening:
1. I have SQL Profiler on in production.
2. I catch the "slow" procedure
3. Immediately I copy and paste the text into Query Analyzer and execute the
query on the same production server -- and it executes quickly.
Same parameters. Same execution plan I would think (I'm not seeing any
recompiles). The parameter sniffing discussion made sense but it doesn't
seem to fit this scenario since the procedure is already compiled and I'm
executing it with the same paramters that made it run slow from the app.
Thanks for any help,
Mike
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:ucLVCUxYGHA.3880@.TK2MSFTNGP04.phx.gbl...
> Google "parameter sniffing".
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> "zomer" <noneee@.gmail.com> wrote in message
> news:1145384015.190289.310680@.e56g2000cwe.googlegroups.com...
> I have 4 processor SQL server. When I run this query in query analyzer
> (two table joins with wly aggregation approx 500,000 rows each) ...
> it takes only 7 seconds... when I run it in a stored procedure... it
> takes about 60 minutes. I dont see parallelism in the execution plan of
> SP... I have already tried hint maxdop... it did'nt work... Im not
> sure what I might be running into'
> Any help is greatly appreciated...
>|||Im glad you mentioned that... the only difference of execution plan is
that the if I use query analyzer... it uses parallelism while stored
procedure does not. Why is it so' The server load is pretty
consistent.|||You may want to search on "firehose cursor".
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Jansen" <mjansen_nntp@.mail.com> wrote in message
news:e%236DQxxYGHA.3832@.TK2MSFTNGP04.phx.gbl...
> Duration on the Profiler is the time between receiving the statement and
> the
> last row being retrieved.
Cool. That's what I was suspecting.
> My guess is that your ADO may not be optimal.
It's a single call to Recordset.Open with a client side cursor so there's
not much other than tuning some settings I can do. I think its time to take
this issue to the ADO forum. Thanks for all your input.
Mike|||I'm thinking it's ADO-related.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"zomer" <noneee@.gmail.com> wrote in message
news:1145387868.100688.258810@.e56g2000cwe.googlegroups.com...
yes... datatypes are the same.
(two table joins with w
ly aggregation approx 500,000 rows each) ...it takes only 7 seconds... when I run it in a stored procedure... it
takes about 60 minutes. I dont see parallelism in the execution plan of
SP... I have already tried hint maxdop... it did'nt work... Im not
sure what I might be running into'
Any help is greatly appreciated...Google "parameter sniffing".
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"zomer" <noneee@.gmail.com> wrote in message
news:1145384015.190289.310680@.e56g2000cwe.googlegroups.com...
I have 4 processor SQL server. When I run this query in query analyzer
(two table joins with w
ly aggregation approx 500,000 rows each) ...it takes only 7 seconds... when I run it in a stored procedure... it
takes about 60 minutes. I dont see parallelism in the execution plan of
SP... I have already tried hint maxdop... it did'nt work... Im not
sure what I might be running into'
Any help is greatly appreciated...|||Try using WITH RECOMPILE on your stored procedure just as an initial test.
It may be getting a less than optimal execution plan. See
http://www.dbtalk.net/microsoft-pub...ter-203396.html
for some thoughts.
I'm running into some similar issues with ADO taking ludicrously long while
Query Analyzer goes quickly. Haven't tracked down the exact cause yet,
though it appears many other people have had the same issue.
Mike
"zomer" <noneee@.gmail.com> wrote in message
news:1145384015.190289.310680@.e56g2000cwe.googlegroups.com...
>I have 4 processor SQL server. When I run this query in query analyzer
> (two table joins with w
ly aggregation approx 500,000 rows each) ...> it takes only 7 seconds... when I run it in a stored procedure... it
> takes about 60 minutes. I dont see parallelism in the execution plan of
> SP... I have already tried hint maxdop... it did'nt work... Im not
> sure what I might be running into'
> Any help is greatly appreciated...
>|||Tom -
Are there other things besides the parameter sniffing that could cause the
performance difference?
I'm running into a similar problem, except here's what's happening:
1. I have SQL Profiler on in production.
2. I catch the "slow" procedure
3. Immediately I copy and paste the text into Query Analyzer and execute the
query on the same production server -- and it executes quickly.
Same parameters. Same execution plan I would think (I'm not seeing any
recompiles). The parameter sniffing discussion made sense but it doesn't
seem to fit this scenario since the procedure is already compiled and I'm
executing it with the same paramters that made it run slow from the app.
Thanks for any help,
Mike
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:ucLVCUxYGHA.3880@.TK2MSFTNGP04.phx.gbl...
> Google "parameter sniffing".
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> "zomer" <noneee@.gmail.com> wrote in message
> news:1145384015.190289.310680@.e56g2000cwe.googlegroups.com...
> I have 4 processor SQL server. When I run this query in query analyzer
> (two table joins with w
ly aggregation approx 500,000 rows each) ...> it takes only 7 seconds... when I run it in a stored procedure... it
> takes about 60 minutes. I dont see parallelism in the execution plan of
> SP... I have already tried hint maxdop... it did'nt work... Im not
> sure what I might be running into'
> Any help is greatly appreciated...
>|||I'd take a close look at the Execution Plan for each (sproc and QA runs) -
sounds like it's not using an index somewhere along the line.
HTH
"zomer" wrote:
> I have 4 processor SQL server. When I run this query in query analyzer
> (two table joins with w
ly aggregation approx 500,000 rows each) ...> it takes only 7 seconds... when I run it in a stored procedure... it
> takes about 60 minutes. I dont see parallelism in the execution plan of
> SP... I have already tried hint maxdop... it did'nt work... Im not
> sure what I might be running into'
> Any help is greatly appreciated...
>|||More info for my previous post: When I profiled SP:Stmt Starting and
SP:StmtEnding, the application executed query showed the length of the
SELECT statements as being lengthened (there are multiple result sets
returned). ALL of the indivdual SELECTs were propotionally slower.
To me this seems to be some type of interaction problem between ADO and SQL
Server, not a SQL Server performance issue. The ADO client uses client side
cursors. This brings up the question: Can slow response on the
SQLOLEDB/ADO driver side affect duration times in SQL Profiler ?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:ucLVCUxYGHA.3880@.TK2MSFTNGP04.phx.gbl...
> Google "parameter sniffing".
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> "zomer" <noneee@.gmail.com> wrote in message
> news:1145384015.190289.310680@.e56g2000cwe.googlegroups.com...
> I have 4 processor SQL server. When I run this query in query analyzer
> (two table joins with w
ly aggregation approx 500,000 rows each) ...> it takes only 7 seconds... when I run it in a stored procedure... it
> takes about 60 minutes. I dont see parallelism in the execution plan of
> SP... I have already tried hint maxdop... it did'nt work... Im not
> sure what I might be running into'
> Any help is greatly appreciated...
>|||I think what you're seeing is data and/or plan caching - and that's by
design. When a query first enters SQL Server, a plan is created and cached.
This takes time. Upon subsequent execution, the original plan is (likely)
used, and this goes faster. However, any data that were read by the
just-executed query are likely now in data cache. Thus, the next time the
query is run, it's getting the data from cache - not from disk. The more
RAM you have, the bigger the cache you have - and the faster (in most cases)
that SQL Server will run.
If you want a pure apples to apples comparison, run the following before
each test:
DBCC FREEPROCCACHE
DBCC DROPCLEANBUFFERS
This flushes the proc and data caches, respectively. Now, you get a fresh
plan - and you get your data from disk. A subsequent run without running
these DBCC's should go significantly faster.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Jansen" <mjansen_nntp@.mail.com> wrote in message
news:uTK$ihxYGHA.1192@.TK2MSFTNGP03.phx.gbl...
Tom -
Are there other things besides the parameter sniffing that could cause the
performance difference?
I'm running into a similar problem, except here's what's happening:
1. I have SQL Profiler on in production.
2. I catch the "slow" procedure
3. Immediately I copy and paste the text into Query Analyzer and execute the
query on the same production server -- and it executes quickly.
Same parameters. Same execution plan I would think (I'm not seeing any
recompiles). The parameter sniffing discussion made sense but it doesn't
seem to fit this scenario since the procedure is already compiled and I'm
executing it with the same paramters that made it run slow from the app.
Thanks for any help,
Mike
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:ucLVCUxYGHA.3880@.TK2MSFTNGP04.phx.gbl...
> Google "parameter sniffing".
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> "zomer" <noneee@.gmail.com> wrote in message
> news:1145384015.190289.310680@.e56g2000cwe.googlegroups.com...
> I have 4 processor SQL server. When I run this query in query analyzer
> (two table joins with w
ly aggregation approx 500,000 rows each) ...> it takes only 7 seconds... when I run it in a stored procedure... it
> takes about 60 minutes. I dont see parallelism in the execution plan of
> SP... I have already tried hint maxdop... it did'nt work... Im not
> sure what I might be running into'
> Any help is greatly appreciated...
>|||Im glad you mentioned that... the only difference of execution plan is
that the if I use query analyzer... it uses parallelism while stored
procedure does not. Why is it so' The server load is pretty
consistent.|||You may want to search on "firehose cursor".
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Jansen" <mjansen_nntp@.mail.com> wrote in message
news:e%236DQxxYGHA.3832@.TK2MSFTNGP04.phx.gbl...
> Duration on the Profiler is the time between receiving the statement and
> the
> last row being retrieved.
Cool. That's what I was suspecting.
> My guess is that your ADO may not be optimal.
It's a single call to Recordset.Open with a client side cursor so there's
not much other than tuning some settings I can do. I think its time to take
this issue to the ADO forum. Thanks for all your input.
Mike|||I'm thinking it's ADO-related.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"zomer" <noneee@.gmail.com> wrote in message
news:1145387868.100688.258810@.e56g2000cwe.googlegroups.com...
yes... datatypes are the same.
Subscribe to:
Posts (Atom)