Error disconnecting clients with ODBC Error

I keep getting an ODBC error (varies) I have SQL 7 on windows 2000 server
with all the updated service packs and patches for the OS and SQL. I also
updated MDAC to 2.8 sp2. We use a third party software program that connects
to the SQL database to store all our data. Every so often we get
disconnected with an ODBC error and have to close the client then reconnect
to the server. The frequency is pretty sparatic sometimes it can occur 5
times and hour or as little as 1 time an hour. Attached is a copy of one of
the error we get if anyone has any ideas as to what could be causing this I
would greatly appreciate it.
ConnectionWrite (WrapperWrite()).
Last SQL String:
select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
MType='M' and MDateTime<=1124822591
Last ODBC Command:
Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
MStatus='U' and MType='M' and MDateTime<=1124822591'
It's pretty hard to say from what's posted. This looks like
it's a HEAT database. If that's the case, Tracing their
sporadic errors with ODBC tracing will slow things down
quite a bit. You can but it's pretty bad on performance. Try
contacting the vendor, Front Range Solutions. That's
generally quicker.
-Sue
On Tue, 23 Aug 2005 12:33:04 -0700, "Anthony"
<Anthony@.discussions.microsoft.com> wrote:

>I keep getting an ODBC error (varies) I have SQL 7 on windows 2000 server
>with all the updated service packs and patches for the OS and SQL. I also
>updated MDAC to 2.8 sp2. We use a third party software program that connects
>to the SQL database to store all our data. Every so often we get
>disconnected with an ODBC error and have to close the client then reconnect
>to the server. The frequency is pretty sparatic sometimes it can occur 5
>times and hour or as little as 1 time an hour. Attached is a copy of one of
>the error we get if anyone has any ideas as to what could be causing this I
>would greatly appreciate it.
>ConnectionWrite (WrapperWrite()).
>Last SQL String:
>select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
>MType='M' and MDateTime<=1124822591
>Last ODBC Command:
>Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
>MStatus='U' and MType='M' and MDateTime<=1124822591'
>
|||Anthony,
Try using another ODBC tool like WinSQL
(http://www.synametrics.com/winsql) and see if you get the same behavior.
How far is your database from your client? This could also be a network
issue.
Anthony wrote:
> I keep getting an ODBC error (varies) I have SQL 7 on windows 2000 server
> with all the updated service packs and patches for the OS and SQL. I also
> updated MDAC to 2.8 sp2. We use a third party software program that connects
> to the SQL database to store all our data. Every so often we get
> disconnected with an ODBC error and have to close the client then reconnect
> to the server. The frequency is pretty sparatic sometimes it can occur 5
> times and hour or as little as 1 time an hour. Attached is a copy of one of
> the error we get if anyone has any ideas as to what could be causing this I
> would greatly appreciate it.
> ConnectionWrite (WrapperWrite()).
> Last SQL String:
> select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
> MType='M' and MDateTime<=1124822591
> Last ODBC Command:
> Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
> MStatus='U' and MType='M' and MDateTime<=1124822591'
>
|||I will look into winsql, thanks. As far as the nework goes everything is in
the same physical location. I have checked network performance and nothing
indicates that it could be a performance problem.
"Dennis Black" wrote:

> Anthony,
> Try using another ODBC tool like WinSQL
> (http://www.synametrics.com/winsql) and see if you get the same behavior.
> How far is your database from your client? This could also be a network
> issue.
>
> Anthony wrote:
>

Error disconnecting clients with ODBC Error

I keep getting an ODBC error (varies) I have SQL 7 on Windows 2000 server
with all the updated service packs and patches for the OS and SQL. I also
updated MDAC to 2.8 sp2. We use a third party software program that connect
s
to the SQL database to store all our data. Every so often we get
disconnected with an ODBC error and have to close the client then reconnect
to the server. The frequency is pretty sparatic sometimes it can occur 5
times and hour or as little as 1 time an hour. Attached is a copy of one of
the error we get if anyone has any ideas as to what could be causing this I
would greatly appreciate it.
ConnectionWrite (WrapperWrite()).
Last SQL String:
select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
MType='M' and MDateTime<=1124822591
Last ODBC Command:
Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
MStatus='U' and MType='M' and MDateTime<=1124822591'It's pretty hard to say from what's posted. This looks like
it's a HEAT database. If that's the case, Tracing their
sporadic errors with ODBC tracing will slow things down
quite a bit. You can but it's pretty bad on performance. Try
contacting the vendor, Front Range Solutions. That's
generally quicker.
-Sue
On Tue, 23 Aug 2005 12:33:04 -0700, "Anthony"
<Anthony@.discussions.microsoft.com> wrote:

>I keep getting an ODBC error (varies) I have SQL 7 on Windows 2000 server
>with all the updated service packs and patches for the OS and SQL. I also
>updated MDAC to 2.8 sp2. We use a third party software program that connec
ts
>to the SQL database to store all our data. Every so often we get
>disconnected with an ODBC error and have to close the client then reconnect
>to the server. The frequency is pretty sparatic sometimes it can occur 5
>times and hour or as little as 1 time an hour. Attached is a copy of one o
f
>the error we get if anyone has any ideas as to what could be causing this I
>would greatly appreciate it.
>ConnectionWrite (WrapperWrite()).
>Last SQL String:
>select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
>MType='M' and MDateTime<=1124822591
>Last ODBC Command:
>Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
>MStatus='U' and MType='M' and MDateTime<=1124822591'
>|||Anthony,
Try using another ODBC tool like WinSQL
(http://www.synametrics.com/winsql) and see if you get the same behavior.
How far is your database from your client? This could also be a network
issue.
Anthony wrote:
> I keep getting an ODBC error (varies) I have SQL 7 on Windows 2000 server
> with all the updated service packs and patches for the OS and SQL. I also
> updated MDAC to 2.8 sp2. We use a third party software program that conne
cts
> to the SQL database to store all our data. Every so often we get
> disconnected with an ODBC error and have to close the client then reconnec
t
> to the server. The frequency is pretty sparatic sometimes it can occur 5
> times and hour or as little as 1 time an hour. Attached is a copy of one
of
> the error we get if anyone has any ideas as to what could be causing this
I
> would greatly appreciate it.
> ConnectionWrite (WrapperWrite()).
> Last SQL String:
> select MRecordID from HEATMsg where MTo='Frank' and MStatus='U' and
> MType='M' and MDateTime<=1124822591
> Last ODBC Command:
> Function: SQLPrepare('select MRecordID from HEATMsg where MTo='Frank' and
> MStatus='U' and MType='M' and MDateTime<=1124822591'
>|||I will look into winsql, thanks. As far as the nework goes everything is in
the same physical location. I have checked network performance and nothing
indicates that it could be a performance problem.
"Dennis Black" wrote:

> Anthony,
> Try using another ODBC tool like WinSQL
> (http://www.synametrics.com/winsql) and see if you get the same behavior.
> How far is your database from your client? This could also be a network
> issue.
>
> Anthony wrote:
>

Error creating DB with numerical name?

Hi, all!! Using SQL 2000, latest patches and such; running under Win2k,
latest patches.
When I try to create a database with a numerical name (such as "12345"), I'm
getting an Incorrect Syntax error in code code (script) and in the Query
Analyzer. However, EntMgr will create it perfectly...
I just know this is going to be something simple, but derned if I can see
it... any ideas' :)
Thanks,
JackHi Jack
Put square brackets around any identifiers that don't follow the normal
rules for identifiers. (The normal rule for the identifies says they must
start with a letter, or one of a very few special chars, but not numbers.)
CREATE DATABASE [12345]
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Jack Black" <jackblackisback@.hotmail.com> wrote in message
news:OKH7EKusDHA.2932@.TK2MSFTNGP11.phx.gbl...
> Hi, all!! Using SQL 2000, latest patches and such; running under Win2k,
> latest patches.
> When I try to create a database with a numerical name (such as "12345"),
I'm
> getting an Incorrect Syntax error in code code (script) and in the Query
> Analyzer. However, EntMgr will create it perfectly...
> I just know this is going to be something simple, but derned if I can see
> it... any ideas' :)
> Thanks,
> Jack
>|||To add to Kalen's comments:
You might want to re-think this. Most developers stay away from names that doesn't confirms to the
rules for standard identifiers, as you have to always mess about with delimiters for the name when
you work against the data (and sooner or later you come across this great tools which doesn't
support delimited identifiers).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Jack Black" <jackblackisback@.hotmail.com> wrote in message
news:OKH7EKusDHA.2932@.TK2MSFTNGP11.phx.gbl...
> Hi, all!! Using SQL 2000, latest patches and such; running under Win2k,
> latest patches.
> When I try to create a database with a numerical name (such as "12345"), I'm
> getting an Incorrect Syntax error in code code (script) and in the Query
> Analyzer. However, EntMgr will create it perfectly...
> I just know this is going to be something simple, but derned if I can see
> it... any ideas' :)
> Thanks,
> Jack
>