Generating Unique Check Digits

Hi all,
I've implemented a small routine that generates "ID" numbers in hexadecimal
format. Does anyone know of any routines to generate a unique check digit
for a hexadecimal number? I've found several ways to do it in Base 10, but
not so much for hex. I really like the UCC mod 10(3) methods, but the check
digits are fairly linear in progression when I try to apply it to hex.
Here's an example of the types of ID's I'll be generating:
B951-D300-1E73-C1xx
Note that the dashes are just to "prettify it", and can be ignored for my
purposes. "xx" represents a placeholder for the 2 hexadecimal check digits.
B951D3001E73C1xx
Thanks. Any help is appreciated.Michael,
Do you need the check digit for more than
catching transcription or typing errors? Is there
a reason "fairly linear" in progression is not acceptable?
Steve Kass
Drew University
Michael C# wrote:

>Hi all,
>I've implemented a small routine that generates "ID" numbers in hexadecimal
>format. Does anyone know of any routines to generate a unique check digit
>for a hexadecimal number? I've found several ways to do it in Base 10, but
>not so much for hex. I really like the UCC mod 10(3) methods, but the chec
k
>digits are fairly linear in progression when I try to apply it to hex.
>Here's an example of the types of ID's I'll be generating:
>B951-D300-1E73-C1xx
>Note that the dashes are just to "prettify it", and can be ignored for my
>purposes. "xx" represents a placeholder for the 2 hexadecimal check digits
.
>B951D3001E73C1xx
>Thanks. Any help is appreciated.
>
>|||Like you mentioned, catching transcription errors is part of it; I also
don't want people to be able to reverse engineer and guess the previous ID
code; for instance, if the code ends with -C1B6, I don't want them to be
able to take a wild guess at -C0B5 being the previous ID.
Thanks
"Steve Kass" <skass@.drew.edu> wrote in message
news:OYxYyK7SFHA.3696@.TK2MSFTNGP15.phx.gbl...
> Michael,
> Do you need the check digit for more than
> catching transcription or typing errors? Is there
> a reason "fairly linear" in progression is not acceptable?
> Steve Kass
> Drew University
>
> Michael C# wrote:
>sql

Generating Replication Alerts through Perfmon monitoring.

We use a third party monitoring system that polls perfmon statistics on
different servers and generates alerts if a threshold is reached. For general
SQL tasks like backup, I programmatically set/reset User Settable counters
(10 in all) through system stored procedures sp_user_counter[1...10] in the
Scheduled task command.
But, this is not working in the case of replication. However, there are
other perfmon monitors that are specifically related to replication.
Would someone be able to identify what is the best parameter to monitor?
Thanks!!!
MZeeshan
Hi MZeeshan,
From your descriptions, I understand you would like to select a better
performance counter for your monitoring. However, I am not sure what you
are going to monitor and improve. Would you please show me more detailed
information, which I believe will make us closer to the resolution
You could find detailed introduction of all replication performance
counters in BOL topic "Using SQL Server Objects"
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||use replication alerts for this. Connect to your sql server using EM, expand
your server, expand the replication monitor node, and then expand the
replication alerts section.
You could monitor conflicts in SQLServer:Replication Merge, monitor the
latency of SQLServer:Replication LogReader and SQLServer:Replication Dist.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"MZeeshan" <mzeeshan@.community.nospam> wrote in message
news:F2BF344D-36CE-47D8-8D76-DDD8A0150B71@.microsoft.com...
> We use a third party monitoring system that polls perfmon statistics on
> different servers and generates alerts if a threshold is reached. For
general
> SQL tasks like backup, I programmatically set/reset User Settable counters
> (10 in all) through system stored procedures sp_user_counter[1...10] in
the
> Scheduled task command.
> But, this is not working in the case of replication. However, there are
> other perfmon monitors that are specifically related to replication.
> Would someone be able to identify what is the best parameter to monitor?
> Thanks!!!
> MZeeshan
|||Let me give you an example of how I am monitoring other tasks now. For
instance, I put the T-SQL below as a Schedule task:
BACKUP DATABASE AMA TO DISK='D:\DailyBackups\Full\AMA.bak' WITH INIT
IF (@.@.error<>0)
BEGIN
EXEC sp_user_counter1 900150
WAITFOR DELAY '00:01:10'
EXEC sp_user_counter1 0
END
Now, this keeps the counter1 with given value for 70 seconds. This is enough
time for the manager program to poll and pick up the value. This is then send
as a page or e-mail.
I tried to implement similar approach on system generated jobs (in SQL
Agent|Scheduler) once transactional replication was created. However, it
didn't work out.
What I basically need is to get information on some perfmon counter(s) that
shows "a change in state" if there is an error in any replication process
(logreader, distributer). The third party vendor we are using has ability to
monitor perfmon counters and provide information as alerts or graphs. FYI...
our internal standards do not allow us to use any of the SQL Server provided
alerting mechanisms (like SQL mail or smtp mail).
Is this clarification enough for you to understand what I am trying to get?
"Michael Cheng [MSFT]" wrote:

> Hi MZeeshan,
> From your descriptions, I understand you would like to select a better
> performance counter for your monitoring. However, I am not sure what you
> are going to monitor and improve. Would you please show me more detailed
> information, which I believe will make us closer to the resolution
> You could find detailed introduction of all replication performance
> counters in BOL topic "Using SQL Server Objects"
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Thanks for the information. I'll definitely check the counter information.
"Hilary Cotter" wrote:

> use replication alerts for this. Connect to your sql server using EM, expand
> your server, expand the replication monitor node, and then expand the
> replication alerts section.
> You could monitor conflicts in SQLServer:Replication Merge, monitor the
> latency of SQLServer:Replication LogReader and SQLServer:Replication Dist.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "MZeeshan" <mzeeshan@.community.nospam> wrote in message
> news:F2BF344D-36CE-47D8-8D76-DDD8A0150B71@.microsoft.com...
> general
> the
>
>
|||Hi MZeeshan,

>What I basically need is to get information on some perfmon counter(s)
that
>shows "a change in state" if there is an error in any replication process
>(logreader, distributer).
Based on my experience, you may perform:
1. SQL Server: Replication Agents Object. It represents the number of
instances of a given replication agent running currently.
2. Since Replication agents (logreader, distributer) correlate to some SQL
Agent jobs, an agent's failing is equivalent to a job's failing. They
should be able to add a step and run something like:
EXEC sp_user_counter2 nnnnnn
WAITFOR DELAY '00:01:10'
EXEC sp_user_counter2 0
Once the step in the replication agent job fails, the custom step can be
run.
However, please note that you will have to test it in your development
scenario before deploy it to the production server.
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I'll definitely check #1. However, with #2, I have already tested that and it
doesn't work. Every time there is a failure, the task will fail and a system
error is generated resulting in non-execution of the remaining portion of the
task.
I had similar problem with DBCC monitoring but I end up creating a DTS
package utilizing ON FAILURE and ON SUCCESS workflow options to identify next
command execution (in other words... generation of alerts through them).
However, I don't have that luxury of making such changes in system setup
replication tasks.
"Michael Cheng [MSFT]" wrote:

> Hi MZeeshan,
> that
> Based on my experience, you may perform:
> 1. SQL Server: Replication Agents Object. It represents the number of
> instances of a given replication agent running currently.
> 2. Since Replication agents (logreader, distributer) correlate to some SQL
> Agent jobs, an agent's failing is equivalent to a job's failing. They
> should be able to add a step and run something like:
> EXEC sp_user_counter2 nnnnnn
> WAITFOR DELAY '00:01:10'
> EXEC sp_user_counter2 0
> Once the step in the replication agent job fails, the custom step can be
> run.
> However, please note that you will have to test it in your development
> scenario before deploy it to the production server.
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||I checked different Replication counters and the two below as
SQL Server: Replication Logreader: Delivery Latency
Normal Working Range: 2-7 seconds
Error Threshold: 60 sec
Monitoring Duration: 2 minutus
SQL Server: Replication Distribution: Delivery Latency
Normal Working Range: 8-9 seconds
Error Threshold: 90 sec
Monitoring Duration: 2 minutus
In words, if the vendor Manager application finds out that the counters have
value equal to or higher than given in Error Threshold and finds this for two
cycles (2 minutes), then it will generate an error alert.
How that sounds?
"MZeeshan" wrote:
[vbcol=seagreen]
> I'll definitely check #1. However, with #2, I have already tested that and it
> doesn't work. Every time there is a failure, the task will fail and a system
> error is generated resulting in non-execution of the remaining portion of the
> task.
> I had similar problem with DBCC monitoring but I end up creating a DTS
> package utilizing ON FAILURE and ON SUCCESS workflow options to identify next
> command execution (in other words... generation of alerts through them).
> However, I don't have that luxury of making such changes in system setup
> replication tasks.
> "Michael Cheng [MSFT]" wrote:
|||Hi MZeeshan,
It's OK and if you have any questions or experience during your monitoring,
don't hesitate to let us know. We are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

