Showing posts with label buffer. Show all posts
Showing posts with label buffer. Show all posts

Saturday, February 25, 2012

Buffer size not specified error

Error: "The specified buffer size is not valid. [buffer size specified = 0]

Hello, im very new to SQL 2005 everywhere but looked like it could do the job for what i needed:

Im working on a c# (.net 2.0) project and loaded data

(one column from one table, 800 rows, text, no greater than 80characters in length)

from an access db into a data set, then lnserted the data in SQLce, great it works fab!

but as soon as I select another field(text, <=10) from the access db, and try to insert it into sql i get the error...

what have i missed?

could you post the code you are using to do the insertion and some info about the schema of the table you are inserting the records into? then we can see what's going on here.

thanks,

Darren

|||The problem was due to a field size not being long enough, i increased the field size and works great.

Buffer Pool vs MemToLeave Area

Whats in the buffer pool and whats in the memtoleave area ? Is this all in
RAM or could it also be virtual memory/pagefile ? Using SQL 2000Whether it is in virtual memory or not depends on how much ram you have and
how you set your system up. As for what is in there I would suggest you
take a look in BooksOnLine under "memory, pool" and it's associated links in
addition to "Inside SQL 2000" which I know you have now<g>.
Andrew J. Kelly
SQL Server MVP
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23rFuqtE9DHA.3012@.TK2MSFTNGP09.phx.gbl...
> Whats in the buffer pool and whats in the memtoleave area ? Is this all in
> RAM or could it also be virtual memory/pagefile ? Using SQL 2000
>|||I didn't really talk about the memtoleave value in the book, but I discussed
it here
http://www.sqlmag.com/Articles/Inde...ArticleID=16522
The above article is several years old now, so it is freely accessible.
I also wrote two articles on memory in SQL Server Magazine last March and
April, but those are only available to subscribers, as they are less than a
year old.
http://www.sqlmag.com/Articles/Inde...ArticleID=37890
http://www.sqlmag.com/Articles/Inde...ArticleID=37908
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:#GqikKJ9DHA.1548@.tk2msftngp13.phx.gbl...
> Whether it is in virtual memory or not depends on how much ram you have
and
> how you set your system up. As for what is in there I would suggest you
> take a look in BooksOnLine under "memory, pool" and it's associated links
in
> addition to "Inside SQL 2000" which I know you have now<g>.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23rFuqtE9DHA.3012@.TK2MSFTNGP09.phx.gbl...
in
>|||Probably not but you do discuss the memory pool<g>.
Andrew J. Kelly
SQL Server MVP
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:uE1kiAL9DHA.2832@.tk2msftngp13.phx.gbl...
> I didn't really talk about the memtoleave value in the book, but I
discussed
> it here
> http://www.sqlmag.com/Articles/Inde...ArticleID=16522
> The above article is several years old now, so it is freely accessible.
> I also wrote two articles on memory in SQL Server Magazine last March and
> April, but those are only available to subscribers, as they are less than
a
> year old.
> http://www.sqlmag.com/Articles/Inde...ArticleID=37890
> http://www.sqlmag.com/Articles/Inde...ArticleID=37908
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:#GqikKJ9DHA.1548@.tk2msftngp13.phx.gbl...
> and
links
> in
all
> in
>|||Have a look at
http://msdn.microsoft.com/data/defa...ev_01262004.asp
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23rFuqtE9DHA.3012@.TK2MSFTNGP09.phx.gbl...
> Whats in the buffer pool and whats in the memtoleave area ? Is this all in
> RAM or could it also be virtual memory/pagefile ? Using SQL 2000
>|||That's a good one Jasper. How did I miss that?
Andrew J. Kelly
SQL Server MVP
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:eanijzL9DHA.2064@.TK2MSFTNGP11.phx.gbl...
> Have a look at
>
http://msdn.microsoft.com/data/defa...004.
asp
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23rFuqtE9DHA.3012@.TK2MSFTNGP09.phx.gbl...
in
>

Buffer Pool vs MemToLeave Area

