Showing posts with label box. Show all posts
Showing posts with label box. Show all posts

Tuesday, March 27, 2012

Duplicate records are being inserted with one insert command.

This is like the bug from hell. It is kind of hard to explain, so
please bear with me.

Background Info: SQL Server 7.0, on an NT box, Active Server pages
with Javascript, using ADO objects.

I'm inserting simple records into a table. But one insert command is
placing 2 or 3 records into the table. The 'extra' records, have the
same data as the previous insert incident, (except for the timestamp).

Here is an example. Follow the values of the 'Search String' field:

I inserted one record at a time, in the following order (And only one
insert per item):
airplane
jet
dog
cat
mouse
tiger

After this, I should have had 6 records in the table. But, I ended
up with 11!

Here is what was recorded in the database:

Vid DateTime Type ProductName SearchString NumResults
cgcgGeorgeWeb3 Fri Sep 26 09:48:26 PDT 2003 i null airplane 112
cgcgGeorgeWeb3 Fri Sep 26 09:49:37 PDT 2003 i null jet 52
cgcgGeorgeWeb3 Fri Sep 26 09:50:00 PDT 2003 i null dog 49
cgcgGeorgeWeb3 Fri Sep 26 09:50:00 PDT 2003 i null jet 52
cgcgGeorgeWeb3 Fri Sep 26 09:50:00 PDT 2003 i null jet 52
cgcgGeorgeWeb3 Fri Sep 26 09:50:22 PDT 2003 i null dog 49
cgcgGeorgeWeb3 Fri Sep 26 09:50:22 PDT 2003 i null cat 75
cgcgGeorgeWeb3 Fri Sep 26 09:52:53 PDT 2003 i null mouse 64
cgcgGeorgeWeb3 Fri Sep 26 09:53:06 PDT 2003 i null tiger 14
cgcgGeorgeWeb3 Fri Sep 26 09:53:06 PDT 2003 i null mouse 64
cgcgGeorgeWeb3 Fri Sep 26 09:53:06 PDT 2003 i null mouse 64

Look at the timestamps, and notice which ones are the same.

I did one insert for 'dog' , but notice how 2 'jet' records were
inserted
at the same time. Then, when I inserted the 'cat' record, another
'dog' record was inserted. I waited awhile, and inserted mouse, and
only the mouse was inserted. But soon after, I inserted 'tiger', and 2
more mouse records were inserted.

If I wait awhile between inserts, then no extra records are inserted.
( Notice 'airplane', and the first 'mouse' entries. ) But if I insert
records right after one another, then the second record insertion also
inserts a record with data from the 1st insertion.

Here is the complete function, in Javascript (The main code of
interest
may start at the Query = "INSERT ... statement):
----------------------
//Write SearchTrack Record -----------

Search.prototype.writeSearchTrackRec = function(){
Response.Write ("<br>Calling function writeSearchTrack \n"); // for
debug
var Query;
var vid;
var type = "i"; // Type is image
var Q = "', '";
var datetime = "GETDATE()";
//Get the Vid
// First - try to get from the outVid var of Cookieinc
try{
vid = outVid;
}catch(e){
vid = Request.Cookies("CGIVid"); // Gets cookie id value
vid = ""+vid;
if (vid == 'undefined' || vid == ""){
vid = "ImageSearchNoVid";
}
}

try{
Query = "INSERT SearchTrack (Vid, Type, SearchString, DateTime,
NumResults) ";
Query += "VALUES ('"+vid+Q+type+Q+this.searchString+"',
"+datetime+","+this.numResults+ ")";
this.cmd.CommandText = Query;
this.cmd.Execute();
}catch(e){
writeGenericErrLog("Insert SearchTrack failed", "Vid: "+vid+"
- SearchString:: "+this.searchString+" - NumResults: "+this.numResults
, e.description);

}
}//end

--------------------
I also wrote a non-object oriented function, and created the command
object inside the function. But I had the same results.

I know that the function is not getting called multiple times
because I print out a message each time it is called.

This really stumps me. I'll really appreciate any help you can
offer.

Thanks,

George"george" <georgem@.crystalgraphics.com> wrote in message
news:620c2f02.0309261014.20789ca0@.posting.google.c om...
> This is like the bug from hell. It is kind of hard to explain, so
> please bear with me.

<snip
I have no idea what's causing the issue, but the usual advice is to use
Profiler to trace the SQL which is getting sent to the database. You may see
something in the statements which helps you pin down what's going on.
Another thing to check is if there is an INSERT trigger on the table.

Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message news:<3f756b8c_4@.news.bluewin.ch>...
> "george" <georgem@.crystalgraphics.com> wrote in message
> news:620c2f02.0309261014.20789ca0@.posting.google.c om...
> > This is like the bug from hell. It is kind of hard to explain, so
> > please bear with me.
> <snip>
> I have no idea what's causing the issue, but the usual advice is to use
> Profiler to trace the SQL which is getting sent to the database. You may see
> something in the statements which helps you pin down what's going on.
> Another thing to check is if there is an INSERT trigger on the table.
> Simon

Thanks for your help. I found the cause. This is a web page that
contained a form. The form had a button with an onClick event handler
that evolked a script that submitted the form. Well, I added another
form to the page, and wanted the form to be submitted when the user
pushed the 'enter' key, so I focused the new submit button, and put an
onSubmit event handler in the new form. But the onSubmit event handler
evolked the before-mentioned script, so apparently two forms were
being submitted. One form had a hidden form element that contained
the previous 'search string' and the other form had an input box for
the current 'search string'. It explains why 2 db inserts happened
when I submitted the form, but it does not explain why sometimes 3
inserts happened. Anyway, it was kind of difficult to debug, because
it was not evident that 2 forms were being submitted, because, to the
user, the page worked just fine.

Well, perhaps this incident will help someone else down the road who
may run into this situation.

George

Monday, March 26, 2012

Duplicate instances

