Showing posts with label process. Show all posts
Showing posts with label process. Show all posts

Wednesday, March 28, 2012

HELP! The merge process could not retrieve identity range resource

Of course I get the error AFTER I start rolling into production!!!!
SQL Server 2000 SP4 and laptops with MSDE SP4 using MERGE with PULL.
There must be a bug in creating articles:
-- ****************** Table Contact with Int16 Identity field on primary key
PRINT 'Table Contact with Int16 Identity field on primary key'
exec sp_addmergearticle @.publication = N'_Prd', @.article = N'Contact',
@.source_owner = N'dbo',
@.source_object = N'Contact', @.type = N'table', @.description = null,
@.column_tracking = N'true',
@.pre_creation_cmd = N'drop', @.creation_script = null, @.schema_option =
0x000000000000CFF1,
@.article_resolver = N'Microsoft SQL Server DATETIME (Later Wins) Conflict
Resolver',
@.resolver_info = N'ChangeStamp',
@.subset_filterclause = null, @.vertical_partition = N'false',
@.destination_owner = N'dbo',
@.auto_identity_range = N'true',
@.pub_identity_range = 15000,
@.identity_range = 100,
@.threshold = 99,
@.verify_resolver_signature = 0,
@.allow_interactive_resolver = N'false', @.fast_multicol_updateproc = N'true',
@.check_permissions = 0
GO
Creates a constraint of:
([ContactId] > 12 and [ContactId] < 30000)
when it should be
([ContactId] > 12 and [ContactId] < 15000)
So now after a few clients I can no longer replicate cause I can only go to
32767.
So a few questions:
1) Why the bug and how do I fix it?
2) How do I fix things in production WITHOUT redoing the replication?
3) How can I tell what the current identity is? I mean, even starting at
30000, I should get lots of ranges on the laptops because they should be only
incrementing by 100. That should still be 27 laptops (100 * 2767) before I
blow the Integer data type. We've only rolled about 5-10.
The publisher range has always been twice as large as it should be. Also the
check constraint is one out. I've pointed these errors to MS developers and
apparently they're ok in SQL Server 2005 (haven't tested this yet).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||your threshold is all wrong. You need a smaller value. Basically you are
saying that at the very best you know that there will be 1 sync occurring
for every insert on Contact and you absolutely know beyond any shadow of a
doubt that this insert will never be kicked back and leave a gap in the
identity field.
For instance try this
create table identity_test
(pk int identity,charcol char(1))
go
begin tran
insert into identity_test (charcol) values ('x')
rollback tran
insert into identity_test (charcol) values ('x')
dbcc checkident('identity_test')
select * from identity_test
you get the value of 2. What happened to 1? you can't reclaim it without
doing a reseed.
This could happen when you want to bump up your threshold and then the next
insert will be kicked back by the constraint.
Pick a value for your range which represents the max amount of inserts which
could occur on your publisher between sync. Multiply by a number to give you
some wiggle room, I use 10. Then set your threshold to 80. This will mean
you get many opportunities for the range to be adjusted.
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
"Buzz" <buzz@.online.nospam> wrote in message
news:C73BE767-1CF1-4289-A875-3F271D6BA3B0@.microsoft.com...
> Of course I get the error AFTER I start rolling into production!!!!
> SQL Server 2000 SP4 and laptops with MSDE SP4 using MERGE with PULL.
> There must be a bug in creating articles:
> -- ****************** Table Contact with Int16 Identity field on primary
key
> PRINT 'Table Contact with Int16 Identity field on primary key'
> exec sp_addmergearticle @.publication = N'_Prd', @.article = N'Contact',
> @.source_owner = N'dbo',
> @.source_object = N'Contact', @.type = N'table', @.description = null,
> @.column_tracking = N'true',
> @.pre_creation_cmd = N'drop', @.creation_script = null, @.schema_option =
> 0x000000000000CFF1,
> @.article_resolver = N'Microsoft SQL Server DATETIME (Later Wins) Conflict
> Resolver',
> @.resolver_info = N'ChangeStamp',
> @.subset_filterclause = null, @.vertical_partition = N'false',
> @.destination_owner = N'dbo',
> @.auto_identity_range = N'true',
> @.pub_identity_range = 15000,
> @.identity_range = 100,
> @.threshold = 99,
> @.verify_resolver_signature = 0,
> @.allow_interactive_resolver = N'false', @.fast_multicol_updateproc =
N'true',
> @.check_permissions = 0
> GO
> Creates a constraint of:
> ([ContactId] > 12 and [ContactId] < 30000)
> when it should be
> ([ContactId] > 12 and [ContactId] < 15000)
> So now after a few clients I can no longer replicate cause I can only go
to
> 32767.
> So a few questions:
> 1) Why the bug and how do I fix it?
> 2) How do I fix things in production WITHOUT redoing the replication?
> 3) How can I tell what the current identity is? I mean, even starting at
> 30000, I should get lots of ranges on the laptops because they should be
only
> incrementing by 100. That should still be 27 laptops (100 * 2767) before I
> blow the Integer data type. We've only rolled about 5-10.
>

Friday, March 23, 2012

Help! Processing Hard Coded vs. Stored Procedure