generate update statements for existing data

Does anyone know how to write scripts for generating update statements for
existing data?
I found a stored procedure online that generates INSERT statements for a
given table, I was wondering if anyone has worked on a UPDATE generatorMike
What do you mean by "generating update"?
Do you want to build a script that does updateting?
declare @.sql varchar(400)
set @.sql='update '+ @.tablename+' set col'..........
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:9E10B2B9-80CC-4E50-9E34-5865A0C3BA1D@.microsoft.com...
> Does anyone know how to write scripts for generating update statements for
> existing data?
> I found a stored procedure online that generates INSERT statements for a
> given table, I was wondering if anyone has worked on a UPDATE generator|||I have a tables with about 1000 records and if I make changes I would like t
o
generate script (UPDATE scripts) for the existing data that I could run on
another server or ship it to a client with the latest changes instead of a
restore.
there is a good insert script available at
http://vyaskn.tripod.com/code.htm#inserts , I am looking for something
similar for UPDATE
"Uri Dimant" wrote:

> Mike
> What do you mean by "generating update"?
> Do you want to build a script that does updateting?
>
> declare @.sql varchar(400)
> set @.sql='update '+ @.tablename+' set col'..........
>
> "Mike" <Mike@.discussions.microsoft.com> wrote in message
> news:9E10B2B9-80CC-4E50-9E34-5865A0C3BA1D@.microsoft.com...
>
>|||Mike
Do you consider using Replication/Triggers ? It will be much better than
generating SQL script.
If you use SQL Server 2005 you can create a SNAPSHOP database ( ah i forgot
, it should be on the same server),sorry.
"Mike" <Mike@.discussions.microsoft.com> wrote in message
news:00EF43C1-EBF7-4422-99D0-A1979F3500A0@.microsoft.com...
>I have a tables with about 1000 records and if I make changes I would like
>to
> generate script (UPDATE scripts) for the existing data that I could run on
> another server or ship it to a client with the latest changes instead of a
> restore.
> there is a good insert script available at
> http://vyaskn.tripod.com/code.htm#inserts , I am looking for something
> similar for UPDATE
> "Uri Dimant" wrote:
>|||Mike wrote:
> I have a tables with about 1000 records and if I make changes I would like
to
> generate script (UPDATE scripts) for the existing data that I could run on
> another server or ship it to a client with the latest changes instead of a
> restore.
> there is a good insert script available at
> http://vyaskn.tripod.com/code.htm#inserts , I am looking for something
> similar for UPDATE
>
http://www.red-gate.com/products/SQ...mpare/index.htm
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||Try www.sqlscripter.com to generate data scripts. All types are supported
(Insert, Update, Delete).
It's free.
Thomas
"Mike" wrote:

> Does anyone know how to write scripts for generating update statements for
> existing data?
> I found a stored procedure online that generates INSERT statements for a
> given table, I was wondering if anyone has worked on a UPDATE generator

Generate SQL script and columns order