On one box Enterprise Manager is indicating a second instance â' . (Windows
NT)â' , in addition to the default instance, â' (local) (Windows NT)â'. This
second instance was not installed, It just appeared. The MSSQL directory
indicates the presence of only one instance. Databases, and security
configurations are identical in structure and information between the two
instances. Has any one seen this happen? Would you recommend deleting the
â'Ghostâ' instance. Any ideas welcome. Thanks to everyone for being there to
help. SQL 2000 SP4.coenzyme wrote:
> On one box Enterprise Manager is indicating a second instance â' . (Windows
> NT)â' , in addition to the default instance, â' (local) (Windows NT)â'. This
> second instance was not installed, It just appeared. The MSSQL directory
> indicates the presence of only one instance. Databases, and security
> configurations are identical in structure and information between the two
> instances. Has any one seen this happen? Would you recommend deleting the
> â'Ghostâ' instance. Any ideas welcome. Thanks to everyone for being there to
> help. SQL 2000 SP4.
>
You can safely delete either one - registrations in EM have no effect on
the actual instances that are running.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks Tracy. It's a real comfort to know there's experienced people like you
who are willing to help.
"Tracy McKibben" wrote:
> coenzyme wrote:
> > On one box Enterprise Manager is indicating a second instance â' . (Windows
> > NT)â' , in addition to the default instance, â' (local) (Windows NT)â'. This
> > second instance was not installed, It just appeared. The MSSQL directory
> > indicates the presence of only one instance. Databases, and security
> > configurations are identical in structure and information between the two
> > instances. Has any one seen this happen? Would you recommend deleting the
> > â'Ghostâ' instance. Any ideas welcome. Thanks to everyone for being there to
> > help. SQL 2000 SP4.
> >
> >
> You can safely delete either one - registrations in EM have no effect on
> the actual instances that are running.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Duplicate instances

On one box Enterprise Manager is indicating a second instance “ . (Window
s
NT)” , in addition to the default instance, “ (local) (Windows NT)”.
This
second instance was not installed, It just appeared. The MSSQL directory
indicates the presence of only one instance. Databases, and security
configurations are identical in structure and information between the two
instances. Has any one seen this happen? Would you recommend deleting the
“Ghost” instance. Any ideas welcome. Thanks to everyone for being there
to
help. SQL 2000 SP4.coenzyme wrote:
> On one box Enterprise Manager is indicating a second instance “ . (Wind
ows
> NT)” , in addition to the default instance, “ (local) (Windows NT)”
. This
> second instance was not installed, It just appeared. The MSSQL directory
> indicates the presence of only one instance. Databases, and security
> configurations are identical in structure and information between the two
> instances. Has any one seen this happen? Would you recommend deleting the
> “Ghost” instance. Any ideas welcome. Thanks to everyone for being ther
e to
> help. SQL 2000 SP4.
>
You can safely delete either one - registrations in EM have no effect on
the actual instances that are running.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Thanks Tracy. It's a real comfort to know there's experienced people like yo
u
who are willing to help.
"Tracy McKibben" wrote:

> coenzyme wrote:
> You can safely delete either one - registrations in EM have no effect on
> the actual instances that are running.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Monday, March 19, 2012

Dump files in SQL 7.0 Enterprise

Hello,
I have been experiencing crash dump files on our SQL 7 Enterprise box several times per day for the last few months. I can't seem to match them up to a particular task or job.
Any ideas appreciated. Thank you.
Here is the head of one of the .dmp files:
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server 1792.842
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Current local time is Wed Jul 21 12:13:00 2004
2 Intel x86 level 6, 797 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
TotalPageFile = 3941 MB
Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
Symbol load failed - Proceed to dump without any symbols
Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 07/21/04 12:13:00 spid 29
*
* Input Buffer 42 bytes -
* s p _ r e s e t _ c o n n e c t i o n
*
************************************************** *****************************
Parsing dump files is not something everybody can do and you only provided a
fraction of it. If your crashing that often you should contact MS PSS and
let them work directly with you to fix the issue. They can certainly access
the dump files properly.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"ddrewrey" <ddrewrey@.discussions.microsoft.com> wrote in message
news:A939C3EC-D341-4835-B4EC-E9FB7AF26638@.microsoft.com...
> Hello,
> I have been experiencing crash dump files on our SQL 7 Enterprise box
several times per day for the last few months. I can't seem to match them up
to a particular task or job.
> Any ideas appreciated. Thank you.
> Here is the head of one of the .dmp files:
> ================================================== ===================
> BugCheck Dump
> ================================================== ===================
> This file is generated by Microsoft SQL Server 1792.842
> upon detection of fatal unexpected error. Please return this file,
> the query or program that produced the bugcheck, the database and
> the error log, and any other pertinent information with a Service Request.
> Computer type is AT/AT COMPATIBLE.
> Current local time is Wed Jul 21 12:13:00 2004
> 2 Intel x86 level 6, 797 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> --
> MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
> TotalPageFile = 3941 MB
> Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
> Symbol load failed - Proceed to dump without any symbols
> Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
>
************************************************** **************************
***
> *
> * BEGIN STACK DUMP:
> * 07/21/04 12:13:00 spid 29
> *
> * Input Buffer 42 bytes -
> * s p _ r e s e t _ c o n n e c t i o n
> *
>
************************************************** **************************
***

Dump files in SQL 7.0 Enterprise

Hello,
I have been experiencing crash dump files on our SQL 7 Enterprise box several times per day for the last few months. I can't seem to match them up to a particular task or job.
Any ideas appreciated. Thank you.
Here is the head of one of the .dmp files:
===================================================================== BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server 1792.842
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Current local time is Wed Jul 21 12:13:00 2004
2 Intel x86 level 6, 797 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
--
MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
TotalPageFile = 3941 MB
Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
Symbol load failed - Proceed to dump without any symbols
Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
*******************************************************************************
*
* BEGIN STACK DUMP:
* 07/21/04 12:13:00 spid 29
*
* Input Buffer 42 bytes -
* s p _ r e s e t _ c o n n e c t i o n
*
*******************************************************************************Parsing dump files is not something everybody can do and you only provided a
fraction of it. If your crashing that often you should contact MS PSS and
let them work directly with you to fix the issue. They can certainly access
the dump files properly.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly SQL MVP
"ddrewrey" <ddrewrey@.discussions.microsoft.com> wrote in message
news:A939C3EC-D341-4835-B4EC-E9FB7AF26638@.microsoft.com...
> Hello,
> I have been experiencing crash dump files on our SQL 7 Enterprise box
several times per day for the last few months. I can't seem to match them up
to a particular task or job.
> Any ideas appreciated. Thank you.
> Here is the head of one of the .dmp files:
> =====================================================================> BugCheck Dump
> =====================================================================> This file is generated by Microsoft SQL Server 1792.842
> upon detection of fatal unexpected error. Please return this file,
> the query or program that produced the bugcheck, the database and
> the error log, and any other pertinent information with a Service Request.
> Computer type is AT/AT COMPATIBLE.
> Current local time is Wed Jul 21 12:13:00 2004
> 2 Intel x86 level 6, 797 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> --
> MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
> TotalPageFile = 3941 MB
> Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
> Symbol load failed - Proceed to dump without any symbols
> Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
>
****************************************************************************
***
> *
> * BEGIN STACK DUMP:
> * 07/21/04 12:13:00 spid 29
> *
> * Input Buffer 42 bytes -
> * s p _ r e s e t _ c o n n e c t i o n
> *
>
****************************************************************************
***