Whats in the buffer pool and whats in the memtoleave area ? Is this all in
RAM or could it also be virtual memory/pagefile ? Using SQL 2000Whether it is in virtual memory or not depends on how much ram you have and
how you set your system up. As for what is in there I would suggest you
take a look in BooksOnLine under "memory, pool" and it's associated links in
addition to "Inside SQL 2000" which I know you have now<g>.
--
Andrew J. Kelly
SQL Server MVP
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23rFuqtE9DHA.3012@.TK2MSFTNGP09.phx.gbl...
> Whats in the buffer pool and whats in the memtoleave area ? Is this all in
> RAM or could it also be virtual memory/pagefile ? Using SQL 2000
>|||I didn't really talk about the memtoleave value in the book, but I discussed
it here
http://www.sqlmag.com/Articles/Index.cfm?ArticleID=16522
The above article is several years old now, so it is freely accessible.
I also wrote two articles on memory in SQL Server Magazine last March and
April, but those are only available to subscribers, as they are less than a
year old.
http://www.sqlmag.com/Articles/Index.cfm?ArticleID=37890
http://www.sqlmag.com/Articles/Index.cfm?ArticleID=37908
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:#GqikKJ9DHA.1548@.tk2msftngp13.phx.gbl...
> Whether it is in virtual memory or not depends on how much ram you have
and
> how you set your system up. As for what is in there I would suggest you
> take a look in BooksOnLine under "memory, pool" and it's associated links
in
> addition to "Inside SQL 2000" which I know you have now<g>.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23rFuqtE9DHA.3012@.TK2MSFTNGP09.phx.gbl...
> > Whats in the buffer pool and whats in the memtoleave area ? Is this all
in
> > RAM or could it also be virtual memory/pagefile ? Using SQL 2000
> >
> >
>|||Probably not but you do discuss the memory pool<g>.
--
Andrew J. Kelly
SQL Server MVP
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:uE1kiAL9DHA.2832@.tk2msftngp13.phx.gbl...
> I didn't really talk about the memtoleave value in the book, but I
discussed
> it here
> http://www.sqlmag.com/Articles/Index.cfm?ArticleID=16522
> The above article is several years old now, so it is freely accessible.
> I also wrote two articles on memory in SQL Server Magazine last March and
> April, but those are only available to subscribers, as they are less than
a
> year old.
> http://www.sqlmag.com/Articles/Index.cfm?ArticleID=37890
> http://www.sqlmag.com/Articles/Index.cfm?ArticleID=37908
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:#GqikKJ9DHA.1548@.tk2msftngp13.phx.gbl...
> > Whether it is in virtual memory or not depends on how much ram you have
> and
> > how you set your system up. As for what is in there I would suggest you
> > take a look in BooksOnLine under "memory, pool" and it's associated
links
> in
> > addition to "Inside SQL 2000" which I know you have now<g>.
> >
> > --
> >
> > Andrew J. Kelly
> > SQL Server MVP
> >
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:%23rFuqtE9DHA.3012@.TK2MSFTNGP09.phx.gbl...
> > > Whats in the buffer pool and whats in the memtoleave area ? Is this
all
> in
> > > RAM or could it also be virtual memory/pagefile ? Using SQL 2000
> > >
> > >
> >
> >
>|||Have a look at
http://msdn.microsoft.com/data/default.aspx?pull=/library/en-us/dnsqldev/html/sqldev_01262004.asp
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23rFuqtE9DHA.3012@.TK2MSFTNGP09.phx.gbl...
> Whats in the buffer pool and whats in the memtoleave area ? Is this all in
> RAM or could it also be virtual memory/pagefile ? Using SQL 2000
>|||That's a good one Jasper. How did I miss that?
--
Andrew J. Kelly
SQL Server MVP
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:eanijzL9DHA.2064@.TK2MSFTNGP11.phx.gbl...
> Have a look at
>
http://msdn.microsoft.com/data/default.aspx?pull=/library/en-us/dnsqldev/html/sqldev_01262004.asp
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23rFuqtE9DHA.3012@.TK2MSFTNGP09.phx.gbl...
> > Whats in the buffer pool and whats in the memtoleave area ? Is this all
in
> > RAM or could it also be virtual memory/pagefile ? Using SQL 2000
> >
> >
>

buffer pool only has data pages ?