Hi All,
I am just in the process of putting a script that updates a reporting table
into a stored procedure and have found that when run as a SP it takes soooo
much longer. Running the script in QA with the "WHERE" clauses hard coded
takes around 1 min, when I attempt to run via a SP with the "WHERE" clauses
replaced by variables (@.Title) that the user inputs it takes around 1 hour.
Below is a sample of both.
Can anyone shed any light on why? What am I doing wrong?
Thanks DC
Stored Procedure - -
CREATE PROCEDURE [dbo]. [sp_Report_Promoted_Issue_Impact_Analysi
s]
@.MarketGroup nvarchar (3),
@.Master_Title_id nvarchar (25),
@.Current_Title_Issue_Rank int
as
TRUNCATE TABLE Report_Promoted_Issue_Impact_Analysis
----
--INSERT INTO Report_Promoted_Issue_Impact_Analysis
( Retail_Type_id,
Retail_Type,
Market_Group_id,
Market_Group_Desc,
Outlet_id,
Branch_id,
EIS_Master_Title_id,
Title_id_2,
Issue_id,
Title_Issue_Rank,
Dist_Qty,
Sales_Qty
)
SELECT O.Retail_Class_id AS Retail_Type_id, MG.Retail_Class_Desc AS
Retail_Type, O.Market_Group_id, MG.Market_Group_Desc, OIH.Outlet_id,
TIB.Branch_id, T.EIS_Master_Title_id, OIH.Title_id_2,
OIH.Issue_id, TIB.Title_Issue_Rank, OIH.Dist_Qty, OIH.Sales_Qty
FROM Titles T RIGHT OUTER JOIN
Outlet_Issue_History OIH ON T.Title_id_2 =
OIH.Title_id_2 LEFT OUTER JOIN
Titles_Issues_Branch TIB ON OIH.Issue_id =
TIB.Issue_id AND OIH.Branch_id = TIB.Branch_id AND OIH.Title_id_2 =
TIB.Title_id_2 LEFT OUTER JOIN
Market_Groups MG RIGHT OUTER JOIN
Outlets O ON MG.Retail_Class_Market_Group_id =
O.Retail_Class_Market_Group_id ON OIH.Outlet_id = O.Outlet_id
WHERE (O.Market_Group_id <> @.MarketGroup) AND (T.EIS_Master_Title_id =
@.Master_Title_id) AND (TIB.Title_Issue_Rank = @.Current_Title_Issue_Rank) AND
(O.Retail_Class_id IN (N'A', N'B', N'K', N'S'))
Hard Coded Script - -
TRUNCATE TABLE Report_Promoted_Issue_Impact_Analysis
----
--
INSERT INTO Report_Promoted_Issue_Impact_Analysis
( Retail_Type_id,
Retail_Type,
Market_Group_id,
Market_Group_Desc,
Outlet_id,
Branch_id,
EIS_Master_Title_id,
Title_id_2,
Issue_id,
Title_Issue_Rank,
Dist_Qty,
Sales_Qty
)
SELECT O.Retail_Class_id AS Retail_Type_id, MG.Retail_Class_Desc AS
Retail_Type, O.Market_Group_id, MG.Market_Group_Desc, OIH.Outlet_id,
TIB.Branch_id, T.EIS_Master_Title_id, OIH.Title_id_2,
OIH.Issue_id, TIB.Title_Issue_Rank, OIH.Dist_Qty, OIH.Sales_Qty
FROM Titles T RIGHT OUTER JOIN
Outlet_Issue_History OIH ON T.Title_id_2 =
OIH.Title_id_2 LEFT OUTER JOIN
Titles_Issues_Branch TIB ON OIH.Issue_id =
TIB.Issue_id AND OIH.Branch_id = TIB.Branch_id AND OIH.Title_id_2 =
TIB.Title_id_2 LEFT OUTER JOIN
Market_Groups MG RIGHT OUTER JOIN
Outlets O ON MG.Retail_Class_Market_Group_id =
O.Retail_Class_Market_Group_id ON OIH.Outlet_id = O.Outlet_id
WHERE (O.Market_Group_id <> 'WW') AND (T.EIS_Master_Title_id = 'OK') AND
(TIB.Title_Issue_Rank = 5) AND (O.Retail_Class_id IN (N'A', N'B', N'K', N'S'
))Sounds to me like the query is using a different execution plan when it know
s
that the 'variables' have a particular value. Check the execution plans, hav
e
a look to see what indexes are being used, and see if this gives you some
clues into the situation.
Also make sure your statistics are updated, as this could cause the
optimiser to think that a particular plan might be best when it's really not
.
Rob
"David C" wrote:

> Hi All,
> I am just in the process of putting a script that updates a reporting tabl
e
> into a stored procedure and have found that when run as a SP it takes sooo
o
> much longer. Running the script in QA with the "WHERE" clauses hard coded
> takes around 1 min, when I attempt to run via a SP with the "WHERE" clause
s
> replaced by variables (@.Title) that the user inputs it takes around 1 hour
.
> Below is a sample of both.
> Can anyone shed any light on why? What am I doing wrong?
> Thanks DC
> Stored Procedure - -
> CREATE PROCEDURE [dbo]. [sp_Report_Promoted_Issue_Impact_Analysi
s]
> @.MarketGroup nvarchar (3),
> @.Master_Title_id nvarchar (25),
> @.Current_Title_Issue_Rank int
> as
> TRUNCATE TABLE Report_Promoted_Issue_Impact_Analysis
> ----
--INSERT INTO Report_Promoted_Issue_Impact_Analysis
> ( Retail_Type_id,
> Retail_Type,
> Market_Group_id,
> Market_Group_Desc,
> Outlet_id,
> Branch_id,
> EIS_Master_Title_id,
> Title_id_2,
> Issue_id,
> Title_Issue_Rank,
> Dist_Qty,
> Sales_Qty
> )
> SELECT O.Retail_Class_id AS Retail_Type_id, MG.Retail_Class_Desc AS
> Retail_Type, O.Market_Group_id, MG.Market_Group_Desc, OIH.Outlet_id,
> TIB.Branch_id, T.EIS_Master_Title_id, OIH.Title_id_2
,
> OIH.Issue_id, TIB.Title_Issue_Rank, OIH.Dist_Qty, OIH.Sales_Qty
> FROM Titles T RIGHT OUTER JOIN
> Outlet_Issue_History OIH ON T.Title_id_2 =
> OIH.Title_id_2 LEFT OUTER JOIN
> Titles_Issues_Branch TIB ON OIH.Issue_id =
> TIB.Issue_id AND OIH.Branch_id = TIB.Branch_id AND OIH.Title_id_2 =
> TIB.Title_id_2 LEFT OUTER JOIN
> Market_Groups MG RIGHT OUTER JOIN
> Outlets O ON MG.Retail_Class_Market_Group_id =
> O.Retail_Class_Market_Group_id ON OIH.Outlet_id = O.Outlet_id
> WHERE (O.Market_Group_id <> @.MarketGroup) AND (T.EIS_Master_Title_id =
> @.Master_Title_id) AND (TIB.Title_Issue_Rank = @.Current_Title_Issue_Rank) A
ND
> (O.Retail_Class_id IN (N'A', N'B', N'K', N'S'))
>
> Hard Coded Script - -
> TRUNCATE TABLE Report_Promoted_Issue_Impact_Analysis
> ----
--
> INSERT INTO Report_Promoted_Issue_Impact_Analysis
> ( Retail_Type_id,
> Retail_Type,
> Market_Group_id,
> Market_Group_Desc,
> Outlet_id,
> Branch_id,
> EIS_Master_Title_id,
> Title_id_2,
> Issue_id,
> Title_Issue_Rank,
> Dist_Qty,
> Sales_Qty
> )
> SELECT O.Retail_Class_id AS Retail_Type_id, MG.Retail_Class_Desc AS
> Retail_Type, O.Market_Group_id, MG.Market_Group_Desc, OIH.Outlet_id,
> TIB.Branch_id, T.EIS_Master_Title_id, OIH.Title_id_2
,
> OIH.Issue_id, TIB.Title_Issue_Rank, OIH.Dist_Qty, OIH.Sales_Qty
> FROM Titles T RIGHT OUTER JOIN
> Outlet_Issue_History OIH ON T.Title_id_2 =
> OIH.Title_id_2 LEFT OUTER JOIN
> Titles_Issues_Branch TIB ON OIH.Issue_id =
> TIB.Issue_id AND OIH.Branch_id = TIB.Branch_id AND OIH.Title_id_2 =
> TIB.Title_id_2 LEFT OUTER JOIN
> Market_Groups MG RIGHT OUTER JOIN
> Outlets O ON MG.Retail_Class_Market_Group_id =
> O.Retail_Class_Market_Group_id ON OIH.Outlet_id = O.Outlet_id
> WHERE (O.Market_Group_id <> 'WW') AND (T.EIS_Master_Title_id = 'OK') A
ND
> (TIB.Title_Issue_Rank = 5) AND (O.Retail_Class_id IN (N'A', N'B', N'K', N'
S'))
>|||use "with recompile" option in the stored proc.. Its just a guess.
Can you run the query and SP together and see the execution plan.
I think for the SP the execution plan is built with the
Report_Promoted_Issue_Impact_Analysis table filled. So it prepares for an
execution plan with the table full, but it gets truncated...
Hope this helps.
--
"David C" wrote:

> Hi All,
> I am just in the process of putting a script that updates a reporting tabl
e
> into a stored procedure and have found that when run as a SP it takes sooo
o
> much longer. Running the script in QA with the "WHERE" clauses hard coded
> takes around 1 min, when I attempt to run via a SP with the "WHERE" clause
s
> replaced by variables (@.Title) that the user inputs it takes around 1 hour
.
> Below is a sample of both.
> Can anyone shed any light on why? What am I doing wrong?
> Thanks DC
> Stored Procedure - -
> CREATE PROCEDURE [dbo]. [sp_Report_Promoted_Issue_Impact_Analysi
s]
> @.MarketGroup nvarchar (3),
> @.Master_Title_id nvarchar (25),
> @.Current_Title_Issue_Rank int
> as
> TRUNCATE TABLE Report_Promoted_Issue_Impact_Analysis
> ----
--INSERT INTO Report_Promoted_Issue_Impact_Analysis
> ( Retail_Type_id,
> Retail_Type,
> Market_Group_id,
> Market_Group_Desc,
> Outlet_id,
> Branch_id,
> EIS_Master_Title_id,
> Title_id_2,
> Issue_id,
> Title_Issue_Rank,
> Dist_Qty,
> Sales_Qty
> )
> SELECT O.Retail_Class_id AS Retail_Type_id, MG.Retail_Class_Desc AS
> Retail_Type, O.Market_Group_id, MG.Market_Group_Desc, OIH.Outlet_id,
> TIB.Branch_id, T.EIS_Master_Title_id, OIH.Title_id_2
,
> OIH.Issue_id, TIB.Title_Issue_Rank, OIH.Dist_Qty, OIH.Sales_Qty
> FROM Titles T RIGHT OUTER JOIN
> Outlet_Issue_History OIH ON T.Title_id_2 =
> OIH.Title_id_2 LEFT OUTER JOIN
> Titles_Issues_Branch TIB ON OIH.Issue_id =
> TIB.Issue_id AND OIH.Branch_id = TIB.Branch_id AND OIH.Title_id_2 =
> TIB.Title_id_2 LEFT OUTER JOIN
> Market_Groups MG RIGHT OUTER JOIN
> Outlets O ON MG.Retail_Class_Market_Group_id =
> O.Retail_Class_Market_Group_id ON OIH.Outlet_id = O.Outlet_id
> WHERE (O.Market_Group_id <> @.MarketGroup) AND (T.EIS_Master_Title_id =
> @.Master_Title_id) AND (TIB.Title_Issue_Rank = @.Current_Title_Issue_Rank) A
ND
> (O.Retail_Class_id IN (N'A', N'B', N'K', N'S'))
>
> Hard Coded Script - -
> TRUNCATE TABLE Report_Promoted_Issue_Impact_Analysis
> ----
--
> INSERT INTO Report_Promoted_Issue_Impact_Analysis
> ( Retail_Type_id,
> Retail_Type,
> Market_Group_id,
> Market_Group_Desc,
> Outlet_id,
> Branch_id,
> EIS_Master_Title_id,
> Title_id_2,
> Issue_id,
> Title_Issue_Rank,
> Dist_Qty,
> Sales_Qty
> )
> SELECT O.Retail_Class_id AS Retail_Type_id, MG.Retail_Class_Desc AS
> Retail_Type, O.Market_Group_id, MG.Market_Group_Desc, OIH.Outlet_id,
> TIB.Branch_id, T.EIS_Master_Title_id, OIH.Title_id_2
,
> OIH.Issue_id, TIB.Title_Issue_Rank, OIH.Dist_Qty, OIH.Sales_Qty
> FROM Titles T RIGHT OUTER JOIN
> Outlet_Issue_History OIH ON T.Title_id_2 =
> OIH.Title_id_2 LEFT OUTER JOIN
> Titles_Issues_Branch TIB ON OIH.Issue_id =
> TIB.Issue_id AND OIH.Branch_id = TIB.Branch_id AND OIH.Title_id_2 =
> TIB.Title_id_2 LEFT OUTER JOIN
> Market_Groups MG RIGHT OUTER JOIN
> Outlets O ON MG.Retail_Class_Market_Group_id =
> O.Retail_Class_Market_Group_id ON OIH.Outlet_id = O.Outlet_id
> WHERE (O.Market_Group_id <> 'WW') AND (T.EIS_Master_Title_id = 'OK') A
ND
> (TIB.Title_Issue_Rank = 5) AND (O.Retail_Class_id IN (N'A', N'B', N'K', N'
S'))
>|||Hi again, I have fixed this problem by creating and inserting into a temp
table first, the processing time is now down to 1-2 min.
The execution plans were quite different between the hard coded and the
original stored procedure.
Thanks again
DC
"David C" wrote:

> Hi All,|||This will be good if there aren't too many concurrent users.
Temporary tabl should be avoided as much as possible because it uses lot of
I/O.
I would suggest you to find the real reason and fix the proc.
if not possible try to use a table variable instead of a temporary table.
-Omnibuzz

Monday, March 12, 2012

HELP! Error atttaching DB

Hi!
When I try Attach a DB I have this error:
Error: 3624
Location: recovery.c:2440
Expression: seenCKptEnd
SPID: 51
Process ID: 1344
Any idea ?This is a multi-part message in MIME format.
--=_NextPart_000_0013_01C447E9.F642C6E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Are you sure that the transaction log file you are specifying to =sp_attach_db is the correct one? If you're not dealing with mismatched =files, I would recommend contacting Microsoft PSS for help in recovering =your database, as this is usually indicative of some sort of log =integrity problem.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Joao Pinto" <joao.pi@.mail.telepac.pt> wrote in message =news:3rrpb0dij3ge90ob16vrkbb8dusi0iqh0b@.4ax.com...
Hi!
When I try Attach a DB I have this error:
Error: 3624
Location: recovery.c:2440
Expression: seenCKptEnd
SPID: 51
Process ID: 1344
Any idea ?
--=_NextPart_000_0013_01C447E9.F642C6E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Are you sure that the transaction log file you are =specifying to sp_attach_db is the correct one? If you're not dealing with =mismatched files, I would recommend contacting Microsoft PSS for help in recovering =your database, as this is usually indicative of some sort of log integrity problem.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Joao Pinto" =wrote in message news:3rrpb0dij3g=e90ob16vrkbb8dusi0iqh0b@.4ax.com...Hi!When I try Attach a DB I have this error:Error: 3624Location: recovery.c:2440Expression: seenCKptEndSPID: 51Process ID: 1344Any idea ?

--=_NextPart_000_0013_01C447E9.F642C6E0--|||This is a multi-part message in MIME format.
--=_NextPart_000_130B_01C4487D.CEF8F2F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
Are you trying to attach the SQL 2000 MDF and LDF file to SQL 7. If yes, =you will not be able to attach a SQL 2000 database to SQL 7 due to
architectural changes. Only solution is to use DTS tools to transfer =objects and data.
Incase you are trying to attach the MDF and LDF of SQL 2000 to the same =version, then the issue might because of problem with the logfile as well as if the database was in an inconsistent state. If the MDF and =LDF file is from a suspect database, it is very difficult to attach.
If you have a backup, better option is to try restoring the backup =rather than using sp_attach_db.
Thanks
Hari
MCDBA
"Ryan Stonecipher [MSFT]" <ryanston@.online.microsoft.com> wrote in =message news:eIlBrSCSEHA.3628@.TK2MSFTNGP12.phx.gbl...
Are you sure that the transaction log file you are specifying to =sp_attach_db is the correct one? If you're not dealing with mismatched =files, I would recommend contacting Microsoft PSS for help in recovering =your database, as this is usually indicative of some sort of log =integrity problem.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Joao Pinto" <joao.pi@.mail.telepac.pt> wrote in message =news:3rrpb0dij3ge90ob16vrkbb8dusi0iqh0b@.4ax.com...
Hi!
When I try Attach a DB I have this error:
Error: 3624
Location: recovery.c:2440
Expression: seenCKptEnd
SPID: 51
Process ID: 1344
Any idea ?
--=_NextPart_000_130B_01C4487D.CEF8F2F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

Hi,Are you trying to attach the SQL 2000 MDF and LDF file =to SQL 7. If yes, you will not be able to attach a SQL 2000 database to SQL =7 due toarchitectural changes. Only solution is to use DTS tools to =transfer objects and data.
Incase you are trying to attach the MDF =and LDF of SQL 2000 to the same version, then the issue might because of =problem with the logfile
as well as if the database was in an inconsistent state. If the MDF =and LDF file is from a suspect database, it is very difficult to attach.
If you have a backup, better option is to try restoring the backup =rather than using sp_attach_db.
ThanksHariMCDBA
"Ryan Stonecipher [MSFT]" wrote in message news:eIlBrSCSEHA.3628=@.TK2MSFTNGP12.phx.gbl...
Are you sure that the transaction log file you are = specifying to sp_attach_db is the correct one? If you're not =dealing with mismatched files, I would recommend contacting Microsoft PSS for =help in recovering your database, as this is usually indicative of some sort =of log integrity problem.

Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Joao Pinto" =wrote in message news:3rrpb0dij3g=e90ob16vrkbb8dusi0iqh0b@.4ax.com...Hi!When I try Attach a DB I have this error:Error: 3624Location: = recovery.c:2440Expression: seenCKptEndSPID: 51Process =ID: 1344Any idea =?

--=_NextPart_000_130B_01C4487D.CEF8F2F0--|||Here is a way to get the database attached, if it is a SQL Server 2000
database.
1. Create a new database with the same name and make sure the file names
for the MDF and LDF are identical to the ones you want to attach.
2. After you create the database. Stop SQL Server.
3. Copy the original MDF and LDF files over the newly created ones.
4. Restart SQL server.
The database will probably sill come up suspect but you can then put it in
emergency mode and possibly get the data out.
Rand
This posting is provided "as is" with no warranties and confers no rights.

HELP! Corrupt MDF

While on vacation, a customer of ours had their RAID die and nobody seemed
to follow a good recovery process so when I came back all I was left with is
a bad MDF. When I use EM to attach I get Error 823: I/O Error (Bad Page ID)
...
Is there any way to force this to attach?Well I got it attached but I think it's toast because everything I try comes
back with an error of some kind or other.
Of course, backups were not functioning (not my network, I'm just trying to
help :p)
Me-thinks they're screwed.
"Bob Castleman" <nomail@.here> wrote in message
news:euC8AIbeGHA.2188@.TK2MSFTNGP04.phx.gbl...
> While on vacation, a customer of ours had their RAID die and nobody seemed
> to follow a good recovery process so when I came back all I was left with
> is a bad MDF. When I use EM to attach I get Error 823: I/O Error (Bad Page
> ID) ...
> Is there any way to force this to attach?
>|||Hey Bob,
I'm contractor and just got a call similar to your situation. But worse yet
is that the IT dept caused it! They had failed drive in RAID 5 config and
were pulling it to replace with spare but yanked wrong drive which then
failed the array...
There proud of themselves for forcing some kind of rebuild but they got 2
suspect DBs so they thought they'd detach and re-attach. Detach worked,
re-attach is giving the 823 torn page error.
So now they call me. Last back was mid-March. If I can recover any data,
I'd sure like to. How did you get yours to re-attach'
peace - kathy|||Hey Bob,
I'm contractor and just got a call similar to your situation. But worse yet
is that the IT dept caused it! They had failed drive in RAID 5 config and
were pulling it to replace with spare but yanked wrong drive which then
failed the array...
There proud of themselves for forcing some kind of rebuild but they got 2
suspect DBs so they thought they'd detach and re-attach. Detach worked,
re-attach is giving the 823 torn page error.
So now they call me. Last back was mid-March. If I can recover any data,
I'd sure like to. How did you get yours to re-attach'
peace - kathy|||Your best bet is to restore from a backup. If no backup is available, you
can do the following and live with some loss_of_data.
1. create a new empty db with the same name/path.
2. put the db into emergency mode (see alter db for sql2k5, modify
sysdatabases for sql2k)
3. take the db offline (see alter db)
4. swap the db files
5. put the db online (alter db)
6. run dbcc checkdb
-oj
"Kathy_Automation" <KathyAutomation@.discussions.microsoft.com> wrote in
message news:3039CC2A-8DF5-4B2C-A6AD-5016A681DA57@.microsoft.com...
> Hey Bob,
> I'm contractor and just got a call similar to your situation. But worse
> yet
> is that the IT dept caused it! They had failed drive in RAID 5 config and
> were pulling it to replace with spare but yanked wrong drive which then
> failed the array...
> There proud of themselves for forcing some kind of rebuild but they got 2
> suspect DBs so they thought they'd detach and re-attach. Detach worked,
> re-attach is giving the 823 torn page error.
> So now they call me. Last back was mid-March. If I can recover any data,
> I'd sure like to. How did you get yours to re-attach'
> peace - kathy|||Your best bet is to restore from a backup. If no backup is available, you
can do the following and live with some loss_of_data.
1. create a new empty db with the same name/path.
2. put the db into emergency mode (see alter db for sql2k5, modify
sysdatabases for sql2k)
3. take the db offline (see alter db)
4. swap the db files
5. put the db online (alter db)
6. run dbcc checkdb
-oj
"Kathy_Automation" <KathyAutomation@.discussions.microsoft.com> wrote in
message news:3039CC2A-8DF5-4B2C-A6AD-5016A681DA57@.microsoft.com...
> Hey Bob,
> I'm contractor and just got a call similar to your situation. But worse
> yet
> is that the IT dept caused it! They had failed drive in RAID 5 config and
> were pulling it to replace with spare but yanked wrong drive which then
> failed the array...
> There proud of themselves for forcing some kind of rebuild but they got 2
> suspect DBs so they thought they'd detach and re-attach. Detach worked,
> re-attach is giving the 823 torn page error.
> So now they call me. Last back was mid-March. If I can recover any data,
> I'd sure like to. How did you get yours to re-attach'
> peace - kathy

HELP! Corrupt MDF

While on vacation, a customer of ours had their RAID die and nobody seemed
to follow a good recovery process so when I came back all I was left with is
a bad MDF. When I use EM to attach I get Error 823: I/O Error (Bad Page ID)
...
Is there any way to force this to attach?Well I got it attached but I think it's toast because everything I try comes
back with an error of some kind or other.
Of course, backups were not functioning (not my network, I'm just trying to
help :p)
Me-thinks they're screwed.
"Bob Castleman" <nomail@.here> wrote in message
news:euC8AIbeGHA.2188@.TK2MSFTNGP04.phx.gbl...
> While on vacation, a customer of ours had their RAID die and nobody seemed
> to follow a good recovery process so when I came back all I was left with
> is a bad MDF. When I use EM to attach I get Error 823: I/O Error (Bad Page
> ID) ...
> Is there any way to force this to attach?
>|||Hey Bob,
I'm contractor and just got a call similar to your situation. But worse yet
is that the IT dept caused it! They had failed drive in RAID 5 config and
were pulling it to replace with spare but yanked wrong drive which then
failed the array...
There proud of themselves for forcing some kind of rebuild but they got 2
suspect DBs so they thought they'd detach and re-attach. Detach worked,
re-attach is giving the 823 torn page error.
So now they call me. Last back was mid-March. If I can recover any data,
I'd sure like to. How did you get yours to re-attach'
peace - kathy|||Your best bet is to restore from a backup. If no backup is available, you
can do the following and live with some loss_of_data.
1. create a new empty db with the same name/path.
2. put the db into emergency mode (see alter db for sql2k5, modify
sysdatabases for sql2k)
3. take the db offline (see alter db)
4. swap the db files
5. put the db online (alter db)
6. run dbcc checkdb
--
-oj
"Kathy_Automation" <KathyAutomation@.discussions.microsoft.com> wrote in
message news:3039CC2A-8DF5-4B2C-A6AD-5016A681DA57@.microsoft.com...
> Hey Bob,
> I'm contractor and just got a call similar to your situation. But worse
> yet
> is that the IT dept caused it! They had failed drive in RAID 5 config and
> were pulling it to replace with spare but yanked wrong drive which then
> failed the array...
> There proud of themselves for forcing some kind of rebuild but they got 2
> suspect DBs so they thought they'd detach and re-attach. Detach worked,
> re-attach is giving the 823 torn page error.
> So now they call me. Last back was mid-March. If I can recover any data,
> I'd sure like to. How did you get yours to re-attach'
> peace - kathy

Friday, March 9, 2012

HELP! Cannot pass GUID's through variables?

I have a project that uses GUID's througout and I'm completely stumped.

1) I create a "batch" GUID to batch the records I'm about to process.

2) I call a web service on a remote machine, and reserve the batch records by inserting the batch GUID into a string works fine

3)I call another web service that returns the rows that I just reserved as XML objects and insert into a string variable

4)I need to use the "batch"GUID variable which is typed as a string (DT_WSTR) as an added column so in a Data Flow Task I do the following:

a) use the XML string variable as the source of a XML Source Task -- works (now that I'm passing custom objects and not a dataset -- curious as to why I can't consume a dataset but thats a different question)

This is where things get tricky:
I've tried to add the BatchGUID as a derived column, as a datatype of DT_WSTR (unicode string) and convert it to uniqueidentifier in the Data Conversion task error, cannot convert unicode to uniqueidentifier (I know I can in C# and SQL Server so why not here).

I've tried to CAST the BatchGUID as a uniqueidentifier and pass that to the datasource -- again conversion error.

I've tried using the type Object and Casting to anything and that doesn't work either.

I've tried to pass the unicode all the way to the SQL Server Destination -- and insert into UniqueIdentifier field... again no go.

All help would be appreciated, at this point I can't see any way of using a UniqueIdentifier as a key field, and maintaining it through the package...
Is this a bug?

Oh and if you want to have some real fun, try returning the type of UniqueIdentifier as an output parameter using a ADO.NET connection.

Thanks!

Maybe a parameterized insert using the SQL Task and a property expression on the query to exchange the value of the GUID ID variable into the insert statement? Have you tried that?

Kirk Haselden
Author "SQL Server Integration Services"

|||

Could you elaborate more on how to implement the property expression in the query? I am doing exqactly as you said using a SQL task and trying to insert into custom logging tables via a sp call. I am using parameter mapping to map system variables to parameters in my sql call, however in my sp I am defining the guids as uniqueidentifiers but ssis system variable guids are strings. What is the easiest way to handle this and convert so it works?