Dump files in SQL 7.0 Enterprise

Hello,
I have been experiencing crash dump files on our SQL 7 Enterprise box severa
l times per day for the last few months. I can't seem to match them up to a
particular task or job.
Any ideas appreciated. Thank you.
Here is the head of one of the .dmp files:
========================================
=============================
BugCheck Dump
========================================
=============================
This file is generated by Microsoft SQL Server 1792.842
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Current local time is Wed Jul 21 12:13:00 2004
2 Intel x86 level 6, 797 Mhz processor(s).
Windows NT 5.0 Build 2195 CSD Service Pack 4.
Memory
--
MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
TotalPageFile = 3941 MB
Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
Symbol load failed - Proceed to dump without any symbols
Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
****************************************
************************************
***
*
* BEGIN STACK DUMP:
* 07/21/04 12:13:00 spid 29
*
* Input Buffer 42 bytes -
* s p _ r e s e t _ c o n n e c t i o n
*
****************************************
************************************
***Parsing dump files is not something everybody can do and you only provided a
fraction of it. If your crashing that often you should contact MS PSS and
let them work directly with you to fix the issue. They can certainly access
the dump files properly.
http://support.microsoft.com/defaul...id=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"ddrewrey" <ddrewrey@.discussions.microsoft.com> wrote in message
news:A939C3EC-D341-4835-B4EC-E9FB7AF26638@.microsoft.com...
> Hello,
> I have been experiencing crash dump files on our SQL 7 Enterprise box
several times per day for the last few months. I can't seem to match them up
to a particular task or job.
> Any ideas appreciated. Thank you.
> Here is the head of one of the .dmp files:
> ========================================
=============================
> BugCheck Dump
> ========================================
=============================
> This file is generated by Microsoft SQL Server 1792.842
> upon detection of fatal unexpected error. Please return this file,
> the query or program that produced the bugcheck, the database and
> the error log, and any other pertinent information with a Service Request.
> Computer type is AT/AT COMPATIBLE.
> Current local time is Wed Jul 21 12:13:00 2004
> 2 Intel x86 level 6, 797 Mhz processor(s).
> Windows NT 5.0 Build 2195 CSD Service Pack 4.
>
> Memory
> --
> MemoryLoad = 97% TotalPhys = 2047 MB AvailPhys = 47 MB
> TotalPageFile = 3941 MB
> Dump thread - spid = 29, PSS = 0x35799138, EC = 0x357992e8
> Symbol load failed - Proceed to dump without any symbols
> Stack Dump being sent to C:\MSSQL7\log\SQL08175.dmp
>
****************************************
************************************
***
> *
> * BEGIN STACK DUMP:
> * 07/21/04 12:13:00 spid 29
> *
> * Input Buffer 42 bytes -
> * s p _ r e s e t _ c o n n e c t i o n
> *
>
****************************************
************************************
***

Dump file