I am using Generate SQL script or scptxft tool for generartion creation
script for my database.
But unfortunally this script generates order for columns in creating
table not saticfying me. I need to have order exactly like I see in
Enterprise Manager, but the default order is other...
Can anybode give an advise how solve this problem?
Hi,
I think you can not.
Try doing a reverse engineering if you have Erwin data modeller or else you
have to arrange manually.
Thanks
Hari
SQL Server MVP
"Sergi Adamchuk" <adamchuk@.gmail.com> wrote in message
news:1126006864.707536.128230@.o13g2000cwo.googlegr oups.com...
>I am using Generate SQL script or scptxft tool for generartion creation
> script for my database.
> But unfortunally this script generates order for columns in creating
> table not saticfying me. I need to have order exactly like I see in
> Enterprise Manager, but the default order is other...
> Can anybode give an advise how solve this problem?
>
|||Sergi Adamchuk wrote:
> I am using Generate SQL script or scptxft tool for generartion
> creation script for my database.
> But unfortunally this script generates order for columns in creating
> table not saticfying me. I need to have order exactly like I see in
> Enterprise Manager, but the default order is other...
> Can anybode give an advise how solve this problem?
I just did a little digging into the SQL EM Generate SQL Scripts and the
Design Table functions to see how they were querying the list of columns
in the tables for display.
It appears they are both using the sp_MShelpcolumns system procedure
with the OrderBy column specified as 'id'. With that parameter, you
should be seeing the order of the columns as they are ordered by their
ColID in syscolumns.
I tested on SQL Server 2000 SP4 (Server and Client Tools). If you are
not seeing the same result from those two functions, can you tell me:
1- Are you running SP4 on the server and/or the client
2- What do you see as the column order when you query the syscolumns
table for the table in question and order by the ColID column? Which
version of the output is correct and which is incorrect?
You can use:
Select name from syscolumns where id = object_id('<table_name>') order
by colid
David Gugick
Quest Software
www.imceda.com
www.quest.com

Generate SQL for a table

Hi

I have two questions

i) is there any SP which will generates SQL Script for a table including all constarint(PK,FK), index etc. and the table data in the format of "INSERT INTO" . if NO, how can i create to do so, or any other SP which will help me( may be third party one)

ii)Where had "Scptxfr.exe" gone in SQL Server 2005 ?

Regards,

Thanks.

Gurpreet S. Gill

There is no SP. You will have to create one yourself or use SMO for example. I don't know the answer to the 2nd one. I am moving the thread to Tools forum to see if someone there might know.|||

Gurpreet Singh Gill wrote:

Hi

I have two questions

i) is there any SP which will generates SQL Script for a table including all constarint(PK,FK), index etc. and the table data in the format of "INSERT INTO" . if NO, how can i create to do so, or any other SP which will help me( may be third party one)

ii)Where had "Scptxfr.exe" gone in SQL Server 2005 ?

Regards,

Thanks.

Gurpreet S. Gill

Hi,

if you are a .Net developer the insert scripts are already genrated for you by the wizard if you have pk in every tables. You might be interested in using it. even if you are not a VS developer

the answer to the second question is just a click away. here. check this out

look for this topic Where to Find SCPTXFR?

http://www.sqlservercentral.com/columnists/jreade/howtoscheduleasqlserverdatabasecreationscript.asp

thanks,

joey

|||

joey

I dont want to create it by .NET code infact only by using the some SP, or inside SSMS only.

I read the artical but i dont find any thing about where is the SCPTXFR.EXE had gone, only one line say, "this is missing", but they are refering the Beta version of SQL Server.

Regards,

Thanks.

Gurpreet S. Gill

|||

the title is misleading. sorry

anyway you can still use the v2000 version of scptxfr.exe

with 2005

|||

I know about scptxfr.exe, I want only one table Script(not all), with Data too.

|||

hi,

got this one from another thread

you can use the sql server wizard to generate scripts insert, update, delete query

Run sql server enterprise manager > tools > wizards > database > create stored procedures wizards.

choose the table and click on insert.

on the completing tab click on edit then click edit Sql

regards,

joey

|||

Sorry to say man, i want to create the SP which will Generate the SQL Script(including Constaints, indexes, checks..etc) for the table as well as the data of that table. The aim is to create the .sql file, which can be used for migration to other DB with the table(create script) with data.

|||I was struggling with the same case a few months back in SQL Server 2005 as the wizard does not include drop statements before creating the object. Unlike SQL Server 2000, the 2005 version uses the IF NOT EXISTS logic instead of the IF EXISTS logic. This is where chanced upon Scriptio, a tool created by SQLTeam.com. From the looks of your requirement, you definitely have to write a script (or an application) to generate an INSERT Statement if you want to migrate the data as well. Why don't you just generate a script to build the database and use SSIS to migrate the data afterwards?|||

Basically, the things are bit different for me, we had a setup at client end, which uses the SQL Server 2005 as a backend(before that the application was using the SQL Base by Centura/Gurpta Technologies).Client dont have SSMS(only Database Services), infact they are using the SQL Talk(again the tool from the same). they want the same funcrionalties as provided by SQL Base, this procedure, which i need is one of them

Could any body help me.

Regards,

Thanks.

Gurpreet S. Gill

Generate scripts generates dump (9.0.3152)

