![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Entry tags:
Nothin' beats nothin'
Gotta love vague and mysterious error messages.
Take MS SQL Server, for instance. I'm writing a query, and it passes the syntax check just fine. Execute the query and you get:
So I go to look up more info on that error message number, and the help documentation says:
How helpful.
Any SQL gurus out there? The concept of the query isn't all that complex or challenging - I'm just having a problem coming up with the actual SQL to get what I want.
Take MS SQL Server, for instance. I'm writing a query, and it passes the syntax check just fine. Execute the query and you get:
Server: Msg 8624, Level 16, State 21, Line 1 Internal SQL Server error.
So I go to look up more info on that error message number, and the help documentation says:
8624 - Internal SQL Server error.
How helpful.
Any SQL gurus out there? The concept of the query isn't all that complex or challenging - I'm just having a problem coming up with the actual SQL to get what I want.
no subject
That discussion thread at tek-tips lead me to a MS article with a workaround that appears to be working.
I had a MAX() expression in a subquery that was part of my overall select statement, and that seems to be what was causing the error.
The query is now humming away - hopefully it will return without error and without running all day. LOL!
Thanks!
no subject