Hi Everyone,
We have a SQL Server creates a dump file & stops the
service. Any help is highly appeciated.
SQL 2000 (SP3A) on a Windows 2000 Box (SP4)
Thanks,
================================================== =========
==========
BugCheck
Dump
================================================== =========
==========
This file is generated by Microsoft SQL Server
8.00.760
upon detection of fatal unexpected error. Please return
this file,
the query or program that produced the bugcheck, the
database and
the error log, and any other pertinent information with a
Service Request.
Computer type is AT/AT
COMPATIBLE.
Bios Version is PhoenixBIOS 4.0 Release
6.0
Current time is 13:27:01
06/18/04.
4 Intel x86 level 15, 3066 Mhz processor
(s).
Windows NT 5.0 Build 2195 CSD Service Pack
4.
Memory
MemoryLoad = 77%
Total Physical = 2046 MB
Available Physical = 465 MB
Total Page File = 3940 MB
Available Page File = 2463 MB
Total Virtual = 2047 MB
Available Virtual = 288 MB
*Dump thread - spid = 68, PSS = 0x52f031c8, EC =
0x52f034f0
*Stack Dump being sent to d:\Microsoft SQL
Server\MSSQL\log\SQLDump0001.txt
*
************************************************** *********
******************
**
*
* BEGIN STACK
DUMP:
* 06/18/04 13:27:01 spid
68
*
*
*
* Input Buffer 224 bytes -
* CREATE UNIQUE CLUSTERED INDEX [PK_promo] ON [dbo].
[promo] ([promo_id]
* ) WITH DROP_EXISTING ON
[PRIMARY]
*
*
* MODULE BASE END
SIZE
* sqlservr 00400000 00B2CFFF
0072d000
* ntdll 77F80000 77FFAFFF
0007b000
* KERNEL32 7C570000 7C622FFF
000b3000
* ADVAPI32 7C2D0000 7C331FFF
00062000
* RPCRT4 77D30000 77D9DFFF
0006e000
* USER32 77E10000 77E6EFFF
0005f000
* GDI32 77F40000 77F78FFF
00039000
* OPENDS60 41060000 41065FFF
00006000
* MSVCRT 78000000 78044FFF
00045000
* UMS 41070000 4107CFFF
0000d000
* SQLSORT 42AE0000 42B6FFFF
00090000
* MSVCIRT 780A0000 780B1FFF
00012000
* sqlevn70 41080000 41086FFF
00007000
* NETAPI32 027A0000 027EEFFF
0004f000
* SECUR32 027F0000 027FEFFF
0000f000
* NETRAP 02800000 02805FFF
00006000
* SAMLIB 02810000 0281EFFF
0000f000
* WS2_32 02820000 02833FFF
00014000
* WS2HELP 02840000 02847FFF
00008000
* WLDAP32 02850000 02879FFF
0002a000
* DNSAPI 02880000 028A3FFF
00024000
* WSOCK32 028B0000 028B7FFF
00008000
* ole32 02CA0000 02D8BFFF
000ec000
* XOLEHLP 02E10000 02E17FFF
00008000
* MSDTCPRX 02E20000 02ED3FFF
000b4000
* MTXCLU 02EE0000 02EEFFFF
00010000
* VERSION 02EF0000 02EF6FFF
00007000
* LZ32 02F00000 02F05FFF
00006000
* CLUSAPI 02F10000 02F1FFFF
00010000
* RESUTILS 02F20000 02F2CFFF
0000d000
* USERENV 02F30000 02F90FFF
00061000
* rnr20 02FA0000 02FABFFF
0000c000
* iphlpapi 02FF0000 03002FFF
00013000
* ICMP 03010000 03014FFF
00005000
* MPRAPI 03020000 03036FFF
00017000
* OLEAUT32 03040000 030DAFFF
0009b000
* ACTIVEDS 030E0000 0310EFFF
0002f000
* ADSLDPC 03110000 03132FFF
00023000
* RTUTILS 03140000 0314DFFF
0000e000
* SETUPAPI 03150000 031DDFFF
0008e000
* RASAPI32 031E0000 03212FFF
00033000
* RASMAN 03220000 03230FFF
00011000
* TAPI32 03240000 03261FFF
00022000
* COMCTL32 03270000 032F3FFF
00084000
* SHLWAPI 03300000 03364FFF
00065000
* DHCPCSVC 03370000 03388FFF
00019000
* winrnr 03830000 03837FFF
00008000
* rasadhlp 03840000 03844FFF
00005000
* SSNMPN70 03F40000 03F45FFF
00006000
* SSNETLIB 03F50000 03F64FFF
00015000
* security 042A0000 042A3FFF
00004000
* msafd 04B90000 04BADFFF
0001e000
* wshtcpip 04C00000 04C06FFF
00007000
* SSmsLPCn 04CA0000 04CA6FFF
00007000
* ntdsapi 04D80000 04D90FFF
00011000
* SQLFTQRY 063E0000 06411FFF
00032000
* CLBCATQ 06420000 064A5FFF
00086000
* sqloledb 064C0000 06532FFF
00073000
* MSDART 06540000 0655EFFF
0001f000
* comdlg32 06560000 0659DFFF
0003e000
* SHELL32 06630000 06877FFF
00248000
* MSDATL3 06880000 06894FFF
00015000
* oledb32 06D30000 06D95FFF
00066000
* OLEDB32R 06DA0000 06DAFFFF
00010000
* msv1_0 06DB0000 06DCEFFF
0001f000
* CRYPT32 06DD0000 06E47FFF
00078000
* MSASN1 06E50000 06E5FFFF
00010000
* xpsqlbot 06E60000 06E65FFF
00006000
* rsabase 07010000 07032FFF
00023000
* xpstar 08830000 08876FFF
00047000
* SQLRESLD 08880000 08886FFF
00007000
* SQLSVC 08890000 088A6FFF
00017000
* ODBC32 088B0000 088E1FFF
00032000
* odbcbcp 088F0000 088F5FFF
00006000
* W95SCM 08900000 0890BFFF
0000c000
* SQLUNIRL 10000000 1002CFFF
0002d000
* WINSPOOL 08910000 0892DFFF
0001e000
* MPR 08930000 08940FFF
00011000
* SHFOLDER 08950000 08957FFF
00008000
* odbcint 08B20000 08B35FFF
00016000
* NDDEAPI 08B40000 08B46FFF
00007000
* SQLSVC 08B50000 08B55FFF
00006000
* xpstar 08B60000 08B68FFF
00009000
* mswsock 08EF0000 08F01FFF
00012000
* xplog70 09960000 09971FFF
00012000
* xplog70 09980000 09983FFF
00004000
* dbghelp 06E90000 06F44FFF
000b5000
*
ec_buftrace.Entry [62]
bpage = 0x1A010000 bhash = 0x00000000
bpageno = (1:744605)
bdbid = 59 breferences = 8336 bstat
= 0xb
bspin = 0 bnext = 0x00000000
ec_buftrace.Entry [63]
bpage = 0x42F52000 bhash = 0x00000000
bpageno = (1:849240)
bdbid = 59 breferences = 1406 bstat
= 0xb
bspin = 0 bnext = 0x00000000
EXCEPT (null) @.0x0DCEC148
exc_number = 0 exc_severity =
0
exc_func = MSQLErrorHandler+0 Line 0+0x0
Under what circumstances do you see this? Also could you please paste the
"short stack dump" that is present in the error logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Dump file