When I attempt to generate scripts via SSMS for several databases on this server (x64 Enterprise Windows 2003 Server SP1), I receive a "severe error" message. I have run DBCC commands of various sorts and backed up and restored but the error persists.

I have read other posts on this forum that seem to be asking about related issues and the response appears to be "talk with support" or "post a bug report". What should I do? Any assistance would be appreciated.

Here's the dump:

=====================================================================
BugCheck Dump
=====================================================================

This file is generated by Microsoft SQL Server
version 9.00.3152.00
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 time is 16:55:02 03/20/07.
4 Unknown CPU 9., 2205 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.

Memory
MemoryLoad = 54%
Total Physical = 4951 MB
Available Physical = 2260 MB
Total Page File = 28583 MB
Available Page File = 26144 MB
Total Virtual = 8388607 MB
Available Virtual = 8383329 MB
***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0052.txt
SqlDumpExceptionHandler: Process 55 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 03/20/07 16:55:02 spid 55
*
*
* Exception Address = 00000000021B4CEF Module(sqlservr+00000000011B4CEF)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 000000001DC6BEE4
* Input Buffer 510 bytes -
* SELECT SCHEMA_NAME(v.schema_id) AS [View_Schema], v.name AS [
* View_Name], st.name AS [Name], st.no_recompute AS [NoAutomaticRecomputat
* ion], st.auto_created AS [IsAutoCreated], CAST(1 - INDEXPROPERTY(st.obje
* ct_id,st.name,N'IsStatistics') AS bit) AS [IsFromIndexCreation] FROM sys
* .all_views AS v INNER JOIN sys.stats st ON st.object_id=v.object_id WHER
* E (v.type = 'V') ORDER BY [View_Schema] ASC,[View_Name] ASC,[Name] ASC
*
*
* MODULE BASE END SIZE
* sqlservr 0000000001000000 0000000003523FFF 02524000
* ntdll 0000000078EC0000 0000000078FF8FFF 00139000
* kernel32 0000000077D40000 0000000077EB2FFF 00173000
* MSVCR80 0000000078130000 00000000781FEFFF 000cf000
* msvcrt 000007FF7FC00000 000007FF7FC85FFF 00086000
* MSVCP80 000000007C420000 000000007C530FFF 00111000
* ADVAPI32 000007FF7FEE0000 000007FF7FFE4FFF 00105000
* RPCRT4 000007FF7FD30000 000007FF7FED8FFF 001a9000
* USER32 0000000078C30000 0000000078D3BFFF 0010c000
* GDI32 000007FF7FC90000 000007FF7FD28FFF 00099000
* CRYPT32 000007FF7D180000 000007FF7D2DEFFF 0015f000
* MSASN1 000007FF7D150000 000007FF7D179FFF 0002a000
* Secur32 000007FF7E7F0000 000007FF7E811FFF 00022000
* MSWSOCK 000007FF76FE0000 000007FF7705BFFF 0007c000
* WS2_32 000007FF77150000 000007FF7717FFFF 00030000
* WS2HELP 000007FF77140000 000007FF7714BFFF 0000c000
* USERENV 000007FF7C4A0000 000007FF7C5A8FFF 00109000
* opends60 00000000333E0000 00000000333E7FFF 00008000
* NETAPI32 000007FF77370000 000007FF77407FFF 00098000
* SHELL32 000007FF7F190000 000007FF7FB97FFF 00a08000
* SHLWAPI 000007FF7EF60000 000007FF7EFFAFFF 0009b000
* IMM32 000007FF7D320000 000007FF7D358FFF 00039000
* comctl32 000007FF7F000000 000007FF7F186FFF 00187000
* psapi 000007FF7E1B0000 000007FF7E1BFFFF 00010000
* instapi 0000000048060000 000000004806CFFF 0000d000
* sqlevn70 000000004F610000 000000004F7B8FFF 001a9000
* SQLOS 00000000344D0000 00000000344D5FFF 00006000
* rsaenh 000000000FFB0000 000000000FFEDFFF 0003e000
* AUTHZ 000007FF7E2C0000 000007FF7E2ECFFF 0002d000
* MSCOREE 000006427EE60000 000006427EED3FFF 00074000
* ole32 000007FF7ECE0000 000007FF7EF51FFF 00272000
* msv1_0 000007FF7E330000 000007FF7E373FFF 00044000
* iphlpapi 000007FF57250000 000007FF57280FFF 00031000
* kerberos 000007FF77410000 000007FF774C2FFF 000b3000
* cryptdll 000007FF7DAB0000 000007FF7DABEFFF 0000f000
* schannel 000007FF7DB70000 000007FF7DBB0FFF 00041000
* COMRES 000007FF7E920000 000007FF7E9E5FFF 000c6000
* XOLEHLP 000007FF5C560000 000007FF5C566FFF 00007000
* MSDTCPRX 000007FF67140000 000007FF67210FFF 000d1000
* msvcp60 0000000009460000 0000000009549FFF 000ea000
* MTXCLU 000007FF7B540000 000007FF7B569FFF 0002a000
* VERSION 000007FF7FBF0000 000007FF7FBFAFFF 0000b000
* WSOCK32 000007FF770F0000 000007FF770F9FFF 0000a000
* OLEAUT32 000007FF7E9F0000 000007FF7EB03FFF 00114000
* CLUSAPI 000007FF7B1C0000 000007FF7B1E3FFF 00024000
* RESUTILS 000007FF7B310000 000007FF7B32BFFF 0001c000
* DNSAPI 0000000009560000 00000000095ADFFF 0004e000
* winrnr 000007FF7E820000 000007FF7E82AFFF 0000b000
* WLDAP32 000007FF7E780000 000007FF7E7E5FFF 00066000
* rasadhlp 0000000009650000 0000000009656FFF 00007000
* security 000007FF77530000 000007FF77534FFF 00005000
* msfte 0000000049980000 0000000049D2DFFF 003ae000
* dbghelp 000000000BAA0000 000000000BBFCFFF 0015d000
* WINTRUST 000007FF7E210000 000007FF7E25DFFF 0004e000
* imagehlp 000007FF7E2A0000 000007FF7E2B2FFF 00013000
* dssenh 000000000FF70000 000000000FFABFFF 0003c000
* hnetcfg 000007FF6D1F0000 000007FF6D280FFF 00091000
* wshtcpip 000007FF76FA0000 000007FF76FAAFFF 0000b000
* NTMARTA 000007FF7E2F0000 000007FF7E32BFFF 0003c000
* SAMLIB 000007FF76F80000 000007FF76F95FFF 00016000
* ntdsapi 000007FF7DAD0000 000007FF7DAF3FFF 00024000
* xpsp2res 000007FF5C210000 000007FF5C4D6FFF 002c7000
* CLBCatQ 0000000003530000 000000000360CFFF 000dd000
* sqlncli 00000000337A0000 0000000033A5FFFF 002c0000
* COMCTL32 000007FF76200000 000007FF762EDFFF 000ee000
* comdlg32 000007FF7D360000 000007FF7D3D6FFF 00077000
* SQLNCLIR 0000000035000000 0000000035032FFF 00033000
* msftepxy 0000000003670000 0000000003690FFF 00021000
* xpsqlbot 000000004A7C0000 000000004A7C7FFF 00008000
* xpstar90 0000000053C30000 0000000053CB5FFF 00086000
* SQLSCM90 0000000053AD0000 0000000053ADBFFF 0000c000
* ODBC32 000007FF63EB0000 000007FF63F16FFF 00067000
* BatchParser90 00000000520C0000 00000000520ECFFF 0002d000
* ATL80 000000007C630000 000000007C64DFFF 0001e000
* odbcint 000007FF63DC0000 000007FF63DD7FFF 00018000
* xpstar90 000000000FC60000 000000000FC85FFF 00026000
* xplog70 0000000034730000 000000003473FFFF 00010000
* xplog70 000000000FCA0000 000000000FCA2FFF 00003000
*
* P1Home: FFFFFADF7A660868:
* P2Home: 000000000AC3E180: FFFFFADF7A660868 000000000AC3E180 0000000000000001 000000009EB0A930 00010000
00000000 FFFFFADF878AD010
* P3Home: 0000000000000001:
* P4Home: 000000009EB0A930: 0000000000000000 000000009EC4E1D8 000000009EB8A000 0000006400000018 00000000
9EACE000 FFFFFFFF00000000
* P5Home: 0001000000000000:
* P6Home: FFFFFADF878AD010:
* ContextFlags: 000000000010001F:
* MxCsr: 0000000000001FA0:
* SegCs: 0000000000000033:
* SegDs: 000000000000002B:
* SegEs: 000000000000002B:
* SegFs: 0000000000000053:
* SegGs: 000000000000002B:
* SegSs: 000000000000002B:
* EFlags: 0000000000010246: 005C003A0043003D 0067006F00720050 0020006D00610072 0065006C00690046 00510053
005C0073 004C004D0058004C
* Rax: 000000001DC6BD50:
* Rcx: 0000000000000000:
* Rdx: 0000000000000000:
* Rbx: 0000000000000001:
* Rsp: 000000000AC3E720: 000000000AC3E778 00000000013DA150 0000000000000000 0000000000000000 00000000
00000000 000000009EB9DD40
* Rbp: 000000009EB0A930: 0000000000000000 000000009EC4E1D8 000000009EB8A000 0000006400000018 00000000
9EACE000 FFFFFFFF00000000
* Rsi: 0000000000000000:
* Rdi: 0000000000000000:
* R8: 000000011DC6BD50: 000000001DC60001 0000000000000000 0000000000000000 0000000000000000 00000000
00000031 000000011DC6ACB0
* R9: 000000009EC4E228: 0000000000000000 0000000000000000 000000009EB0A930 0000000000000000 00000000
00000000 0000000000000000
* R10: 0000000001017C00: 2444C74878EC8348 5C8948FFFFFFFE30 4868246C89487024 247C894860247489 894C5024
64894C58 8B48DA8B4848246C
* R11: 000000000AC3E988: 0000000000000000 00000000FFFFFFFF 0000000000000000 0000000000000000 00000000
FFFFFFFF 0000000000000000
* R12: 000000011DC6BD50: 000000001DC60001 0000000000000000 0000000000000000 0000000000000000 00000000
00000031 000000011DC6ACB0
* R13: 000000000AC3EA00: 0000000000000000 0000000000000000 0000000002ECF280 0000000000000000 FFFFFFFF
FFFFFFFE 000000011D9581C0
* R14: 0000000003640580: 0000000200000000 0000000000000008 0000026300000000 0000000003640080 00000001
1DC6C300 000000011DC6A2B0
* R15: 0000000000000002:
* Rip: 00000000021B4CEF: 848900000194808B 548D480000018024 3687E8C88B497824 485024448948FEEE 1374187D
3B66E88B 01DCB58B187D8B66
* *******************************************************************************
* -
* Short Stack Dump
00000000021B4CEF Module(sqlservr+00000000011B4CEF)
00000000021BAD40 Module(sqlservr+00000000011BAD40)
00000000021BAEBA Module(sqlservr+00000000011BAEBA)
00000000021BB029 Module(sqlservr+00000000011BB029)
00000000017B32FA Module(sqlservr+00000000007B32FA)
0000000001343FBC Module(sqlservr+0000000000343FBC)
0000000002527308 Module(sqlservr+0000000001527308)
0000000001CC9A78 Module(sqlservr+0000000000CC9A78)
0000000001391E90 Module(sqlservr+0000000000391E90)
0000000001343ACB Module(sqlservr+0000000000343ACB)
0000000001343B70 Module(sqlservr+0000000000343B70)
0000000001343D4F Module(sqlservr+0000000000343D4F)
0000000001079D91 Module(sqlservr+0000000000079D91)
00000000010796A1 Module(sqlservr+00000000000796A1)
000000000147EE04 Module(sqlservr+000000000047EE04)
000000000147EEBB Module(sqlservr+000000000047EEBB)
0000000001023AA2 Module(sqlservr+0000000000023AA2)
00000000010243A2 Module(sqlservr+00000000000243A2)
0000000001035FDA Module(sqlservr+0000000000035FDA)
00000000010355E5 Module(sqlservr+00000000000355E5)
00000000010366C8 Module(sqlservr+00000000000366C8)
0000000001289FEE Module(sqlservr+0000000000289FEE)
000000000100782E Module(sqlservr+000000000000782E)
0000000001007FB2 Module(sqlservr+0000000000007FB2)
00000000010079D1 Module(sqlservr+00000000000079D1)
000000000146B4D7 Module(sqlservr+000000000046B4D7)
000000000146BC0A Module(sqlservr+000000000046BC0A)
000000000146BB01 Module(sqlservr+000000000046BB01)
000000000146B999 Module(sqlservr+000000000046B999)
00000000781337A7 Module(MSVCR80+00000000000037A7)
0000000078133864 Module(MSVCR80+0000000000003864)
0000000077D6B69A Module(kernel32+000000000002B69A)

