In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
Thanks
SalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default...b;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB)42147483647470470
min server memory (MB)02147483647256256
set working set size0111
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/default...b;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you should
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>
Showing posts with label size. Show all posts
Showing posts with label size. Show all posts
Monday, March 26, 2012
Error 823, Severity: 24
In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
Error 823, Severity: 24
In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/defaul...kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB) 4 2147483647 470 470
min server memory (MB) 0 2147483647 256 256
set working set size 0 1 1 1
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/defaul...kb;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you shou
ld
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>sql
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/defaul...kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB) 4 2147483647 470 470
min server memory (MB) 0 2147483647 256 256
set working set size 0 1 1 1
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/defaul...kb;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you shou
ld
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>sql
Wednesday, March 7, 2012
Error 3726
Hi all,
I am encountering a similar problem to Tom's. I am trying to do a merge repl
with sql 2005 on both ends. I have a decent size db of 1.2 gb. I had the
replication working ok before. But due to some updates I had to apply to a
program , I had to break replication. When get the snapshot made and the try
to sync I get: "The schema script "xxx.sch" could not be propagated to the
subscriber." Upon further digging in the logs I see that I too am getting the
3726 saying "Could not drop object 'dbo.xxx' because it is referenced by a
FOREIGN KEY constraint."
I remember getting this error before and I had re-created the publication a
few times and was somehow able to get it to work. I am not able to get it to
work now. Any insight would be greatly appreciated.
Thanks
"Tom" wrote:
> I am doing a snapshot replication between SQL server 200 and SQLexpress.
> When I sync I get the following error:
> Could not drop object 'Events' because it is referenced by a FOREIGN KEY
> constraint..
> I went into the "Events" table and removed all the foreign keys, but the
> error persists. Also, the database is being used for simple queries and no
> data input.
> Any insight would be appreciated.
> Tom
>
>
>
I answered this in your other post, but I believe Tom's case was different -
certainly the description is distinct in that he mentions he removed the FK
constraints. It might be that he removed them on the publisher! In this case
he does has the same issue and will need to drop them on the subscriber
before the table is dropped eg via a pre-snapshot script.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
I am encountering a similar problem to Tom's. I am trying to do a merge repl
with sql 2005 on both ends. I have a decent size db of 1.2 gb. I had the
replication working ok before. But due to some updates I had to apply to a
program , I had to break replication. When get the snapshot made and the try
to sync I get: "The schema script "xxx.sch" could not be propagated to the
subscriber." Upon further digging in the logs I see that I too am getting the
3726 saying "Could not drop object 'dbo.xxx' because it is referenced by a
FOREIGN KEY constraint."
I remember getting this error before and I had re-created the publication a
few times and was somehow able to get it to work. I am not able to get it to
work now. Any insight would be greatly appreciated.
Thanks
"Tom" wrote:
> I am doing a snapshot replication between SQL server 200 and SQLexpress.
> When I sync I get the following error:
> Could not drop object 'Events' because it is referenced by a FOREIGN KEY
> constraint..
> I went into the "Events" table and removed all the foreign keys, but the
> error persists. Also, the database is being used for simple queries and no
> data input.
> Any insight would be appreciated.
> Tom
>
>
>
I answered this in your other post, but I believe Tom's case was different -
certainly the description is distinct in that he mentions he removed the FK
constraints. It might be that he removed them on the publisher! In this case
he does has the same issue and will need to drop them on the subscriber
before the table is dropped eg via a pre-snapshot script.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Error 3624 - SQL-DMO(ODBC SQLState:HY000)
My ProjectServer database suddenly became (suspect), the log file increased
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================
(After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
Johnny
Hi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/de...r_da2_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:
> My ProjectServer database suddenly became (suspect), the log file increased
> like balloon 49.9GB, I don't know exactly what was the size before. The mdf
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================
> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================
(After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
Johnny
Hi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/de...r_da2_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/inf...suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:
> My ProjectServer database suddenly became (suspect), the log file increased
> like balloon 49.9GB, I don't know exactly what was the size before. The mdf
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================
> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>
Error 3624 - SQL-DMO(ODBC SQLState:HY000)
My ProjectServer database suddenly became (suspect), the log file increased
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================
(After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
JohnnyHi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/d...r />
_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:
> My ProjectServer database suddenly became (suspect), the log file increase
d
> like balloon 49.9GB, I don't know exactly what was the size before. The md
f
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================
> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================
(After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
JohnnyHi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/d...r />
_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:
> My ProjectServer database suddenly became (suspect), the log file increase
d
> like balloon 49.9GB, I don't know exactly what was the size before. The md
f
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================
> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>
Error 3624 - SQL-DMO(ODBC SQLState:HY000)
My ProjectServer database suddenly became (suspect), the log file increased
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================ (After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
JohnnyHi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:
> My ProjectServer database suddenly became (suspect), the log file increased
> like balloon 49.9GB, I don't know exactly what was the size before. The mdf
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>
like balloon 49.9GB, I don't know exactly what was the size before. The mdf
file is about 640MB. To get the situation worst, the backup wasn't good,
tried to copy the file to a different folder, so a detached the DB to copy
both of them.
Later I tried to attach the DB back and it gave me this error message.
(SQL2000 SP3)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:321
Expression: m_len !=0
SPID: 54
Process ID: 1832"
================================ (After applying SP4)
"Microsoft SQL-DMO(ODBC SQLState:HY000)
345 transactions rolled forward in database "ProjectServer"(9).
LocationL scanrid.cpp:359
Expression: m_len !=0
SPID: 54
Process ID: 1896"
Where do I start, is there any repai utility to fix this problem?
I am not a database or SQL expert, any help will be very appreciated.
I can't attach the database back anymore.
JohnnyHi Johnny
You have probably run out of space where the log file is located. You can
check for open transactions in the database using DBCC OPENTRAN, but there
should not be any as you have detached the database. Use BACKUP LOG to free
up the log file and DBCC SHRINKFILE to shrink it. You may want to see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp
Once a reasonable size you should change the growth amount to be a fixed
value and not a percentage.
To change the database so it is not suspect see
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
You should also implement a backup schedule or maintenance plan that will
backup the database and also backup the logs.
John
"Johnny" wrote:
> My ProjectServer database suddenly became (suspect), the log file increased
> like balloon 49.9GB, I don't know exactly what was the size before. The mdf
> file is about 640MB. To get the situation worst, the backup wasn't good,
> tried to copy the file to a different folder, so a detached the DB to copy
> both of them.
> Later I tried to attach the DB back and it gave me this error message.
> (SQL2000 SP3)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:321
> Expression: m_len !=0
> SPID: 54
> Process ID: 1832"
> ================================> (After applying SP4)
> "Microsoft SQL-DMO(ODBC SQLState:HY000)
> 345 transactions rolled forward in database "ProjectServer"(9).
> LocationL scanrid.cpp:359
> Expression: m_len !=0
> SPID: 54
> Process ID: 1896"
> Where do I start, is there any repai utility to fix this problem?
> I am not a database or SQL expert, any help will be very appreciated.
> I can't attach the database back anymore.
> Johnny
>
>
Subscribe to:
Posts (Atom)