Search for "log files" returned 4688 results.

Search all the documentation for "log files"

  1. Can't log in to Redgate Monitor with Active Directory or OpenID Connect

    If Redgate Monitor is configured to authenticate users with Active Directory or OpenID Connect and you're unable to log in, check that: Yo

    /monitor14/can-t-log-in-to-redgate-monitor-with-active-directory-or-openid-connect-239668901.html

  2. About config files

    You can use a config file: to customize how SQL Source Control works with Git, SVN, TFS and Vault to use a different source control syste

    /soc5/linking-to-source-control/other-source-control-systems/link-to-a-custom-setup/about-config-files

  3. Working with key files for encrypted backups

    SQL Virtual Restore works with encrypted backup files created by SQL HyperBac http://www.red-gate.com/products/SQL_HyperBac/index.htm and

    /rp/sql-virtual-restore/worked-examples-for-sql-virtual-restore/working-with-key-files-for-encrypted-backups

  4. Release Notes

    1.0.69029 Released on 2024-07-04 Warnings - Breaking Change: CLI does not return "podName" field as part of Data Container details - Break

    /redgate-clone/administration/release-notes

  5. Using the command line

    be redirected to a file by one of several methods: Use the /out switch to specify the file to which you want output directed: SQLDataGene

    /sdg2/using-the-command-line

  6. Managing security

    as described here https://documentation.red-gate.com/display/SM13/Enabling+Application+Initialization+in+IIS. Log files The Redgate Monit

    /monitor14/managing-security-239667413.html

  7. Specifying file paths

    SQL Backup often requires you to specify a file path or name, as, for example, in the Back Up wizard: SpecifyingFilePaths1.gif You can ty

    /sbu7/troubleshooting/specifying-file-paths

  8. Activating your license

    https://www.red-gate.com/account/. Then you can run the auth command making sure to agree to the EULA by passing the --agree-to-eula flag

    /testdatamanager/getting-started/licensing/activating-your-license

  9. Restoring backups - destination database

    . Filegroups and files The data and log files (and any full text catalogs or filestream data) will be restored to the default SQL Server d

    /sbu7/restoring/restoring-backups/restoring-backups-destination-database

  10. SQL Server error 4214 - BACKUP LOG cannot be performed because there is no current database backup

    When attempting a log backup of a database, the following error may occur: BACKUP LOG cannot be performed because there is no current dat

    /sbu6/errors-and-warnings/sql-server-errors/sql-server-error-4214-backup-log-cannot-be-performed-because-there-is-no-current-database-backup

  11. Specifying file paths

    SQL Backup often requires you to specify a file path or name, as, for example, in the Back Up wizard: SpecifyingFilePaths1.gif You can ty

    /sbu9/troubleshooting/specifying-file-paths

  12. Creating backups - select the backup type and databases

    transactions. Truncating the transaction log does not reduce the size of the log file on disk; for this, refer to the SQL Server document

    /sbu6/backing-up/creating-backups/creating-backups-select-the-backup-type-and-databases

  13. System error 32 - The process cannot access the file because it is being used by another process

    the backup to. If you used tags to generate the file name, you can find the file name in the Activity Log: In the SQL Backup Pro graphica

    /display/SBU8/System+error+32+-+The+process+cannot+access+the+file+because+it+is+being+used+by+another+process

  14. Command line switches

    :<level> Alias: /log Creates a log file with a specified minimum log level. The default is none. Log files collect information about the a

    /dco2/using-the-command-line/command-line-switches

  15. Restoring backups - destination database

    . Filegroups and files The data and log files (and any full text catalogs or filestream data) will be restored to the default SQL Server d

    /sbu9/restoring/restoring-backups/restoring-backups-destination-database

  16. SQL Scripts Manager 2.0 release notes

    to log files corrected Now uses new installer user interface. Version 2.0.0, February 9th, 2017 Features * New window appearance * New pr

    /ssm2/release-notes-and-other-versions/sql-scripts-manager-2-0-release-notes

  17. Command line switches

    : /log Creates a log file with a specified minimum log level. The default is none. Log files collect information about the application whi

    /sco4/using-the-command-line/command-line-switches

  18. SMB File Share

    to specify the user's domain if needed. image2022-1-12_15-45-18.png Verifying SMB file share connection parameters You can verify the con

    /redgate-clone/administration/admin-console/configuration/backup-storage/smb-file-share

  19. Command line switches

    :<level> Alias: /log Creates a log file with a specified minimum log level. The default is none. Log files collect information about the a

    /dco4/using-the-command-line/command-line-switches

  20. Scheduling backups - select the backup type and database

    then be reused by new transactions. Truncating the transaction log does not reduce the size of the log file on disk; for this, refer to t

    /sbu6/backing-up/scheduling-backup-jobs/scheduling-backups-select-the-backup-type-and-database

  21. Privacy Information

    Log files are an important tool for troubleshooting, and ideally should be included in all support cases. These log files are collected i

    /ref11/getting-started/privacy-information

  22. Command line switches

    direct connection option in the Schema Compare Application Options. /loglevel:<level> Alias: /log Creates a log file with a specified min

    /sco3/using-the-command-line/command-line-switches

  23. Can't log in to SQL Monitor with Active Directory

    If SQL Monitor is configured to authenticate users with Active Directory and you're unable to log in, check that: you've typed your usern

    /sm7/troubleshooting/can-t-log-in-to-sql-monitor-with-active-directory

  24. Privacy Information

    Log files are an important tool for troubleshooting, and ideally should be included in all support cases. These log files are collected i

    /ref10/getting-started/privacy-information

  25. The RESTORE command

    . For information on restoring multiple log backups in one RESTORE command, see the FROM DISK argument below. FILE = 'logical_file_name' |

    /sbu6/scripting-sql-backup/the-restore-command


Didn't find what you were looking for?