Thanks!

|||

There's some examples here:

Using dynamic SQL in an OLE DB Source component
http://blogs.conchango.com/jamiethomson/archive/2005/12/09/2480.aspx

Setting Expressions
http://blogs.conchango.com/jamiethomson/archive/2006/03/11/3063.aspx

Dynamic modification of SSIS packages
http://blogs.conchango.com/jamiethomson/archive/2005/02/28/1085.aspx

-Jamie

Wednesday, March 7, 2012

Help! - Subscriptions won't run; here is the LOG file

2007-05-18 11:07:07 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86
unicode retail build) : Process ID
2007-05-18 11:07:07 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86
unicode retail build) : Process ID 3036
2007-05-18 11:07:07 - ? [101] SQL Server <my computer name> version 8.00.760
(0 connection limit)
2007-05-18 11:07:07 - ? [102] SQL Server ODBC driver version 3.85.1025
2007-05-18 11:07:07 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
Local host server is
2007-05-18 11:07:07 - ? [310] 1 processor(s) and 768 MB RAM detected
2007-05-18 11:07:07 - ? [339] Local computer is <my computer name> running
Windows NT 5.2 (3790)
2007-05-18 11:07:07 - ! [364] The Messenger service has not been started -
NetSend notifications will not be sent
2007-05-18 11:07:07 - ? [129] SQLSERVERAGENT starting under Windows NT
service control
2007-05-18 11:07:07 - + [260] Unable to start mail session (reason: No mail
profile defined)
2007-05-18 11:07:07 - + [396] An idle CPU condition has not been defined -
OnIdle job schedules will have no effect
2007-05-18 11:08:03 - + [000] Schedule 2 has already been cached by job
0xD9C1E426A1AAD5498B92EDBEA79A8654
2007-05-18 11:10:01 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 2
2007-05-18 11:10:01 - + [163] 1 operations applied (0 remaining)
2007-05-18 11:12:09 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 3
2007-05-18 11:12:09 - + [000] Schedule 3 has already been cached by job
0x4CC373CEC320804D9AF67C7704B6F747
2007-05-18 11:13:23 - + [000] Schedule 4 has already been cached by job
0x6CC98A2943018F488AF45B20E63E1DC7
2007-05-18 11:15:00 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 4
2007-05-18 11:15:00 - + [163] 1 operations applied (0 remaining)
2007-05-18 11:22:46 - + [000] Schedule 5 has already been cached by job
0xAE9A0B33E1E4374B9B60F807A7772999
2007-05-18 11:24:00 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 5
2007-05-18 11:24:00 - + [163] 1 operations applied (0 remaining)
2007-05-18 11:32:02 - + [000] Schedule 6 has already been cached by job
0x05979EE4A61D87489C664CE2D68B0D24
2007-05-18 11:33:00 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 6
2007-05-18 11:33:00 - + [163] 1 operations applied (0 remaining)
2007-05-18 11:35:23 - + [000] Schedule 7 has already been cached by job
0xBAE7D146168A5B4586DBB7333EE1D0C5
2007-05-18 11:36:00 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 7
2007-05-18 11:36:00 - + [163] 1 operations applied (0 remaining)
2007-05-18 11:39:55 - + [000] Schedule 8 has already been cached by job
0x877BA9F8E7147E4EA91EB6F2E1E701C0
2007-05-18 11:41:00 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 8
2007-05-18 11:41:00 - + [163] 1 operations applied (0 remaining)
2007-05-18 15:40:07 - + [000] Schedule 9 has already been cached by job
0xA5BBF8F9EA07834EA0B475B553911869
2007-05-18 15:41:01 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 9
2007-05-18 15:41:01 - + [163] 1 operations applied (0 remaining)
2007-05-18 15:42:47 - + [000] Schedule 10 has already been cached by job
0x13322C18AB3BC5409D40385C02129F54
2007-05-18 15:45:01 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 10
2007-05-18 15:45:01 - + [163] 1 operations applied (0 remaining)
2007-05-18 15:48:17 - + [000] Schedule 11 has already been cached by job
0x830F8A65D9A9BC4A914123CF6CB5E8F9
2007-05-18 15:50:00 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 11
2007-05-18 15:50:00 - + [163] 1 operations applied (0 remaining)
2007-05-18 16:02:05 - + [000] Schedule 12 has already been cached by job
0x6E49B2772349B84CB65BD39CC3C47810
2007-05-18 16:05:01 - + [162] Internal request (from SetJobNextRunDate
[reason: schedule will not run again]) to deactivate schedule 12
2007-05-18 16:05:01 - + [163] 1 operations applied (0 remaining)
2007-05-21 09:16:02 - + [000] Schedule 13 has already been cached by job
0xEFBDC763EB628A4AA037D27A483ADE7C
2007-05-21 09:21:16 - + [000] Schedule 14 has already been cached by job
0xB79CC4672770A94492543246E78D049F
2007-05-21 09:22:40 - + [000] Schedule 15 has already been cached by job
0xA812252789CF72418FA14FEC66C90089
2007-05-21 09:31:11 - + [000] Schedule 16 has already been cached by job
0xCDDBFEFA899ACE4DBADC96FFC6932279
2007-05-21 09:33:05 - + [000] Schedule 17 has already been cached by job
0x4010169385C38E478077F9AE67D7E298I was able to correct this error message 2007-05-18 11:07:07 - ! [364] The
Messenger service has not been started -
NetSend notifications will not be sent
I started this service but it still did now process.
"OriginalStealth" wrote:
> 2007-05-18 11:07:07 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86
> unicode retail build) : Process ID
> 2007-05-18 11:07:07 - ? [100] Microsoft SQLServerAgent version 8.00.760 (x86
> unicode retail build) : Process ID 3036
> 2007-05-18 11:07:07 - ? [101] SQL Server <my computer name> version 8.00.760
> (0 connection limit)
> 2007-05-18 11:07:07 - ? [102] SQL Server ODBC driver version 3.85.1025
> 2007-05-18 11:07:07 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
> Local host server is
> 2007-05-18 11:07:07 - ? [310] 1 processor(s) and 768 MB RAM detected
> 2007-05-18 11:07:07 - ? [339] Local computer is <my computer name> running
> Windows NT 5.2 (3790)
> 2007-05-18 11:07:07 - ! [364] The Messenger service has not been started -
> NetSend notifications will not be sent
> 2007-05-18 11:07:07 - ? [129] SQLSERVERAGENT starting under Windows NT
> service control
> 2007-05-18 11:07:07 - + [260] Unable to start mail session (reason: No mail
> profile defined)
> 2007-05-18 11:07:07 - + [396] An idle CPU condition has not been defined -
> OnIdle job schedules will have no effect
> 2007-05-18 11:08:03 - + [000] Schedule 2 has already been cached by job
> 0xD9C1E426A1AAD5498B92EDBEA79A8654
> 2007-05-18 11:10:01 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 2
> 2007-05-18 11:10:01 - + [163] 1 operations applied (0 remaining)
> 2007-05-18 11:12:09 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 3
> 2007-05-18 11:12:09 - + [000] Schedule 3 has already been cached by job
> 0x4CC373CEC320804D9AF67C7704B6F747
> 2007-05-18 11:13:23 - + [000] Schedule 4 has already been cached by job
> 0x6CC98A2943018F488AF45B20E63E1DC7
> 2007-05-18 11:15:00 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 4
> 2007-05-18 11:15:00 - + [163] 1 operations applied (0 remaining)
> 2007-05-18 11:22:46 - + [000] Schedule 5 has already been cached by job
> 0xAE9A0B33E1E4374B9B60F807A7772999
> 2007-05-18 11:24:00 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 5
> 2007-05-18 11:24:00 - + [163] 1 operations applied (0 remaining)
> 2007-05-18 11:32:02 - + [000] Schedule 6 has already been cached by job
> 0x05979EE4A61D87489C664CE2D68B0D24
> 2007-05-18 11:33:00 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 6
> 2007-05-18 11:33:00 - + [163] 1 operations applied (0 remaining)
> 2007-05-18 11:35:23 - + [000] Schedule 7 has already been cached by job
> 0xBAE7D146168A5B4586DBB7333EE1D0C5
> 2007-05-18 11:36:00 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 7
> 2007-05-18 11:36:00 - + [163] 1 operations applied (0 remaining)
> 2007-05-18 11:39:55 - + [000] Schedule 8 has already been cached by job
> 0x877BA9F8E7147E4EA91EB6F2E1E701C0
> 2007-05-18 11:41:00 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 8
> 2007-05-18 11:41:00 - + [163] 1 operations applied (0 remaining)
> 2007-05-18 15:40:07 - + [000] Schedule 9 has already been cached by job
> 0xA5BBF8F9EA07834EA0B475B553911869
> 2007-05-18 15:41:01 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 9
> 2007-05-18 15:41:01 - + [163] 1 operations applied (0 remaining)
> 2007-05-18 15:42:47 - + [000] Schedule 10 has already been cached by job
> 0x13322C18AB3BC5409D40385C02129F54
> 2007-05-18 15:45:01 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 10
> 2007-05-18 15:45:01 - + [163] 1 operations applied (0 remaining)
> 2007-05-18 15:48:17 - + [000] Schedule 11 has already been cached by job
> 0x830F8A65D9A9BC4A914123CF6CB5E8F9
> 2007-05-18 15:50:00 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 11
> 2007-05-18 15:50:00 - + [163] 1 operations applied (0 remaining)
> 2007-05-18 16:02:05 - + [000] Schedule 12 has already been cached by job
> 0x6E49B2772349B84CB65BD39CC3C47810
> 2007-05-18 16:05:01 - + [162] Internal request (from SetJobNextRunDate
> [reason: schedule will not run again]) to deactivate schedule 12
> 2007-05-18 16:05:01 - + [163] 1 operations applied (0 remaining)
> 2007-05-21 09:16:02 - + [000] Schedule 13 has already been cached by job
> 0xEFBDC763EB628A4AA037D27A483ADE7C
> 2007-05-21 09:21:16 - + [000] Schedule 14 has already been cached by job
> 0xB79CC4672770A94492543246E78D049F
> 2007-05-21 09:22:40 - + [000] Schedule 15 has already been cached by job
> 0xA812252789CF72418FA14FEC66C90089
> 2007-05-21 09:31:11 - + [000] Schedule 16 has already been cached by job
> 0xCDDBFEFA899ACE4DBADC96FFC6932279
> 2007-05-21 09:33:05 - + [000] Schedule 17 has already been cached by job
> 0x4010169385C38E478077F9AE67D7E298