Hi Everyone,
We have a SQL Server creates a dump file & stops the
service. Any help is highly appeciated.
SQL 2000 (SP3A) on a Windows 2000 Box (SP4)
Thanks,
=========================================================== ========== BugCheck
Dump
=========================================================== ==========
This file is generated by Microsoft SQL Server
8.00.760
upon detection of fatal unexpected error. Please return
this file,
the query or program that produced the bugcheck, the
database and
the error log, and any other pertinent information with a
Service Request.
Computer type is AT/AT
COMPATIBLE.
Bios Version is PhoenixBIOS 4.0 Release
6.0
Current time is 13:27:01
06/18/04.
4 Intel x86 level 15, 3066 Mhz processor
(s).
Windows NT 5.0 Build 2195 CSD Service Pack
4.
Memory
MemoryLoad = 77%
Total Physical = 2046 MB
Available Physical = 465 MB
Total Page File = 3940 MB
Available Page File = 2463 MB
Total Virtual = 2047 MB
Available Virtual = 288 MB
*Dump thread - spid = 68, PSS = 0x52f031c8, EC = 0x52f034f0
*Stack Dump being sent to d:\Microsoft SQL
Server\MSSQL\log\SQLDump0001.txt
*
***********************************************************
******************
**
*
* BEGIN STACK
DUMP:
* 06/18/04 13:27:01 spid
68
*
*
*
* Input Buffer 224 bytes -
* CREATE UNIQUE CLUSTERED INDEX [PK_promo] ON [dbo].
[promo] ([promo_id]
* ) WITH DROP_EXISTING ON
[PRIMARY]
*
*
* MODULE BASE END
SIZE
* sqlservr 00400000 00B2CFFF
0072d000
* ntdll 77F80000 77FFAFFF
0007b000
* KERNEL32 7C570000 7C622FFF
000b3000
* ADVAPI32 7C2D0000 7C331FFF
00062000
* RPCRT4 77D30000 77D9DFFF
0006e000
* USER32 77E10000 77E6EFFF
0005f000
* GDI32 77F40000 77F78FFF
00039000
* OPENDS60 41060000 41065FFF
00006000
* MSVCRT 78000000 78044FFF
00045000
* UMS 41070000 4107CFFF
0000d000
* SQLSORT 42AE0000 42B6FFFF
00090000
* MSVCIRT 780A0000 780B1FFF
00012000
* sqlevn70 41080000 41086FFF
00007000
* NETAPI32 027A0000 027EEFFF
0004f000
* SECUR32 027F0000 027FEFFF
0000f000
* NETRAP 02800000 02805FFF
00006000
* SAMLIB 02810000 0281EFFF
0000f000
* WS2_32 02820000 02833FFF
00014000
* WS2HELP 02840000 02847FFF
00008000
* WLDAP32 02850000 02879FFF
0002a000
* DNSAPI 02880000 028A3FFF
00024000
* WSOCK32 028B0000 028B7FFF
00008000
* ole32 02CA0000 02D8BFFF
000ec000
* XOLEHLP 02E10000 02E17FFF
00008000
* MSDTCPRX 02E20000 02ED3FFF
000b4000
* MTXCLU 02EE0000 02EEFFFF
00010000
* VERSION 02EF0000 02EF6FFF
00007000
* LZ32 02F00000 02F05FFF
00006000
* CLUSAPI 02F10000 02F1FFFF
00010000
* RESUTILS 02F20000 02F2CFFF
0000d000
* USERENV 02F30000 02F90FFF
00061000
* rnr20 02FA0000 02FABFFF
0000c000
* iphlpapi 02FF0000 03002FFF
00013000
* ICMP 03010000 03014FFF
00005000
* MPRAPI 03020000 03036FFF
00017000
* OLEAUT32 03040000 030DAFFF
0009b000
* ACTIVEDS 030E0000 0310EFFF
0002f000
* ADSLDPC 03110000 03132FFF
00023000
* RTUTILS 03140000 0314DFFF
0000e000
* SETUPAPI 03150000 031DDFFF
0008e000
* RASAPI32 031E0000 03212FFF
00033000
* RASMAN 03220000 03230FFF
00011000
* TAPI32 03240000 03261FFF
00022000
* COMCTL32 03270000 032F3FFF
00084000
* SHLWAPI 03300000 03364FFF
00065000
* DHCPCSVC 03370000 03388FFF
00019000
* winrnr 03830000 03837FFF
00008000
* rasadhlp 03840000 03844FFF
00005000
* SSNMPN70 03F40000 03F45FFF
00006000
* SSNETLIB 03F50000 03F64FFF
00015000
* security 042A0000 042A3FFF
00004000
* msafd 04B90000 04BADFFF
0001e000
* wshtcpip 04C00000 04C06FFF
00007000
* SSmsLPCn 04CA0000 04CA6FFF
00007000
* ntdsapi 04D80000 04D90FFF
00011000
* SQLFTQRY 063E0000 06411FFF
00032000
* CLBCATQ 06420000 064A5FFF
00086000
* sqloledb 064C0000 06532FFF
00073000
* MSDART 06540000 0655EFFF
0001f000
* comdlg32 06560000 0659DFFF
0003e000
* SHELL32 06630000 06877FFF
00248000
* MSDATL3 06880000 06894FFF
00015000
* oledb32 06D30000 06D95FFF
00066000
* OLEDB32R 06DA0000 06DAFFFF
00010000
* msv1_0 06DB0000 06DCEFFF
0001f000
* CRYPT32 06DD0000 06E47FFF
00078000
* MSASN1 06E50000 06E5FFFF
00010000
* xpsqlbot 06E60000 06E65FFF
00006000
* rsabase 07010000 07032FFF
00023000
* xpstar 08830000 08876FFF
00047000
* SQLRESLD 08880000 08886FFF
00007000
* SQLSVC 08890000 088A6FFF
00017000
* ODBC32 088B0000 088E1FFF
00032000
* odbcbcp 088F0000 088F5FFF
00006000
* W95SCM 08900000 0890BFFF
0000c000
* SQLUNIRL 10000000 1002CFFF
0002d000
* WINSPOOL 08910000 0892DFFF
0001e000
* MPR 08930000 08940FFF
00011000
* SHFOLDER 08950000 08957FFF
00008000
* odbcint 08B20000 08B35FFF
00016000
* NDDEAPI 08B40000 08B46FFF
00007000
* SQLSVC 08B50000 08B55FFF
00006000
* xpstar 08B60000 08B68FFF
00009000
* mswsock 08EF0000 08F01FFF
00012000
* xplog70 09960000 09971FFF
00012000
* xplog70 09980000 09983FFF
00004000
* dbghelp 06E90000 06F44FFF
000b5000
*
ec_buftrace.Entry [62]
--
bpage = 0x1A010000 bhash = 0x00000000
bpageno = (1:744605)
bdbid = 59 breferences = 8336 bstat
= 0xb
bspin = 0 bnext = 0x00000000
ec_buftrace.Entry [63]
--
bpage = 0x42F52000 bhash = 0x00000000
bpageno = (1:849240)
bdbid = 59 breferences = 1406 bstat
= 0xb
bspin = 0 bnext = 0x00000000
EXCEPT (null) @.0x0DCEC148
--
exc_number = 0 exc_severity = 0
exc_func = MSQLErrorHandler+0 Line 0+0x0Under what circumstances do you see this? Also could you please paste the
"short stack dump" that is present in the error logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Dump file