Or does the buffer pool include procedure cache as well ?
I know in sql 2000, they have this mem to leave concept that I have heard is
no longer referred to in 2005. So whats it called in 2005?
ThanksCome on now Hassan this is getting beyond petty. Do you really expect
everyone to spoon feed you everything about SQL Server just because you
don't want to read a book or do a simple Google search. The answer to this
is certainly something you should already know by now but can be found in at
least 20 places with little trouble. Heck even BooksOnLine can answer that
question easily. 95% of the questions you ask here can be found in "Inside
SQL Server 2005" alone. Do everyone including yourself a favor and buy the
book and take a little time to read it. Or at least the sections that are
relevant to what you need to know at the time. You won't regret it.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Hassan" <hassan@.test.com> wrote in message
news:Om2ZjtcZIHA.4696@.TK2MSFTNGP05.phx.gbl...
> Or does the buffer pool include procedure cache as well ?
> I know in sql 2000, they have this mem to leave concept that I have heard
> is no longer referred to in 2005. So whats it called in 2005?
> Thanks|||Andrew J. Kelly wrote:
> Come on now Hassan this is getting beyond petty. Do you really expect
> everyone to spoon feed you everything about SQL Server just because
> you don't want to read a book or do a simple Google search. The answer
> to this is certainly something you should already know by now but can
> be found in at least 20 places with little trouble. Heck even
> BooksOnLine can answer that question easily. 95% of the questions you
> ask here can be found in "Inside SQL Server 2005" alone. Do everyone
> including yourself a favor and buy the book and take a little time to
> read it. Or at least the sections that are relevant to what you need
> to know at the time. You won't regret it.
>
And neither will we :)

Buffer Overrun?

Over the past couple of days we have seen the following message in the SQL
Server Logs:
"SqlSecurityHandler is invoked. Potential buffer overrun detected - server
is terminating."
At this point, the SQL Server and SQL Server Agent will terminate and have
to be restarted. We are running SQL2000(SP4) on Windows Server '03 (no SP).
Has anyone else seen this?We've just seen the error. Our production environment went down with that
message in the log. It took about 8 hours before we were up and running
again. (The Sql Server automatically started a restore operation)
We are also running SQL2000(SP4) on Windows Server 2003.
Veritas NetBackup had just finished a backup when the error occurred.
I really hope that Microsoft can help out with this, cause this is a
_serious_ problem.
SQL server just terminates!
Do you have any new information?
"JKKUS" wrote:

> Over the past couple of days we have seen the following message in the SQL
> Server Logs:
> "SqlSecurityHandler is invoked. Potential buffer overrun detected - server
> is terminating."
> At this point, the SQL Server and SQL Server Agent will terminate and have
> to be restarted. We are running SQL2000(SP4) on Windows Server '03 (no SP
).
> Has anyone else seen this?
>|||Nothing yet. If you find anything out, please post. This problem is annoyi
ng.
"Bjorn L" wrote:
[vbcol=seagreen]
> We've just seen the error. Our production environment went down with that
> message in the log. It took about 8 hours before we were up and running
> again. (The Sql Server automatically started a restore operation)
> We are also running SQL2000(SP4) on Windows Server 2003.
> Veritas NetBackup had just finished a backup when the error occurred.
> I really hope that Microsoft can help out with this, cause this is a
> _serious_ problem.
> SQL server just terminates!
> Do you have any new information?
> "JKKUS" wrote:
>|||Its more than annoying to us, since our production database shuts down.
Anyway, from what we've seen, it definitely seems to be related to backups.
We disabled all backup activities this weekend, and from that on we haven't
seen the problem. (fingers crossed though)
We'll keep investigating.
Would be interesting to hear if its backups thats causing your problems as
well?
"JKKUS" wrote:
[vbcol=seagreen]
> Nothing yet. If you find anything out, please post. This problem is anno
ying.
> "Bjorn L" wrote:
>

Buffer Overrun?

Over the past couple of days we have seen the following message in the SQL
Server Logs:
"SqlSecurityHandler is invoked. Potential buffer overrun detected - server
is terminating."
At this point, the SQL Server and SQL Server Agent will terminate and have
to be restarted. We are running SQL2000(SP4) on Windows Server '03 (no SP).
Has anyone else seen this?
We've just seen the error. Our production environment went down with that
message in the log. It took about 8 hours before we were up and running
again. (The Sql Server automatically started a restore operation)
We are also running SQL2000(SP4) on Windows Server 2003.
Veritas NetBackup had just finished a backup when the error occurred.
I really hope that Microsoft can help out with this, cause this is a
_serious_ problem.
SQL server just terminates!
Do you have any new information?
"JKKUS" wrote:

> Over the past couple of days we have seen the following message in the SQL
> Server Logs:
> "SqlSecurityHandler is invoked. Potential buffer overrun detected - server
> is terminating."
> At this point, the SQL Server and SQL Server Agent will terminate and have
> to be restarted. We are running SQL2000(SP4) on Windows Server '03 (no SP).
> Has anyone else seen this?
>
|||Nothing yet. If you find anything out, please post. This problem is annoying.
"Bjorn L" wrote:
[vbcol=seagreen]
> We've just seen the error. Our production environment went down with that
> message in the log. It took about 8 hours before we were up and running
> again. (The Sql Server automatically started a restore operation)
> We are also running SQL2000(SP4) on Windows Server 2003.
> Veritas NetBackup had just finished a backup when the error occurred.
> I really hope that Microsoft can help out with this, cause this is a
> _serious_ problem.
> SQL server just terminates!
> Do you have any new information?
> "JKKUS" wrote:
|||Its more than annoying to us, since our production database shuts down.
Anyway, from what we've seen, it definitely seems to be related to backups.
We disabled all backup activities this weekend, and from that on we haven't
seen the problem. (fingers crossed though)
We'll keep investigating.
Would be interesting to hear if its backups thats causing your problems as
well?
"JKKUS" wrote:
[vbcol=seagreen]
> Nothing yet. If you find anything out, please post. This problem is annoying.
> "Bjorn L" wrote:

Buffer Overrun?

Over the past couple of days we have seen the following message in the SQL
Server Logs:
"SqlSecurityHandler is invoked. Potential buffer overrun detected - server
is terminating."
At this point, the SQL Server and SQL Server Agent will terminate and have
to be restarted. We are running SQL2000(SP4) on Windows Server '03 (no SP).
Has anyone else seen this?We've just seen the error. Our production environment went down with that
message in the log. It took about 8 hours before we were up and running
again. (The Sql Server automatically started a restore operation)
We are also running SQL2000(SP4) on Windows Server 2003.
Veritas NetBackup had just finished a backup when the error occurred.
I really hope that Microsoft can help out with this, cause this is a
_serious_ problem.
SQL server just terminates!
Do you have any new information?
"JKKUS" wrote:
> Over the past couple of days we have seen the following message in the SQL
> Server Logs:
> "SqlSecurityHandler is invoked. Potential buffer overrun detected - server
> is terminating."
> At this point, the SQL Server and SQL Server Agent will terminate and have
> to be restarted. We are running SQL2000(SP4) on Windows Server '03 (no SP).
> Has anyone else seen this?
>|||Nothing yet. If you find anything out, please post. This problem is annoying.
"Bjorn L" wrote:
> We've just seen the error. Our production environment went down with that
> message in the log. It took about 8 hours before we were up and running
> again. (The Sql Server automatically started a restore operation)
> We are also running SQL2000(SP4) on Windows Server 2003.
> Veritas NetBackup had just finished a backup when the error occurred.
> I really hope that Microsoft can help out with this, cause this is a
> _serious_ problem.
> SQL server just terminates!
> Do you have any new information?
> "JKKUS" wrote:
> > Over the past couple of days we have seen the following message in the SQL
> > Server Logs:
> >
> > "SqlSecurityHandler is invoked. Potential buffer overrun detected - server
> > is terminating."
> >
> > At this point, the SQL Server and SQL Server Agent will terminate and have
> > to be restarted. We are running SQL2000(SP4) on Windows Server '03 (no SP).
> > Has anyone else seen this?
> >
> >|||Its more than annoying to us, since our production database shuts down.
Anyway, from what we've seen, it definitely seems to be related to backups.
We disabled all backup activities this weekend, and from that on we haven't
seen the problem. (fingers crossed though)
We'll keep investigating.
Would be interesting to hear if its backups thats causing your problems as
well?
"JKKUS" wrote:
> Nothing yet. If you find anything out, please post. This problem is annoying.
> "Bjorn L" wrote:
> > We've just seen the error. Our production environment went down with that
> > message in the log. It took about 8 hours before we were up and running
> > again. (The Sql Server automatically started a restore operation)
> >
> > We are also running SQL2000(SP4) on Windows Server 2003.
> > Veritas NetBackup had just finished a backup when the error occurred.
> >
> > I really hope that Microsoft can help out with this, cause this is a
> > _serious_ problem.
> > SQL server just terminates!
> >
> > Do you have any new information?
> >
> > "JKKUS" wrote:
> >
> > > Over the past couple of days we have seen the following message in the SQL
> > > Server Logs:
> > >
> > > "SqlSecurityHandler is invoked. Potential buffer overrun detected - server
> > > is terminating."
> > >
> > > At this point, the SQL Server and SQL Server Agent will terminate and have
> > > to be restarted. We are running SQL2000(SP4) on Windows Server '03 (no SP).
> > > Has anyone else seen this?
> > >
> > >