Help! - Error in moving data from AS400

I have a process that simply copies data from a table on an AS400 to SQL Server. This process executes fine until it gets to around 44 million rows copied out of 48 million rows in the source table. At this point, the process exits with the following error messages:

The attempt to send a row to SQL Server failed with error code 0x80004005.

The ProcessInput method on component "SQL Server Destination" (40) failed with error code 0xC02020C7.
The identified component returned an error from the ProcessInput method.
The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.

Thread "WorkThread0" has exited with error code 0xC02020C7.

The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.

Thread "SourceThread0" has exited with error code 0xC0047038.

I am using the Microsoft OLEDB Provider for DB2 to access the AS400 and have tried the Table/View and SQL Command access modes with the same result.

Any help will be Greatly Appreciated!

-Mark Redman.

Hi Mark

The error was from your SQL Server Destination rather than from the DB2 source.

Which connection you have at your destination and which provider?

Thanks
Wenyang|||Hi Mark

This is not directly related to your problem, but I am also trying to use the MS OLE DB Provider for DB2 for connecting to an AS400, but I cannot make it work... How are your parameters setup? Could you perhaps post a screenshot?|||I am using the SQL Native Provider as the destination. It is a SQL Server 2005 Release Version server.|||The Parameters I have filled in are:

APPC Mode Name: QPCSUPP
APPC Security Type: Program
Defer Prepare: False
Derive Parameters False
Host CCSID 37
Network Address BKL400 <this would be different for you>
Network Port 446
Network Transport Library TCPIP
Package Collection QSYS2
PC Code Page 1252
Data Source bkl400
Initial Catalog bkl400
I hope this helps!|||The error was from your destination provider. Seems to me it's not related to the source you used in your package. I'm not sure whether you are using MS OLEDB for ODBC, if that's the case, search online using the error code 0x80004005 may bring you to some helpful web sites.