PSS @.0x0000000099D9DBF0
--

CSession @.0x0000000099D9C410
-
m_spid = 55 m_cRef = 22 m_rgcRefType[0] = 1
m_rgcRefType[1] = 1 m_rgcRefType[2] = 19 m_rgcRefType[3] = 1
m_rgcRefType[4] = 0 m_rgcRefType[5] = 0 m_pmo = 0x0000000099D9C080
m_pstackBhfPool = 0x0000000000000000 m_dwLoginFlags = 0x83e0 m_fBackground = 0
m_fClientRequestConnReset = 0 m_fUserProc = -1 m_fConnReset = 0
m_fIsConnReset = 0 m_fInLogin = 0 m_fAuditLoginSent = 1
m_fAuditLoginFailedSent = 0 m_fReplRelease = 0 m_fKill = 0
m_ulLoginStamp = 122 m_eclClient = 5 m_protType = 6
m_hHttpToken = FFFFFFFFFFFFFFFF

m_pV7LoginRec

0000000000000000: 5c010000 02000972 00100000 00000006 e8130000 ?\......r............

0000000000000014: 00000000 e0830000 00000000 00000000 5e000f00 ?................^...

0000000000000028: 00000000 00000000 7c002600 c8000f00 e6000000 ?........|.&.........

