I found this error on my sql server:
The log file for database dbname is full. Back up the transaction log for
the database to free up some log space.
Then I run the backup program for transaction log, now my sql can work fine.
But the .LDF file still very big. Can I decrease this file's size?
Such as defrag or compress'Dear all:
I've check the file again and find out that the .LDF file was smaller then
before!
From 3G to 1M !!! I think its because the backup.
But why not change size immedialy?
Thank you very much!
"LetsCount" <come2@.ms1.pchome.com.tw> ¦b¶l¥ó
news:u82uPwQxDHA.2356@.TK2MSFTNGP12.phx.gbl ¤¤¼¶¼g...
> I found this error on my sql server:
> The log file for database dbname is full. Back up the transaction log for
> the database to free up some log space.
> Then I run the backup program for transaction log, now my sql can work
fine.
> But the .LDF file still very big. Can I decrease this file's size?
> Such as defrag or compress'
>|||Check out below KB articles:
INF: How to Shrink the SQL Server 7.0 Transaction Log
http://support.microsoft.com/default.aspx?scid=kb;en-us;256650
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/default.aspx?scid=kb;en-us;272318
Log File Grows too big
http://www.support.microsoft.com/?id=317375
Log file filling up
http://www.support.microsoft.com/?id=110139
Considerations for Autogrow and AutoShrink
http://www.support.microsoft.com/?id=315512
http://www.mssqlserver.com/faq/logs-shrinklog.asp
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"LetsCount" <come2@.ms1.pchome.com.tw> wrote in message news:u82uPwQxDHA.2356@.TK2MSFTNGP12.phx.gbl...
> I found this error on my sql server:
> The log file for database dbname is full. Back up the transaction log for
> the database to free up some log space.
> Then I run the backup program for transaction log, now my sql can work fine.
> But the .LDF file still very big. Can I decrease this file's size?
> Such as defrag or compress'
>
Showing posts with label occur. Show all posts
Showing posts with label occur. Show all posts
Tuesday, March 27, 2012
Thursday, March 22, 2012
Error 8162
We get an Error 8162 when one of our SQR programs attempt
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."
Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."
Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Error 8162
We get an Error 8162 when one of our SQR programs attempt
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Error 8162
We get an Error 8162 when one of our SQR programs attempt
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql
to insert records into a table. The error is irratic
since it does not always occur. We have been unable to
determine exactly what this error means or what may be
causing it. The full error message we get is listed below:
"(SQR 5528) ODBC SQL dbexec: SQLExecute error 8162 in
cursor 18: [MICROSOFT] [ODBD SQL Server Driver] [SQL
Server] Formal parameter '@.P21' was defined as OUTPUT but
the actual parameter not declared OUTPUT."Looks like a mismatch in procedure parameters. Have you tried dropping and
recerating the stored proc and then running it?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql
Subscribe to:
Posts (Atom)