Search for "log files" returned 4688 results.

Search all the documentation for "log files"

  1. Log shipping - network share

    the processed transaction log backup files are moved to on completion (see step 4). If you typed the network share name, click Test to ch

    /sbu7/log-shipping/configuring-log-shipping/log-shipping-network-share

  2. Configuring log shipping

    backups. Step 2: Specify the locations and file names for the transaction log backups, configure settings for managing existing backup fi

    /sbu9/log-shipping/configuring-log-shipping

  3. Finding database files

    of the Schedule Restore Jobs wizard) you can specify where each data and log file will be restored to by selecting Individual files to sp

    /sbu7/restoring/finding-database-files

  4. Scheduling restores - specify the file locations

    : All files to default locations Data and log files to specified locations Individual files to specified locations If you have launched th

    /sbu10/restoring/scheduling-restore-jobs/scheduling-restores-specify-the-file-locations

  5. Configuring log shipping

    backups. Step 2: Specify the locations and file names for the transaction log backups, configure settings for managing existing backup fi

    /sbu10/log-shipping/configuring-log-shipping

  6. Log shipping - specify source and destination database

    Create a new database to restore to. Then type a name for the new database and specify the folders in which you want the database's data

    /sbu7/log-shipping/configuring-log-shipping/log-shipping-specify-source-and-destination-database

  7. Finding database files

    of the Schedule Restore Jobs wizard) you can specify where each data and log file will be restored to by selecting Individual files to sp

    /sbu9/restoring/finding-database-files

  8. Logging

    Redgate Change Automation command line and Docker image When using the command line or docker image, the log level desired can be specifi

    /rca3/troubleshooting/logging

  9. Log shipping - specify source and destination database

    Create a new database to restore to. Then type a name for the new database and specify the folders in which you want the database's data

    /sbu9/log-shipping/configuring-log-shipping/log-shipping-specify-source-and-destination-database

  10. Logging

    Redgate Change Automation command line and Docker image When using the command line or docker image, the log level desired can be specifi

    /rca4/troubleshooting/logging

  11. Finding database files

    of the Schedule Restore Jobs wizard) you can specify where each data and log file will be restored to by selecting Individual files to sp

    /sbu10/restoring/finding-database-files

  12. Log shipping - network share

    servers cannot be browsed. The network share must not be the same location as the folder the processed transaction log backup files are m

    /sbu9/log-shipping/configuring-log-shipping/log-shipping-network-share

  13. Log shipping - specify source and destination database

    Create a new database to restore to. Then type a name for the new database and specify the folders in which you want the database's data

    /sbu10/log-shipping/configuring-log-shipping/log-shipping-specify-source-and-destination-database

  14. Log shipping - network share

    servers cannot be browsed. The network share must not be the same location as the folder the processed transaction log backup files are m

    /sbu10/log-shipping/configuring-log-shipping/log-shipping-network-share

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

    to. If you used tags to generate the file name, you can find the file name in the Activity Log: In the SQL Backup graphical user interfac

    /sbu6/errors-and-warnings/other-errors/system-error-32-the-process-cannot-access-the-file-because-it-is-being-used-by-another-process

  16. SQL Log Rescue

    This product is not available to download, and is no longer supported. SQL Log Rescue only works with SQL Server 2000. For help, visit th

    /rp/sql-log-rescue

  17. "Too many open files"

    When creating containers, we have observed errors where a container has complained that there are too many open files Typical error messag

    /redgate-clone/administration/troubleshooting/too-many-open-files

  18. Data Generation command-line reference

    Minimum Log Level Purpose File Default location varies per OS: Windows : C:\ProgramData\Red Gate\Logs\TDM\DataGenerator Linux/Mac OSX (ce

    /testdatamanager/command-line-interface-cli/data-generation/data-generation-command-line-reference

  19. 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

    /sbu7/errors-and-warnings/other-errors/system-error-32-the-process-cannot-access-the-file-because-it-is-being-used-by-another-process

  20. 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

    /sbu9/errors-and-warnings/other-errors/system-error-32-the-process-cannot-access-the-file-because-it-is-being-used-by-another-process

  21. 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

    /sbu10/errors-and-warnings/other-errors/system-error-32-the-process-cannot-access-the-file-because-it-is-being-used-by-another-process

  22. Extracting and installing from the .msi file

    Installing from the .msi file

    /in/extracting-and-installing-from-the-msi-file

  23. File location tags

    will use the following values: FULL for full backups DIFF for differential backups LOG for transaction log backups FILE for filegroup or

    /sbu6/settings-and-options/file-location-tags

  24. Creating backups - file settings

    on the C: drive on ServerA, not on the local machine. If you specify a network share as the backup file location, the SQL Backup Agent se

    /sbu6/backing-up/creating-backups/creating-backups-file-settings

  25. Scheduling backups - file settings

    , click Test to check that the "log on" user for the SQL Backup Agent service on the source SQL Server has permission to create files on t

    /sbu6/backing-up/scheduling-backup-jobs/scheduling-backups-file-settings


Didn't find what you were looking for?