000000000000003C: e6001c00 1e010000 1e010000 0014c23f 4c1e1e01 ?...............?L...

0000000000000050: 3e005c01 00005c01 00000000 0000???????????????>.\...\.......

CPhysicalConnection @.0x0000000099D9C2E0

m_pPhyConn->m_pmo = 0x0000000099D9C080
m_pPhyConn->m_pNetConn = 0x0000000099D9CB00
m_pPhyConn->m_pConnList = 0x0000000099D9C3E0
m_pPhyConn->m_pSess = 0x0000000099D9C410 m_pPhyConn->m_fTracked = -1
m_pPhyConn->m_cbPacketsize = 4096 m_pPhyConn->m_fMars = 0 m_pPhyConn->m_fKill = 0

CBatch @.0x0000000099D9CFD0
--
m_pSess = 0x0000000099D9C410 m_pConn = 0x0000000099D9CEC0 m_cRef = 3
m_rgcRefType[0] = 1 m_rgcRefType[1] = 1 m_rgcRefType[2] = 1
m_rgcRefType[3] = 0 m_rgcRefType[4] = 0 m_pTask = 0x00000000062C4DA8

EXCEPT (null) @.0x000000000AC3B608

exc_number = 0 exc_severity = 0 exc_func = 0x0000000001891970