Thanks
Wenyang|||

The destination provider I am using is the Native OLEDB/SQL Native Client (SQLNCLI).

Monday, February 27, 2012

HELP!

17310 :
FRunCM: Process 2816 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
EVENT ID:17055
http://support.microsoft.com/default...b;en-us;814572
"??H" <lemel@.hungnet.idv.tw> wrote in message
news:ez$87qf$EHA.1260@.TK2MSFTNGP12.phx.gbl...
> 17310 :
> FRunCM: Process 2816 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> EVENT ID:17055
> http://support.microsoft.com/default...b;en-us;814572
>
Have you tried following the directions listed in the support document?
What platform are you running on? What version of SQL Server? When did
this happen? Did the Server ever start.
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA

HELP!

17310 :
FRunCM: Process 2816 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
EVENT ID:17055
http://support.microsoft.com/defaul...kb;en-us;814572"??H" <lemel@.hungnet.idv.tw> wrote in message
news:ez$87qf$EHA.1260@.TK2MSFTNGP12.phx.gbl...
> 17310 :
> FRunCM: Process 2816 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> EVENT ID:17055
> http://support.microsoft.com/defaul...kb;en-us;814572
>
Have you tried following the directions listed in the support document?
What platform are you running on? What version of SQL Server? When did
this happen? Did the Server ever start.
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA

HELP!

17310 :
FRunCM: Process 2816 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
EVENT ID:17055
http://support.microsoft.com/default.aspx?scid=kb;en-us;814572"¶Ë¤ß¤H" <lemel@.hungnet.idv.tw> wrote in message
news:ez$87qf$EHA.1260@.TK2MSFTNGP12.phx.gbl...
> 17310 :
> FRunCM: Process 2816 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> EVENT ID:17055
> http://support.microsoft.com/default.aspx?scid=kb;en-us;814572
>
Have you tried following the directions listed in the support document?
What platform are you running on? What version of SQL Server? When did
this happen? Did the Server ever start.
More information would be helpful.
Rick Sawtell
MCT, MCSD, MCDBA