Hi Everyone,
We have a SQL Server creates a dump file & stops the
service. Any help is highly appeciated.
SQL 2000 (SP3A) on a Windows 2000 Box (SP4)
Thanks,
========================================
===================
==========
BugCheck
Dump
========================================
===================
==========
This file is generated by Microsoft SQL Server
8.00.760
upon detection of fatal unexpected error. Please return
this file,
the query or program that produced the bugcheck, the
database and
the error log, and any other pertinent information with a
Service Request.
Computer type is AT/AT
COMPATIBLE.
Bios Version is PhoenixBIOS 4.0 Release
6.0
Current time is 13:27:01
06/18/04.
4 Intel x86 level 15, 3066 Mhz processor
(s).
Windows NT 5.0 Build 2195 CSD Service Pack
4.
Memory
MemoryLoad = 77%
Total Physical = 2046 MB
Available Physical = 465 MB
Total Page File = 3940 MB
Available Page File = 2463 MB
Total Virtual = 2047 MB
Available Virtual = 288 MB
*Dump thread - spid = 68, PSS = 0x52f031c8, EC =
0x52f034f0
*Stack Dump being sent to d:\Microsoft SQL
Server\MSSQL\log\SQLDump0001.txt
*
****************************************
*******************
******************
**
*
* BEGIN STACK
DUMP:
* 06/18/04 13:27:01 spid
68
*
*
*
* Input Buffer 224 bytes -
* CREATE UNIQUE CLUSTERED INDEX [PK_promo] ON [dbo].
[promo] ([promo_id]
* ) WITH DROP_EXISTING ON
[PRIMARY]
*
*
* MODULE BASE END
SIZE
* sqlservr 00400000 00B2CFFF
0072d000
* ntdll 77F80000 77FFAFFF
0007b000
* KERNEL32 7C570000 7C622FFF
000b3000
* ADVAPI32 7C2D0000 7C331FFF
00062000
* RPCRT4 77D30000 77D9DFFF
0006e000
* USER32 77E10000 77E6EFFF
0005f000
* GDI32 77F40000 77F78FFF
00039000
* OPENDS60 41060000 41065FFF
00006000
* MSVCRT 78000000 78044FFF
00045000
* UMS 41070000 4107CFFF
0000d000
* SQLSORT 42AE0000 42B6FFFF
00090000
* MSVCIRT 780A0000 780B1FFF
00012000
* sqlevn70 41080000 41086FFF
00007000
* NETAPI32 027A0000 027EEFFF
0004f000
* SECUR32 027F0000 027FEFFF
0000f000
* NETRAP 02800000 02805FFF
00006000
* SAMLIB 02810000 0281EFFF
0000f000
* WS2_32 02820000 02833FFF
00014000
* WS2HELP 02840000 02847FFF
00008000
* WLDAP32 02850000 02879FFF
0002a000
* DNSAPI 02880000 028A3FFF
00024000
* WSOCK32 028B0000 028B7FFF
00008000
* ole32 02CA0000 02D8BFFF
000ec000
* XOLEHLP 02E10000 02E17FFF
00008000
* MSDTCPRX 02E20000 02ED3FFF
000b4000
* MTXCLU 02EE0000 02EEFFFF
00010000
* VERSION 02EF0000 02EF6FFF
00007000
* LZ32 02F00000 02F05FFF
00006000
* CLUSAPI 02F10000 02F1FFFF
00010000
* RESUTILS 02F20000 02F2CFFF
0000d000
* USERENV 02F30000 02F90FFF
00061000
* rnr20 02FA0000 02FABFFF
0000c000
* iphlpapi 02FF0000 03002FFF
00013000
* ICMP 03010000 03014FFF
00005000
* MPRAPI 03020000 03036FFF
00017000
* OLEAUT32 03040000 030DAFFF
0009b000
* ACTIVEDS 030E0000 0310EFFF
0002f000
* ADSLDPC 03110000 03132FFF
00023000
* RTUTILS 03140000 0314DFFF
0000e000
* SETUPAPI 03150000 031DDFFF
0008e000
* RASAPI32 031E0000 03212FFF
00033000
* RASMAN 03220000 03230FFF
00011000
* TAPI32 03240000 03261FFF
00022000
* COMCTL32 03270000 032F3FFF
00084000
* SHLWAPI 03300000 03364FFF
00065000
* DHCPCSVC 03370000 03388FFF
00019000
* winrnr 03830000 03837FFF
00008000
* rasadhlp 03840000 03844FFF
00005000
* SSNMPN70 03F40000 03F45FFF
00006000
* SSNETLIB 03F50000 03F64FFF
00015000
* security 042A0000 042A3FFF
00004000
* msafd 04B90000 04BADFFF
0001e000
* wshtcpip 04C00000 04C06FFF
00007000
* SSmsLPCn 04CA0000 04CA6FFF
00007000
* ntdsapi 04D80000 04D90FFF
00011000
* SQLFTQRY 063E0000 06411FFF
00032000
* CLBCATQ 06420000 064A5FFF
00086000
* sqloledb 064C0000 06532FFF
00073000
* MSDART 06540000 0655EFFF
0001f000
* comdlg32 06560000 0659DFFF
0003e000
* SHELL32 06630000 06877FFF
00248000
* MSDATL3 06880000 06894FFF
00015000
* oledb32 06D30000 06D95FFF
00066000
* OLEDB32R 06DA0000 06DAFFFF
00010000
* msv1_0 06DB0000 06DCEFFF
0001f000
* CRYPT32 06DD0000 06E47FFF
00078000
* MSASN1 06E50000 06E5FFFF
00010000
* xpsqlbot 06E60000 06E65FFF
00006000
* rsabase 07010000 07032FFF
00023000
* xpstar 08830000 08876FFF
00047000
* SQLRESLD 08880000 08886FFF
00007000
* SQLSVC 08890000 088A6FFF
00017000
* ODBC32 088B0000 088E1FFF
00032000
* odbcbcp 088F0000 088F5FFF
00006000
* W95SCM 08900000 0890BFFF
0000c000
* SQLUNIRL 10000000 1002CFFF
0002d000
* WINSPOOL 08910000 0892DFFF
0001e000
* MPR 08930000 08940FFF
00011000
* SHFOLDER 08950000 08957FFF
00008000
* odbcint 08B20000 08B35FFF
00016000
* NDDEAPI 08B40000 08B46FFF
00007000
* SQLSVC 08B50000 08B55FFF
00006000
* xpstar 08B60000 08B68FFF
00009000
* mswsock 08EF0000 08F01FFF
00012000
* xplog70 09960000 09971FFF
00012000
* xplog70 09980000 09983FFF
00004000
* dbghelp 06E90000 06F44FFF
000b5000
*
ec_buftrace.Entry [62]
--
bpage = 0x1A010000 bhash = 0x00000000
bpageno = (1:744605)
bdbid = 59 breferences = 8336 bstat
= 0xb
bspin = 0 bnext = 0x00000000
ec_buftrace.Entry [63]
--
bpage = 0x42F52000 bhash = 0x00000000
bpageno = (1:849240)
bdbid = 59 breferences = 1406 bstat
= 0xb
bspin = 0 bnext = 0x00000000
EXCEPT (null) @.0x0DCEC148
--
exc_number = 0 exc_severity =
0
exc_func = MSQLErrorHandler+0 Line 0+0x0Under what circumstances do you see this? Also could you please paste the
"short stack dump" that is present in the error logs.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Sunday, March 11, 2012

Dual Xeon or Dual P4 for SQL Server?

I am planning to build a server to be used as a SQL Server and web server.
Right now I can only use a single box for both.

I have read some threads were dual processors are having problems with some
parallel queries and the suggestions of having sql server use a single CPU.

My budget is limited so I am debating whether to get 2.6G dual xeon 533FSB
or dual P4 800FSB (DRR@. ram) or stick with a speedy single cpu.
If I get a dual cpu motherboard, is it a good idea to have 1 cpu used for
sql server and the other for everything else?

John DalbergOn Sun, 21 Nov 2004 07:14:17 -0800, John Dalberg wrote:

> I am planning to build a server to be used as a SQL Server and web server.
> Right now I can only use a single box for both.
> I have read some threads were dual processors are having problems with some
> parallel queries and the suggestions of having sql server use a single CPU.
> My budget is limited so I am debating whether to get 2.6G dual xeon 533FSB
> or dual P4 800FSB (DRR@. ram) or stick with a speedy single cpu.
> If I get a dual cpu motherboard, is it a good idea to have 1 cpu used for
> sql server and the other for everything else?
> John Dalberg

I forgot to mention also what about AMD's Athlon since I can get faster
Athlons for the same amount of money for Intel CPUs? Are dual Athlon
motherboards a good choice for SQL Server?

John Dalberg|||In article <u1ekecr53aij.1ek79hzro64q4$.dlg@.40tude.net>,
john_dd@.hotmail.com says...
> I am planning to build a server to be used as a SQL Server and web server.
> Right now I can only use a single box for both.
> I have read some threads were dual processors are having problems with some
> parallel queries and the suggestions of having sql server use a single CPU.
> My budget is limited so I am debating whether to get 2.6G dual xeon 533FSB
> or dual P4 800FSB (DRR@. ram) or stick with a speedy single cpu.
> If I get a dual cpu motherboard, is it a good idea to have 1 cpu used for
> sql server and the other for everything else?

John, you can't use Dual P4's any more, Intel fixed that after the P3.

If you want to build a cheap but fast SQL Server, assuming SQL 2000 or
higher, tape a look at the ASUS PC-DL Deluxe motherboard. I have about
30 of these running the following:

ASUS PC-DL Deluxe
Dua Xeon 2.4G (or faster) (make sure they are same lot/part)
2GB or 4GB of RAM (does not require ECC RAM)
It has onboard SATA and IDE, you can use a total of 6 drives between the
connectors without a problem.

The 2GB systems with Dual 250GB SATA drives, video, case, CD-ROM, etc...
are under $1900 each.

If you want a big box, like this:

PC-DL Deluxe
Dual Xeon 2.8ghz
2 x 80GB IDE (OS = 12GB, LOGS = 60GB)
6 x 250GB IDE (for DATA files)
Promise SX6000 Hardware IDE RAID Controller (hot swap IDE drives)
cheap video
Chenbro Server case with Dual 550W PSU's
and Windows 2003 Standard Server 5cal

This box runs about $4000

I run SQL 2000 on Dual P3 and Dual/Quad Xeon without any problems.

If you get a P4, get one that does Hyper-Threading, and use Server 2003
so that you get the most benefit from it.

As for Athlon, faster is a matter of what task is being performed and
how stable you want the system to be. When it comes to business systems
I use Intel CPU's only, but that's a personal preference and has never
cost me a job or stability.

--
--
spamfree999@.rrohio.com
(Remove 999 to reply to me)|||John Dalberg (john_dd@.hotmail.com) writes:
> I am planning to build a server to be used as a SQL Server and web server.
> Right now I can only use a single box for both.
> I have read some threads were dual processors are having problems with
> some parallel queries and the suggestions of having sql server use a
> single CPU.
> My budget is limited so I am debating whether to get 2.6G dual xeon 533FSB
> or dual P4 800FSB (DRR@. ram) or stick with a speedy single cpu.
> If I get a dual cpu motherboard, is it a good idea to have 1 cpu used for
> sql server and the other for everything else?

Machine configurations is not my best game, but if you are going to have
both SQL Server and web server on the same box, I would definitely go for
two CPUs. (Or at least one CPU that is hyper-threaded.)

As for SQL Server and parallel queries, yes, there is a potential problem.
I have seen more than once, SQL Server being too optimistic about parallel
query plans, and taken a plan with poor performance. What we usually do,
when we run into these queries is to add the query hint OPTION (MAXDOP 1)
which turns of parallellism for that query.

A more definitive cure is to set the configuration option "Max degress of
parllellism" to 1. Note that this is not the same as confining SQL Server
to one CPU only, but that one single query can only take one processor. Two
users executing different queries can still get one CPU each.

Giving SQL Server only one CPU *may* be a good idea, if you expect the
web server and the rest to need substantial amount of resources. But you
could also get the effect that one processor is mainly idle, while the
other is working around the clock.

So my recommendation would be set "Max degrees of Parallelism" to 1 (Or
to 2, if you have two hyper-threaded CPUs), but let SQL Server use both
CPUs.

Finally, there may be a licensing issue. I vaguely recall that for some
editions that you pay a license per processor, but please check this with
Microsoft. Licensing is definitely not my best game.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||In article <Xns95A8BE037B8EAYazorman@.127.0.0.1>, esquel@.sommarskog.se
says...
> Finally, there may be a licensing issue. I vaguely recall that for some
> editions that you pay a license per processor, but please check this with
> Microsoft. Licensing is definitely not my best game.

I was told by the MS People in the Great Lakes MS Office that HT CPU's
still count as 1 CPU for licensing.

One other thing, unless he's using SBS, I was also told that a Web
Server accessing a MS SQL Database, requires a CPU License on the
Database server for each physical CPU the SQL server is permitted to
use.

I have always licensed our SQL Servers in CPU mode when being accessed
by a web server using anonymous connections to the web server.

--
--
spamfree999@.rrohio.com
(Remove 999 to reply to me)|||Erland Sommarskog wrote:
> John Dalberg (john_dd@.hotmail.com) writes:
> > I am planning to build a server to be used as a SQL Server and web
server.
> > Right now I can only use a single box for both.
> > bob.mckenna@.rbc.com
> > I have read some threads were dual processors are having problems
with
> > some parallel queries and the suggestions of having sql server use
a
> > single CPU.
> > My budget is limited so I am debating whether to get 2.6G dual xeon
533FSB
> > or dual P4 800FSB (DRR@. ram) or stick with a speedy single cpu.
> > If I get a dual cpu motherboard, is it a good idea to have 1 cpu
used for
> > sql server and the other for everything else?
> Machine configurations is not my best game, but if you are going to
have
> both SQL Server and web server on the same box, I would definitely go
for
> two CPUs. (Or at least one CPU that is hyper-threaded.)
> As for SQL Server and parallel queries, yes, there is a potential
problem.
> I have seen more than once, SQL Server being too optimistic about
parallel
> query plans, and taken a plan with poor performance. What we usually
do,
> when we run into these queries is to add the query hint OPTION
(MAXDOP 1)
> which turns of parallellism for that query.
> A more definitive cure is to set the configuration option "Max
degress of
> parllellism" to 1. Note that this is not the same as confining SQL
Server
> to one CPU only, but that one single query can only take one
processor. Two
> users executing different queries can still get one CPU each.
> Giving SQL Server only one CPU *may* be a good idea, if you expect
the
> web server and the rest to need substantial amount of resources. But
you
> could also get the effect that one processor is mainly idle, while
the
> other is working around the clock.
> So my recommendation would be set "Max degrees of Parallelism" to 1
(Or
> to 2, if you have two hyper-threaded CPUs), but let SQL Server use
both
> CPUs.
>
> Finally, there may be a licensing issue. I vaguely recall that for
some
> editions that you pay a license per processor, but please check this
with
> Microsoft. Licensing is definitely not my best game.
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp

Friday, March 9, 2012

dual processor benefit

Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?
Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:

> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we should
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to verify
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>
|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
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
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>

dual processor benefit

Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:

> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we shoul
d
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to veri
fy
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
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
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>

dual processor benefit

Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
Current db size is 62 gigabytes.
Our situation: We use Meditech hospital software which has it's own db
structure (mumps). Nightly, most of the data that is entered into the
"live" system is replicated to the SQL database. We recently upgraded the
Meditech software and now their SQL consultant is telling us that we should
be installing a second processor because their initial load program (in
which the program compares data in the Meditech system and the SQL to verify
it's all there) is taxing the CPU at >40%.
My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
believe, something in the newer Meditech software that's causing the
problem?Hi,
To directly answer your question: Yes SQL Server can utilize the processors
effectively.
But, CPU usage aprx. 40% is nothing, unless it is causing other issues on
the server. And if there were no other changes made to the server, its the
application that is causing the extra load.
hth
DeeJay Puar
"pdwight" wrote:
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we should
> be installing a second processor because their initial load program (in
> which the program compares data in the Meditech system and the SQL to verify
> it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as we
> believe, something in the newer Meditech software that's causing the
> problem?
>
>|||40% proc utilization is not high... If the batch + users run it up, you
may wish to get another processor... One of the big reasons to go multi proc
is to allow SQL to service 2 connections concurrently, and therefore no
single long running thing will block the processor queue...
--
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
"pdwight" <paulc@.mmcwm.com> wrote in message
news:OE6ogW$KFHA.2952@.TK2MSFTNGP10.phx.gbl...
> Currently running SQL 2K on a W2K sp3 box with one P3 1.2 processor.
> Current db size is 62 gigabytes.
> Our situation: We use Meditech hospital software which has it's own db
> structure (mumps). Nightly, most of the data that is entered into the
> "live" system is replicated to the SQL database. We recently upgraded the
> Meditech software and now their SQL consultant is telling us that we
> should be installing a second processor because their initial load program
> (in which the program compares data in the Meditech system and the SQL to
> verify it's all there) is taxing the CPU at >40%.
> My question: Does SQL 2000 effectively utilize a second CPU or is it, as
> we believe, something in the newer Meditech software that's causing the
> problem?
>

Dual core or hyperthreading enabled

How can I find out if its a dual core box or a box with hyperthreading
enabled ?
So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
am using SQL 2005. Even if not through SQL, what are the other ways that I
can do so by running a command ?
Thanks
It's most likely dual core. Check the CPU model number. If it's the Opteron
8000 series, it's dual core.
Linchi
"Hassan" wrote:

> How can I find out if its a dual core box or a box with hyperthreading
> enabled ?
> So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
> CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
> that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
> am using SQL 2005. Even if not through SQL, what are the other ways that I
> can do so by running a command ?
> Thanks
>
>

Dual core or hyperthreading enabled

How can I find out if its a dual core box or a box with hyperthreading
enabled ?
So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
am using SQL 2005. Even if not through SQL, what are the other ways that I
can do so by running a command ?
ThanksIt's most likely dual core. Check the CPU model number. If it's the Opteron
8000 series, it's dual core.
Linchi
"Hassan" wrote:

> How can I find out if its a dual core box or a box with hyperthreading
> enabled ?
> So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
> CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
> that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
> am using SQL 2005. Even if not through SQL, what are the other ways that I
> can do so by running a command ?
> Thanks
>
>

Dual core or hyperthreading enabled

How can I find out if its a dual core box or a box with hyperthreading
enabled ?
So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
am using SQL 2005. Even if not through SQL, what are the other ways that I
can do so by running a command ?
ThanksIt's most likely dual core. Check the CPU model number. If it's the Opteron
8000 series, it's dual core.
Linchi
"Hassan" wrote:
> How can I find out if its a dual core box or a box with hyperthreading
> enabled ?
> So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
> CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
> that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
> am using SQL 2005. Even if not through SQL, what are the other ways that I
> can do so by running a command ?
> Thanks
>
>

Friday, February 17, 2012

dts vs. job

I have a DTS package that runs fine on a SQL 7 sp3 box. When I try and run
it as a job it fails with this error:
DTSRun: Loading...
Error: -2147287038 (80030002); Provider Error: 0 (0)
Error string: The system cannot find the file specified.
Error source: Microsoft Data Transformation Services (DTS) Package
Help file: sqldts.hlp
Help context: 713
Any ideas?Check out the following article:
269074 INF: How to Run a DTS Package as a Scheduled Job
http://support.microsoft.com/?id=269074
Rand
This posting is provided "as is" with no warranties and confers no rights.|||jj,
The problem is probably the context that DTS is executing under. One thing
to remember is that DTS is a client process, not a server process.
When run interactively, where is it running? If you are running it from your
machine, then access to the package would be obtained using your domain
rights. If you login to the SQL7 box, then the login that you use must have
the proper domain rights to get to the file.
Now, when you run it as a SQL Agent job, it will run either as the SQL
Server service account (e.g. MyDomain/MySQLServer) or if the job is not
owned by a sysadmin it runs as the SQL Agent proxy account (e.g.
MyDomain/MySQLAgentProxy). See:
xp_sql_agent_proxy
http://msdn.microsoft.com/library/d...-us/tsqlref/ts_
xp_aa-sz_8sdm.asp
SQL Server Agent Permissions Checks
http://msdn.microsoft.com/library/d...-us/adminsql/ad
_automate_054p.asp
Which ever account is _actually_ in use must have the necessary rights to
access the package.
Russell Fields
"jj" <jeff_detoro@.urmc.rochester.edu> wrote in message
news:eLsAD$eBEHA.744@.TK2MSFTNGP10.phx.gbl...
> I have a DTS package that runs fine on a SQL 7 sp3 box. When I try and run
> it as a job it fails with this error:
> DTSRun: Loading...
> Error: -2147287038 (80030002); Provider Error: 0 (0)
> Error string: The system cannot find the file specified.
> Error source: Microsoft Data Transformation Services (DTS) Package
> Help file: sqldts.hlp
> Help context: 713
> Any ideas?
>