Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:../libapi/stats.c
Line:79
In Fcn.:stats_increment
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:INSERT INTO stats (stat_date, hits, searches, assists, email_assists, smarts, sessions, ans_viewed, interface_id) VALUES ('2010-09-07 00:00:00', 0, 0, 0, 0, 0, 1, 0, 1)
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:../libapi/stats.c
Line:79
In Fcn.:stats_increment
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:INSERT INTO stats (stat_date, hits, searches, assists, email_assists, smarts, sessions, ans_viewed, interface_id) VALUES ('2010-09-07 00:00:00', 1, 0, 0, 0, 0, 0, 1, 1)
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:../libapi/stats.c
Line:189
In Fcn.:stats_update_faq
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:INSERT INTO incident_stats (ref_no, faq_date, faq_hits, interface_id) VALUES ('080128-000054', '2010-09-07 00:00:00', 1, 1)
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:610
In Fcn.:sql_exec_direct
Called Fcn.:SQLExecDirect() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

SQL Error SQL Error
File:solved.c
Line:68
In Fcn.:solved_increment
SQL Fcn.:sql_exec_direct() returned -1
SQL Stmt.:UPDATE incidents SET solved_count = solved_count + 2, access_time = '2010-09-07 11:30:32' WHERE ref_no = '080128-000054'
SQL Error:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Internal Error Internal Error
File:../libdbapi/odbc2.c
Line:573
In Fcn.:sql_execute
Called Fcn.:SQLExecute() returned -1
Description:42000: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'MSI_SupportKB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases

Answer
 
Maximizer > Support > Knowledge Base Search New - Searching Tips Disclaimer
 Answers 
   
  Help  
Search Results
Related Answers
Product

   
Category

     
Search Text (optional) Search Tips? 
   
Search by      Sort by

Powered by RightNow Web
  Reference #  
080128-000054
  Product  
Maximizer
  All Articles
  Category  
How-To
  Administrator
  Date Updated  
11/03/2009 10:46 AM

 Print  Print Answer 		  
  Setting Up an Automated Backup with Microsoft SQL Express 2005
  Question
 

Setting Up an Automated Backup - Maximizer CRM 10.x Group Edition and Maximizer CRM 10 Entrepreneur Edition

Problem

Maximizer CRM 10.x Group Edition uses Microsoft SQL Server 2005 Express edition as its database engine. The SQL Agent, which is used to facilitate automated backups, is only included in higher editions of Microsoft SQL Server. It is still possible to facilitate an automated backup by running a SQL script in the Windows Task Scheduler.
  Answer
 

Solution

The instructions below must be applied on Maximizer application server.

  1. In a text editor, create a file called SqlBackup.sql, and add the following line:

    2. BACKUP DATABASE [database name] TO DISK = [backup name] WITH INIT

    where [database name] is the name of the Maximizer CQL database and [backup name] is the filename and location of your backup file. See the example below:

    BACKUP DATABASE EsconaTutorial TO DISK = 'D:\Escona.bak' WITH INIT.

  2. In a text editor, create a file called SqlBackup.bat, and add the following line:

    3. Sqlcmd -S [sql server name] -U MASTER -P [sql user password] -i [sql script name]

    Where [sql server name] is the name of your SQL Server, [sql user password] is the password of the MASTER user, and [sql script name] is the name and path of the file you created in step 1. See example below:

    Sqlcmd -S MYSQLSERVER\MAXIMIZER -U MASTER -P CONTROL -i C:\SqlBackup.sql

  3. Add the Scheduled task.
    1. Go to Control Panel > Scheduled Tasks
    2. Double-click Add Scheduled Task.
    3. Click the Next button.
    4. Click the browse button. Browse to the SqlBackup.bat file you created, select the file and click open.
    5. Choose how often you would like the backup to occur. For example, choose Daily and click Next.
    6. Select the time you want the backup to start. For example, select 11:00 PM and click Next.
    7. In the Enter the user name field, enter [Machine Name]\Administrator, specify the Administrator’s password, and click Next. [Machine Name] is the name of the Maximizer application server.
    8. Click Finish to schedule the backup and close the Scheduled Task Wizard.

Using the above example, a backup of your Maximizer database will occur at 11:00 PM on a daily basis.

This is a simple example and the process will accomplish an automated backup. If you require additional functionality, see the Transact SQL documentation for details on adding functionality to the SQL script.

Applicability

  • Maximizer CRM 10.x Group Edition
  • Maximizer CRM 10 Entrepreneur Edition






At 11/03/2009 10:04 AM we wrote - updated script
 
  How well did this answer your question?
 
100% 0%   
Back
  Back to Search Results