Task @.0x00000000062C4DA8

CPU Ticks used (ms) = 159 Task State = 2
WAITINFO_INTERNAL: WaitResource = 0x0000000000000000 WAITINFO_INTERNAL: WaitType = 0x0
WAITINFO_INTERNAL: WaitSpinlock = 0x0000000000000000 SchedulerId = 0x3
ThreadId = 0x1374 m_state = 0 m_eAbortSev = 0

EC @.0x0000000099D9DC00
-
spid = 55 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x0 ec_atomic = 0x0 __fSubProc = 1
ec_dbccContext = 0x0000000000000000 __pSETLS = 0x0000000099D9CF30 __pSEParams = 0x0000000099D9D350
__pDbLocks = 0x0000000099D9DCC0

SEInternalTLS @.0x0000000099D9CF30

m_flags = 0 m_TLSstatus = 3 m_owningTask = 0x00000000062C4DA8
m_activeHeapDatasetList = 0x0000000099D9CF30
m_activeIndexDatasetList = 0x0000000099D9CF40

SEParams @.0x0000000099D9D350
-
m_lockTimeout = 10000 m_isoLevel = 4096 m_logDontReplicate = 0
m_neverReplicate = 0 m_XactWorkspace = 0x0000000091150410
m_pSessionLocks = 0x0000000099D9DD70 m_pDbLocks = 0x0000000099D9DCC0
m_execStats = 0x000000011CADE810 m_pAllocFileLimit = 0x0000000000000000

Hi Bob,

For this one please open a case with product support. They will need to collect some more information from your system to determine the root of the problem.