Buffer Overrun reported in SQLDiag

I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
(Active/ Passive), and have started to get Buffer Overrun errors on running
SQLDiag - as follows :
/********************************
Event ID:26
User:N/A
Description:
Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
detected!
Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
/********************************
SQLDiag is being run by an SQL job running an OS command as follows :
SQLDiag -O Z:\Outputsqldiag.txt -E -C
This was always successful prior to the installation of SP4. There seems to
be nothing about this on the web...
Any thoughts or comments gratefully received.
This is a known bug... I don't think there is anything you can do about it
until it is fixed, but it has been reported...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"BarryC" <BarryC@.discussions.microsoft.com> wrote in message
news:45D5EBF1-0642-46D9-A3A0-696FBC1C2650@.microsoft.com...
>I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on
> running
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems
> to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.
|||SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
around for an immediate solution
Rename the existing SQLDiag.exe (SP4)
Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
the Binn folder
This old version SQLDiag works fine with the SP4. I tested this solution
and it works fine.
"BarryC" wrote:

> I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on running
> SQLDiag - as follows :
> /********************************
> Event ID:26
> User:N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.
|||Thanks for that - in testing at the moment, but its looking good. Have MS
got an official line on this one yet?
"M. S. Reddy" wrote:
[vbcol=seagreen]
> SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
> around for an immediate solution
> Rename the existing SQLDiag.exe (SP4)
> Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
> the Binn folder
> This old version SQLDiag works fine with the SP4. I tested this solution
> and it works fine.
>
>
>
> "BarryC" wrote:

Buffer Overrun reported in SQLDiag

I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
(Active/ Passive), and have started to get Buffer Overrun errors on running
SQLDiag - as follows :
/********************************
Event ID: 26
User: N/A
Description:
Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
detected!
Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
/********************************
SQLDiag is being run by an SQL job running an OS command as follows :
SQLDiag -O Z:\Outputsqldiag.txt -E -C
This was always successful prior to the installation of SP4. There seems to
be nothing about this on the web...
Any thoughts or comments gratefully received.This is a known bug... I don't think there is anything you can do about it
until it is fixed, but it has been reported...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"BarryC" <BarryC@.discussions.microsoft.com> wrote in message
news:45D5EBF1-0642-46D9-A3A0-696FBC1C2650@.microsoft.com...
>I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on
> running
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems
> to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.|||SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
around for an immediate solution
Rename the existing SQLDiag.exe (SP4)
Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
the Binn folder
This old version SQLDiag works fine with the SP4. I tested this solution
and it works fine.
"BarryC" wrote:
> I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on running
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.|||Thanks for that - in testing at the moment, but its looking good. Have MS
got an official line on this one yet?
"M. S. Reddy" wrote:
> SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
> around for an immediate solution
> Rename the existing SQLDiag.exe (SP4)
> Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
> the Binn folder
> This old version SQLDiag works fine with the SP4. I tested this solution
> and it works fine.
>
>
>
> "BarryC" wrote:
> > I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> > (Active/ Passive), and have started to get Buffer Overrun errors on running
> > SQLDiag - as follows :
> >
> > /********************************
> > Event ID: 26
> > User: N/A
> > Description:
> > Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> > detected!
> >
> > Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> >
> > A buffer overrun has been detected which has corrupted the program's
> > internal state. The program cannot safely continue execution and must
> > now be terminated.
> > /********************************
> >
> > SQLDiag is being run by an SQL job running an OS command as follows :
> >
> > SQLDiag -O Z:\Outputsqldiag.txt -E -C
> >
> > This was always successful prior to the installation of SP4. There seems to
> > be nothing about this on the web...
> >
> > Any thoughts or comments gratefully received.

Buffer Overrun reported in SQLDiag

I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
(Active/ Passive), and have started to get Buffer Overrun errors on running
SQLDiag - as follows :
/********************************
Event ID: 26
User: N/A
Description:
Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
detected!
Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
/********************************
SQLDiag is being run by an SQL job running an OS command as follows :
SQLDiag -O Z:\Outputsqldiag.txt -E -C
This was always successful prior to the installation of SP4. There seems to
be nothing about this on the web...
Any thoughts or comments gratefully received.This is a known bug... I don't think there is anything you can do about it
until it is fixed, but it has been reported...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"BarryC" <BarryC@.discussions.microsoft.com> wrote in message
news:45D5EBF1-0642-46D9-A3A0-696FBC1C2650@.microsoft.com...
>I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on
> running
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems
> to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.|||SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
around for an immediate solution
Rename the existing SQLDiag.exe (SP4)
Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
the Binn folder
This old version SQLDiag works fine with the SP4. I tested this solution
and it works fine.
"BarryC" wrote:

> I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on runnin
g
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems
to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.|||Thanks for that - in testing at the moment, but its looking good. Have MS
got an official line on this one yet?
"M. S. Reddy" wrote:
[vbcol=seagreen]
> SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this wo
rk
> around for an immediate solution
> Rename the existing SQLDiag.exe (SP4)
> Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0)
to
> the Binn folder
> This old version SQLDiag works fine with the SP4. I tested this solution
> and it works fine.
>
>
>
> "BarryC" wrote:
>

Buffer overrun detected

When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
Cluster (Active/Active), I receive the next message:
Buffer Overrun detected!
A buffer overrun has been detected which has corrupted the programs internal
state. The program cannot safely continue execution and must now be
terminated.
In a cluster I have two instances. The first instance installed perfect but
in second instance have a problem describe above.
Thank youHi, we've just come across this too. Has anyone got a solution?
BruceB
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1757341.html|||Hi
You may want to call PSS on this one.
John
"Mario Felix Filho" <Mario Felix Filho@.discussions.microsoft.com> wrote in
message news:DA97BB4C-309E-4CDF-A1F2-A2B4851D264F@.microsoft.com...
> When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
> Cluster (Active/Active), I receive the next message:
> Buffer Overrun detected!
> A buffer overrun has been detected which has corrupted the programs
> internal
> state. The program cannot safely continue execution and must now be
> terminated.
> In a cluster I have two instances. The first instance installed perfect
> but
> in second instance have a problem describe above.
> Thank you
>

Buffer overrun detected

When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
Cluster (Active/Active), I receive the next message:
Buffer Overrun detected!
A buffer overrun has been detected which has corrupted the programs internal
state. The program cannot safely continue execution and must now be
terminated.
In a cluster I have two instances. The first instance installed perfect but
in second instance have a problem describe above.
Thank you
Hi, we've just come across this too. Has anyone got a solution?|||Hi
You may want to call PSS on this one.
John
"Mario Felix Filho" <Mario Felix Filho@.discussions.microsoft.com> wrote in
message news:DA97BB4C-309E-4CDF-A1F2-A2B4851D264F@.microsoft.com...
> When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
> Cluster (Active/Active), I receive the next message:
> Buffer Overrun detected!
> A buffer overrun has been detected which has corrupted the programs
> internal
> state. The program cannot safely continue execution and must now be
> terminated.
> In a cluster I have two instances. The first instance installed perfect
> but
> in second instance have a problem describe above.
> Thank you
>

Buffer overrun detected

When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
Cluster (Active/Active), I receive the next message:
Buffer Overrun detected!
A buffer overrun has been detected which has corrupted the programs internal
state. The program cannot safely continue execution and must now be
terminated.
In a cluster I have two instances. The first instance installed perfect but
in second instance have a problem describe above.
Thank youHi
You may want to call PSS on this one.
John
"Mario Felix Filho" <Mario Felix Filho@.discussions.microsoft.com> wrote in
message news:DA97BB4C-309E-4CDF-A1F2-A2B4851D264F@.microsoft.com...
> When I run SQL SP4 in a SQL Server (SQL SP3) running on a Windows 2000
> Cluster (Active/Active), I receive the next message:
> Buffer Overrun detected!
> A buffer overrun has been detected which has corrupted the programs
> internal
> state. The program cannot safely continue execution and must now be
> terminated.
> In a cluster I have two instances. The first instance installed perfect
> but
> in second instance have a problem describe above.
> Thank you
>

Buffer overflow exception in SSIS

I am running a SSIS package which inserts records in 8 tables. After inserting about 280 records I get an error "Buffer overflow". Any help is greatly appreciated.

We'll need more info. What are the sources and destinations? What providers are being used? What transformation objects does the package use? What OS platform are you running on? etc.

Thanks

Donald Farmer

Buffer Manager on SQl server

I am monitoring my SQL Server. If the server has 2gig of
physical ram and SQL server memory is 1.6G and the SQL
Servver Buffer Manager cache hit ratio is 99, is that
good? If not, what configuration can be done? The server
is very slow at themoment. Thank you.
Jasmine>--Original Message--
>I am monitoring my SQL Server. If the server has 2gig of
>physical ram and SQL server memory is 1.6G and the SQL
>Servver Buffer Manager cache hit ratio is 99, is that
>good? If not, what configuration can be done? The
server
>is very slow at the moment. Thank you.
>Jasmine
Friends,
I just thought I should post this from sp_configure so you
can see how the memory is configured for sql server. It
is set to dynamically configure sql server memory - but
when I run performance monitoring it shows that sql server
consumes too much memory. Please take a look and let me
know if I need to reduce the amount of sql memory or some
key buffer and sort buffer configurations? Thank you very
much.
minimum maximum configure_value run_value
max degree of parallelism 0 32 0 0
max server memory (MB) 4 2147483647 2147483647
2147483647
max text repl size (B) 0 2147483647 65536
65536
max worker threads 32 32767 255 255
media retention 0 365 0 0
min memory per query (KB) 512 2147483647
1024 1024
min server memory (MB) 0 2147483647 0 0
>|||Those numbers are pretty good. SQL is using as much memory as is available
(2GB minus some for OS, overhead, etc. 1.6 is about right). 99% Buffer
cache hit ratio is also good. Until that gets under 95% or so, adding
memory likely won't give a noticable performance boost.
It looks like memory isn't your performance problem. Here is a good
starting point for finding out why your server isn't responding as well as
you need it to.
HOW TO: Troubleshoot Application Performance Issues
http://support.microsoft.com/default.aspx?scid=kb;en-us;298475&Product=sql2k
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jasmine Quinlan" <anonymous@.discussions.microsoft.com> wrote in message
news:f64701c43dd2$ff0f0f20$a001280a@.phx.gbl...
> I am monitoring my SQL Server. If the server has 2gig of
> physical ram and SQL server memory is 1.6G and the SQL
> Servver Buffer Manager cache hit ratio is 99, is that
> good? If not, what configuration can be done? The server
> is very slow at themoment. Thank you.
> Jasmine
>|||Geoff,
Thank you so much for your help. I appreciate that.
Jasmine
>--Original Message--
>Those numbers are pretty good. SQL is using as much
memory as is available
>(2GB minus some for OS, overhead, etc. 1.6 is about
right). 99% Buffer
>cache hit ratio is also good. Until that gets under 95%
or so, adding
>memory likely won't give a noticable performance boost.
>It looks like memory isn't your performance problem.
Here is a good
>starting point for finding out why your server isn't
responding as well as
>you need it to.
>HOW TO: Troubleshoot Application Performance Issues
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;298475&Product=sql2k
>
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Jasmine Quinlan" <anonymous@.discussions.microsoft.com>
wrote in message
>news:f64701c43dd2$ff0f0f20$a001280a@.phx.gbl...
>> I am monitoring my SQL Server. If the server has 2gig
of
>> physical ram and SQL server memory is 1.6G and the SQL
>> Servver Buffer Manager cache hit ratio is 99, is that
>> good? If not, what configuration can be done? The
server
>> is very slow at themoment. Thank you.
>> Jasmine
>
>.
>

Buffer Manager on SQl server

I am monitoring my SQL Server. If the server has 2gig of
physical ram and SQL server memory is 1.6G and the SQL
Servver Buffer Manager cache hit ratio is 99, is that
good? If not, what configuration can be done? The server
is very slow at themoment. Thank you.
Jasmine
Those numbers are pretty good. SQL is using as much memory as is available
(2GB minus some for OS, overhead, etc. 1.6 is about right). 99% Buffer
cache hit ratio is also good. Until that gets under 95% or so, adding
memory likely won't give a noticable performance boost.
It looks like memory isn't your performance problem. Here is a good
starting point for finding out why your server isn't responding as well as
you need it to.
HOW TO: Troubleshoot Application Performance Issues
http://support.microsoft.com/default...&Product=sql2k
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jasmine Quinlan" <anonymous@.discussions.microsoft.com> wrote in message
news:f64701c43dd2$ff0f0f20$a001280a@.phx.gbl...
> I am monitoring my SQL Server. If the server has 2gig of
> physical ram and SQL server memory is 1.6G and the SQL
> Servver Buffer Manager cache hit ratio is 99, is that
> good? If not, what configuration can be done? The server
> is very slow at themoment. Thank you.
> Jasmine
>
|||Geoff,
Thank you so much for your help. I appreciate that.
Jasmine

>--Original Message--
>Those numbers are pretty good. SQL is using as much
memory as is available
>(2GB minus some for OS, overhead, etc. 1.6 is about
right). 99% Buffer
>cache hit ratio is also good. Until that gets under 95%
or so, adding
>memory likely won't give a noticable performance boost.
>It looks like memory isn't your performance problem.
Here is a good
>starting point for finding out why your server isn't
responding as well as
>you need it to.
>HOW TO: Troubleshoot Application Performance Issues
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;298475&Product=sql2k
>
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Jasmine Quinlan" <anonymous@.discussions.microsoft.com>
wrote in message[vbcol=seagreen]
>news:f64701c43dd2$ff0f0f20$a001280a@.phx.gbl...
of[vbcol=seagreen]
server
>
>.
>

Buffer Manager on SQl server

I am monitoring my SQL Server. If the server has 2gig of
physical ram and SQL server memory is 1.6G and the SQL
Servver Buffer Manager cache hit ratio is 99, is that
good? If not, what configuration can be done? The server
is very slow at themoment. Thank you.
JasmineThose numbers are pretty good. SQL is using as much memory as is available
(2GB minus some for OS, overhead, etc. 1.6 is about right). 99% Buffer
cache hit ratio is also good. Until that gets under 95% or so, adding
memory likely won't give a noticable performance boost.
It looks like memory isn't your performance problem. Here is a good
starting point for finding out why your server isn't responding as well as
you need it to.
HOW TO: Troubleshoot Application Performance Issues
http://support.microsoft.com/defaul...5&Product=sql2k
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jasmine Quinlan" <anonymous@.discussions.microsoft.com> wrote in message
news:f64701c43dd2$ff0f0f20$a001280a@.phx.gbl...
> I am monitoring my SQL Server. If the server has 2gig of
> physical ram and SQL server memory is 1.6G and the SQL
> Servver Buffer Manager cache hit ratio is 99, is that
> good? If not, what configuration can be done? The server
> is very slow at themoment. Thank you.
> Jasmine
>|||Geoff,
Thank you so much for your help. I appreciate that.
Jasmine

>--Original Message--
>Those numbers are pretty good. SQL is using as much
memory as is available
>(2GB minus some for OS, overhead, etc. 1.6 is about
right). 99% Buffer
>cache hit ratio is also good. Until that gets under 95%
or so, adding
>memory likely won't give a noticable performance boost.
>It looks like memory isn't your performance problem.
Here is a good
>starting point for finding out why your server isn't
responding as well as
>you need it to.
>HOW TO: Troubleshoot Application Performance Issues
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;298475&Product=sql2k
>
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Jasmine Quinlan" <anonymous@.discussions.microsoft.com>
wrote in message
>news:f64701c43dd2$ff0f0f20$a001280a@.phx.gbl...
of[vbcol=seagreen]
server[vbcol=seagreen]
>
>.
>

Buffer manager

Hi,
Could there be anything wrong with Buffer Manager\Page
reads/writes/sec spikes?
Many thanks,
Oskar
Oscar
Not enough memory for SQL Server
"Oskar" <anonymous@.discussions.microsoft.com> wrote in message
news:314c01c4b05c$99325930$a301280a@.phx.gbl...
> Hi,
> Could there be anything wrong with Buffer Manager\Page
> reads/writes/sec spikes?
> --
> Many thanks,
> Oskar
>

Buffer manager

Hi,
Could there be anything wrong with Buffer Manager\Page
reads/writes/sec spikes?
Many thanks,
OskarOscar
Not enough memory for SQL Server
"Oskar" <anonymous@.discussions.microsoft.com> wrote in message
news:314c01c4b05c$99325930$a301280a@.phx.gbl...
> Hi,
> Could there be anything wrong with Buffer Manager\Page
> reads/writes/sec spikes?
> --
> Many thanks,
> Oskar
>

Buffer manager

Hi,
Could there be anything wrong with Buffer Manager\Page
reads/writes/sec spikes?
--
Many thanks,
OskarOscar
Not enough memory for SQL Server
"Oskar" <anonymous@.discussions.microsoft.com> wrote in message
news:314c01c4b05c$99325930$a301280a@.phx.gbl...
> Hi,
> Could there be anything wrong with Buffer Manager\Page
> reads/writes/sec spikes?
> --
> Many thanks,
> Oskar
>