Errors: Recovery Mode: Full and Simple

Hi
I have a production database that is set to Recovery Mode: Simple.
However I decided to change this to Recovery Mode: Full. A scheduled
backup of the database was then run that night.
Unfortunately I was then told to reset the Recovery Mode back to
Simple as not enough testing had been done. So I did this.
The next day we received error messages that "The log file for the
database is full. Back up the transaction log for the database to free
up some log space."
The production db was then unusable for the apps. As a quick solution
I changed the recovery mode back to full and backed up the transaction
log ( because you cannot backup the transaction log in simple mode).
This made the database operational again.
I then changed the Recovery mode back to simple for the next night's
scheduled backup.
So..... the nightly backup goes ahead with the db still in simple
mode.
HOWEVER we are still getting the log full error messages and I keep
having to change to recovery mode full and backup the transaction log
and then swap back again to simple mode.
I realise that if the database is set to Recovery Mode: Full then the
transaction log must be backed up regularly. But we are no longer
running in Full mode and I don’t not want to run in full mode
and the transaction logs never used to get full in Simple mode and we
never had to back them up.
I would just like things to get back to how they were - the database
running in simple mode and nightly backups taking place. Then those
nightly backups - which are in one file - restoring ok on a test
machine.
Has anyone got any ideas?
Many thanks!
Thiko!Thiko
How large is your transaction log? Even with simple
recovery model the transaction log is still used.
It is just cleared when transactions complete. If you have
some/one very large transaction running on the system you
may still fill up the transaction log even in simple
recovery mode.
If your transaction log is quite small, you may solve your
problem by increasing it.
Regards
Johnsql

Errors Deploying an SSIS package

Hi All,

I hope someone can help becuase this problem is issue us several headaches.

We are currently trying to deploy an SSIS package to a production server. The deployment goes fine, the package runs ok when executed manually. The issues start when we try and execute it under the SQL agent.

Having gone back to the drawing board and spent much of the day reading various articles and applying the various options (especially those within the MS KB article 918760), we are still no closer to a resolution.

The SSIS package was created under an Administrator, and the SQL agent runs under a different Domain Admin account.

When we set up the Schedule to read from SQL Server or the SSIS Store the standard "Executed as user: DOMAIN\USERNAME. The package execution failed. The step failed" in the history.

We tried to create the package as a file access and now get "Package could not be found" even though you can browse to i in the schedule list. The Domain account as full access to the folder where the package resides.

Has anyone else come across this issue, or have a workable solution?

Many TIA.

But does the SQL Server service account have access to everything? Not the Agent user, but the SQL Server service account?|||

Phil,

Thanks for the assist, adding access rights the SQL Server Account ot the database helped, and it seems to have fixed one issue in that it now adds the /Decrypt item to the when saved as EncryptWithPassword, and stores the information.

We have decided to run the package from the SQL server rather than a file, However we still get the same permission error when running the job in SQL agent.

Any more ideas?

|||

This KB article maqy help

http://support.microsoft.com/kb/918760

|||

Thanks for the Pointer Rafael, but we have already tried to apply the workrounds mentioned in the articles with no joy.

I'm coming to the conclusion that MS have really over done the security model for SSIS, I still pondering what the point of of the EncryptWithUserKey setting is as most jobs will generally need to be scheduled and run under the SQLAgent account.

Errors

Folks,
This might not be SQL Server related, but nevertheless, it brought our production sql server to a halt. Does anyone know what these entries mean?
System log:-
Event Type:Error
Event Source:Perflib
Event Category:None
Event ID:1015
Date:7/20/2004
Time:4:24:56 AM
User:N/A
Computer:TOROONDC975
Description:
The timeout waiting for the performance data collection function
"PerfOS" in the "C:\WINNT\system32\perfos.dll" Library to finish
has expired. There may be a problem with this extensible counter
or the service it is collecting data from or the system may have
been very busy when this call was attempted.
Application log:-
Event Type:Information
Event Source:Application Popup
Event Category:None
Event ID:26
Date:7/20/2004
Time:6:45:21 PM
User:N/A
Computer:TOROONDC975
Description:
Application popup: cmd.exe - Application Error : The application
failed to initialize properly (0xc0000142). Click on OK to terminate
the application.
Any guidance is much appreciated.
Karthik.
PS: We are running
SQL 2K Enterprise Edition SP3
Windows 2K Advanced Server
What do the sql error log say? That error message doenst seem like an event
that could bring a machine down.
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.
|||Well, it occured on a server that happened to be our production SQL Server. Not really a SQL Server error. Anyways, the reason this brought our server down was because there was about 150 CMD.EXE running when we looked at the unresponsive server in the mo
rning. And we found the errors I have attached in the event viewer.
Thanks.
"Vikram Jayaram [MS]" wrote:

> What do the sql error log say? That error message doenst seem like an event
> that could bring a machine down.
> 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.
>
>

Errors

Folks,
This might not be SQL Server related, but nevertheless, it brought our produ
ction sql server to a halt. Does anyone know what these entries mean?
System log:-
Event Type: Error
Event Source: Perflib
Event Category: None
Event ID: 1015
Date: 7/20/2004
Time: 4:24:56 AM
User: N/A
Computer: TOROONDC975
Description:
The timeout waiting for the performance data collection function
"PerfOS" in the "C:\WINNT\system32\perfos.dll" Library to finish
has expired. There may be a problem with this extensible counter
or the service it is collecting data from or the system may have
been very busy when this call was attempted.
Application log:-
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 7/20/2004
Time: 6:45:21 PM
User: N/A
Computer: TOROONDC975
Description:
Application popup: cmd.exe - Application Error : The application
failed to initialize properly (0xc0000142). Click on OK to terminate
the application.
Any guidance is much appreciated.
Karthik.
PS: We are running
SQL 2K Enterprise Edition SP3
Windows 2K Advanced ServerWhat do the sql error log say? That error message doenst seem like an event
that could bring a machine down.
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.|||Well, it occured on a server that happened to be our production SQL Server.
Not really a SQL Server error. Anyways, the reason this brought our server d
own was because there was about 150 CMD.EXE running when we looked at the un
responsive server in the mo
rning. And we found the errors I have attached in the event viewer.
Thanks.
"Vikram Jayaram [MS]" wrote:

> What do the sql error log say? That error message doenst seem like an even
t
> that could bring a machine down.
> 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.
>
>