This error message is generated from ODBC, and not really
from SQL Server. It is generated when a connection
something the ODBC fails ie DB2 (see Microsoft) so
although SQL Server is reporting it, it is not the cause.
I would sugest that you go through the Event View on your
NT, or put in a trace to see exactly where it fails.
J
>--Original Message--
>Receiving error:
>"General network error. Check your network documentation.
[SQLSTATE 08S01]
>(Error 11)".
>Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
>This started after we rebuild the server. We have tens
of jobs that run at
>night. This error is happening only randomly as some
days nothing happens
>and same job runs fine but other day it blows up. It is
not happening with
>same job either. Then we restart the job and it runs
fine.
>
>.
>
Nothing in the event log or SQLServer log accept that error message.
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:1302301c4433d$9f6096f0$a101280a@.phx.gbl...[vbcol=seagreen]
> This error message is generated from ODBC, and not really
> from SQL Server. It is generated when a connection
> something the ODBC fails ie DB2 (see Microsoft) so
> although SQL Server is reporting it, it is not the cause.
> I would sugest that you go through the Event View on your
> NT, or put in a trace to see exactly where it fails.
> J
>
> [SQLSTATE 08S01]
> of jobs that run at
> days nothing happens
> not happening with
> fine.
|||Hi ilovesql,
We are expiriencing the same issue - I was woundering if you had this resolved.
I also wanted to ask you - when you rebuild the server did it have the same configuration as before or you installed SP3 for SQL Server?
We went from Win2000 server SQL server 2000 SP2 to WIN2003 server SP3 and we started to have this problem from that day on. Microsoft is working on it but this is the second day and they haven't came up with the solution.
I think it is SP3 - something is not right with it.
Thanks,
Anna
"ilovesql" wrote:
> Nothing in the event log or SQLServer log accept that error message.
>
> "Julie" <anonymous@.discussions.microsoft.com> wrote in message
> news:1302301c4433d$9f6096f0$a101280a@.phx.gbl...
>
>
Showing posts with label odbc. Show all posts
Showing posts with label odbc. Show all posts
Thursday, March 29, 2012
General network error.
This error message is generated from ODBC, and not really
from SQL Server. It is generated when a connection
something the ODBC fails ie DB2 (see Microsoft) so
although SQL Server is reporting it, it is not the cause.
I would sugest that you go through the Event View on your
NT, or put in a trace to see exactly where it fails.
J
>--Original Message--
>Receiving error:
>"General network error. Check your network documentation.
[SQLSTATE 08S01]
>(Error 11)".
>Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
>This started after we rebuild the server. We have tens
of jobs that run at
>night. This error is happening only randomly as some
days nothing happens
>and same job runs fine but other day it blows up. It is
not happening with
>same job either. Then we restart the job and it runs
fine.
>
>.
>Nothing in the event log or SQLServer log accept that error message.
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:1302301c4433d$9f6096f0$a101280a@.phx
.gbl...[vbcol=seagreen]
> This error message is generated from ODBC, and not really
> from SQL Server. It is generated when a connection
> something the ODBC fails ie DB2 (see Microsoft) so
> although SQL Server is reporting it, it is not the cause.
> I would sugest that you go through the Event View on your
> NT, or put in a trace to see exactly where it fails.
> J
>
> [SQLSTATE 08S01]
> of jobs that run at
> days nothing happens
> not happening with
> fine.|||Hi ilovesql,
We are expiriencing the same issue - I was woundering if you had this resolv
ed.
I also wanted to ask you - when you rebuild the server did it have the same
configuration as before or you installed SP3 for SQL Server?
We went from Win2000 server SQL server 2000 SP2 to WIN2003 server SP3 and we
started to have this problem from that day on. Microsoft is working on it b
ut this is the second day and they haven't came up with the solution.
I think it is SP3 - something is not right with it.
Thanks,
Anna
"ilovesql" wrote:
> Nothing in the event log or SQLServer log accept that error message.
>
> "Julie" <anonymous@.discussions.microsoft.com> wrote in message
> news:1302301c4433d$9f6096f0$a101280a@.phx
.gbl...
>
>sql
from SQL Server. It is generated when a connection
something the ODBC fails ie DB2 (see Microsoft) so
although SQL Server is reporting it, it is not the cause.
I would sugest that you go through the Event View on your
NT, or put in a trace to see exactly where it fails.
J
>--Original Message--
>Receiving error:
>"General network error. Check your network documentation.
[SQLSTATE 08S01]
>(Error 11)".
>Running on SQLServer 2000 EE, SP3, Windows 2000 Adv.
>This started after we rebuild the server. We have tens
of jobs that run at
>night. This error is happening only randomly as some
days nothing happens
>and same job runs fine but other day it blows up. It is
not happening with
>same job either. Then we restart the job and it runs
fine.
>
>.
>Nothing in the event log or SQLServer log accept that error message.
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:1302301c4433d$9f6096f0$a101280a@.phx
.gbl...[vbcol=seagreen]
> This error message is generated from ODBC, and not really
> from SQL Server. It is generated when a connection
> something the ODBC fails ie DB2 (see Microsoft) so
> although SQL Server is reporting it, it is not the cause.
> I would sugest that you go through the Event View on your
> NT, or put in a trace to see exactly where it fails.
> J
>
> [SQLSTATE 08S01]
> of jobs that run at
> days nothing happens
> not happening with
> fine.|||Hi ilovesql,
We are expiriencing the same issue - I was woundering if you had this resolv
ed.
I also wanted to ask you - when you rebuild the server did it have the same
configuration as before or you installed SP3 for SQL Server?
We went from Win2000 server SQL server 2000 SP2 to WIN2003 server SP3 and we
started to have this problem from that day on. Microsoft is working on it b
ut this is the second day and they haven't came up with the solution.
I think it is SP3 - something is not right with it.
Thanks,
Anna
"ilovesql" wrote:
> Nothing in the event log or SQLServer log accept that error message.
>
> "Julie" <anonymous@.discussions.microsoft.com> wrote in message
> news:1302301c4433d$9f6096f0$a101280a@.phx
.gbl...
>
>sql
Monday, March 26, 2012
General Access Project info
Hi all, we currently have an access databse with linked odbc connections to an SQL server database.
Performance wise I don't think this is great.
Anyone have any general information about doing an upgrade to a micrsoft project database, and what are the pros and cons of access projects compared to Access databases with linked tables.
About 30 -40 users currently hammer the access front end during the day.Access Data Projects are MUCH better than Access MDB databases with linked tables. Off the top of my head I can't think of any advantage to using an MDB with linked tables instead of going with an ADP file.|||OK, one disadvantage: You cannot store ANY tables locally in an Access ADP file, so any setup or configuration data cannot be stored on the user's machine (at least in the database file).
Performance wise I don't think this is great.
Anyone have any general information about doing an upgrade to a micrsoft project database, and what are the pros and cons of access projects compared to Access databases with linked tables.
About 30 -40 users currently hammer the access front end during the day.Access Data Projects are MUCH better than Access MDB databases with linked tables. Off the top of my head I can't think of any advantage to using an MDB with linked tables instead of going with an ADP file.|||OK, one disadvantage: You cannot store ANY tables locally in an Access ADP file, so any setup or configuration data cannot be stored on the user's machine (at least in the database file).
Wednesday, March 7, 2012
Function (fn locate(@p1, P_fam_nm))
In the profiler, I saw the following constructions as part of a statement :
(fn locate(@.p1, P_fam_nm))= 1
This look to me as an ODBC function, but I cannot find the function
described in the BOL. The function is problably replaced by a SQL-server
function. (Could be patindex).
Where and how can I find which function is used in SQL-server instead.
Or can SQL-server run this type (ODBC ?) functions ?
ben brugmanI've never heard of that function. I googled it and didn't see any hits
associated with ODBC or MDAC. It doesn't exist on my server. So... I suspect
it's a user defined function.
You can run this statement in all your databases to see where the function
exists.
select * from sysobjects where name like 'fn_locate'
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"ben brugman" <ben@.niethier.nl> wrote in message
news:ebZVBx1sDHA.2508@.TK2MSFTNGP12.phx.gbl...
> In the profiler, I saw the following constructions as part of a statement
:
> (fn locate(@.p1, P_fam_nm))= 1
> This look to me as an ODBC function, but I cannot find the function
> described in the BOL. The function is problably replaced by a SQL-server
> function. (Could be patindex).
> Where and how can I find which function is used in SQL-server instead.
> Or can SQL-server run this type (ODBC ?) functions ?
> ben brugman
>|||I see in in the profiler, the coding using it, does work.
The syntax is <(FN locate(string1,string2))
The FN denotes the a function follows.
Behind the FN is a space.
If it is a user defined function the calling program
does define the function before it is called, because
it is not inserted by 'humans'.
And the function does not work from the QA so it
is not present as such.
I'll have a check if the calling program is defining the
function, but this is unlikely to me.
(The workings of the function is very similar (or equal to)
patindex).
ben brugman
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:ucz3LR2sDHA.3492@.TK2MSFTNGP11.phx.gbl...
> I've never heard of that function. I googled it and didn't see any hits
> associated with ODBC or MDAC. It doesn't exist on my server. So... I
suspect
> it's a user defined function.
> You can run this statement in all your databases to see where the function
> exists.
> select * from sysobjects where name like 'fn_locate'
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:ebZVBx1sDHA.2508@.TK2MSFTNGP12.phx.gbl...
> > In the profiler, I saw the following constructions as part of a
statement
> :
> >
> > (fn locate(@.p1, P_fam_nm))= 1
> >
> > This look to me as an ODBC function, but I cannot find the function
> > described in the BOL. The function is problably replaced by a SQL-server
> > function. (Could be patindex).
> >
> > Where and how can I find which function is used in SQL-server instead.
> > Or can SQL-server run this type (ODBC ?) functions ?
> >
> > ben brugman
> >
> >
>
(fn locate(@.p1, P_fam_nm))= 1
This look to me as an ODBC function, but I cannot find the function
described in the BOL. The function is problably replaced by a SQL-server
function. (Could be patindex).
Where and how can I find which function is used in SQL-server instead.
Or can SQL-server run this type (ODBC ?) functions ?
ben brugmanI've never heard of that function. I googled it and didn't see any hits
associated with ODBC or MDAC. It doesn't exist on my server. So... I suspect
it's a user defined function.
You can run this statement in all your databases to see where the function
exists.
select * from sysobjects where name like 'fn_locate'
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"ben brugman" <ben@.niethier.nl> wrote in message
news:ebZVBx1sDHA.2508@.TK2MSFTNGP12.phx.gbl...
> In the profiler, I saw the following constructions as part of a statement
:
> (fn locate(@.p1, P_fam_nm))= 1
> This look to me as an ODBC function, but I cannot find the function
> described in the BOL. The function is problably replaced by a SQL-server
> function. (Could be patindex).
> Where and how can I find which function is used in SQL-server instead.
> Or can SQL-server run this type (ODBC ?) functions ?
> ben brugman
>|||I see in in the profiler, the coding using it, does work.
The syntax is <(FN locate(string1,string2))
The FN denotes the a function follows.
Behind the FN is a space.
If it is a user defined function the calling program
does define the function before it is called, because
it is not inserted by 'humans'.
And the function does not work from the QA so it
is not present as such.
I'll have a check if the calling program is defining the
function, but this is unlikely to me.
(The workings of the function is very similar (or equal to)
patindex).
ben brugman
"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:ucz3LR2sDHA.3492@.TK2MSFTNGP11.phx.gbl...
> I've never heard of that function. I googled it and didn't see any hits
> associated with ODBC or MDAC. It doesn't exist on my server. So... I
suspect
> it's a user defined function.
> You can run this statement in all your databases to see where the function
> exists.
> select * from sysobjects where name like 'fn_locate'
> --
> Brian Moran
> Principal Mentor
> Solid Quality Learning
> SQL Server MVP
> http://www.solidqualitylearning.com
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:ebZVBx1sDHA.2508@.TK2MSFTNGP12.phx.gbl...
> > In the profiler, I saw the following constructions as part of a
statement
> :
> >
> > (fn locate(@.p1, P_fam_nm))= 1
> >
> > This look to me as an ODBC function, but I cannot find the function
> > described in the BOL. The function is problably replaced by a SQL-server
> > function. (Could be patindex).
> >
> > Where and how can I find which function is used in SQL-server instead.
> > Or can SQL-server run this type (ODBC ?) functions ?
> >
> > ben brugman
> >
> >
>
Subscribe to:
Posts (Atom)