Search for "log files" returned 4688 results.

Search all the documentation for "log files"

  1. Creating backups

    of backup, and the database that you want to back up. Step 3: Specify the backup file locations (including any copies to hosted storage o

    /display/SBU8/Creating+backups

  2. "An existing connection was forcibly closed by the remote host" error

    When the SQL Clone Agent installation fails, you might see an error among Windows Application Event Logs, which is similar to below one:

    /pages/viewpage.action?pageId=42542232

  3. Installing SQL Clone

    the server. The server's web app uses Windows authentication, so log in with your Windows credentials. The URL will be of the form: http:

    /display/CLONE0/Installing+SQL+Clone

  4. Email settings

    or restore operation: In the graphical user interface, you specify the email addresses in the back up, scheduled backup, restore, schedul

    /display/SBU8/Email+settings

  5. Limitations

    Clone The source of an image cannot: Have a total combined file size (mdf+ldf) of over 2TB. Contain filestream or memory-optimized tables

    /display/CLONE1/Limitations

  6. "Pad block corrupted" after changing the user that SQL Clone Server runs as

    machine with the old account details Add-Type -Path "C:\Program Files\Red Gate\SQL Clone Beta\RedGate.SqlClone.Credentials.dll" $credenti

    /pages/viewpage.action?pageId=42542246

  7. Uninstalling SQL Clone

    , and deleting the folder "localappdata%\Red Gate\SQL Clone\clones" Remove all images within the application, and deleting any files left

    /display/CLONE1/Uninstalling+SQL+Clone

  8. Uninstalling SQL Clone

    , and deleting the folder "localappdata%\Red Gate\SQL Clone\clones" Remove all images within the application, and deleting any files left

    /display/CLONE0/Uninstalling+SQL+Clone

  9. AlwaysOn Availability Groups

    . For additional file name options see File location tags For more information about the types of backup allowed on Availability Group pri

    /display/SBU8/AlwaysOn+Availability+Groups

  10. SQL Backup Pro 7.0 release notes

    April 24th 2012 New features Schedule a recurring restore from a full backup or set of backups that does not exist yet by specifying a fo

    /display/SBU8/SQL+Backup+Pro+7.0+release+notes

  11. Upgrading the server components

    created using version 5, 6 or 7 are supported in version 8, and will work in the same way. SQL Backup 6 introduced changes to the SQL Bac

    /display/SBU8/Upgrading+the+server+components

  12. Object level recovery

    ) enables you to extract individual database objects from a backup file, and recover them to a database of your choice. By recovering only

    /display/SBU8/Object+level+recovery

  13. New-SqlCloneImage

    <RedGate.SqlClone.Client.Api.Objects.BackupLocationResource> Specifies location of the backup files. The Get-SqlCloneBackupLocation cmdle

    /display/CLONE0/New-SqlCloneImage

  14. Remove-InstantCloneClone

    database, backing-file and directory. The original snapshot is unaffacted. This should always be used to remove a clone - do not directly

    /display/IC0/Remove-InstantCloneClone

  15. Activating

    Activation Response. When the activation response is displayed under Step 2, copy all of it. Alternatively you can save the activation re

    /display/SBU8/Activating

  16. Error - Cannot load the DLL xp_sqlbackup.dll, or one of the DLLs it references

    of the DLLs it references. Reason: 1114 (A dynamic link library (DLL) initialization routine failed.). This error occurs when the old xp_

    /display/SBU8/Error+-++Cannot+load+the+DLL+xp_sqlbackup.dll%2C+or+one+of+the+DLLs+it+references

  17. SQL Backup 3.1 release notes

    April, 2005 New features Added new keyword MAILTO_ONERROR to send email notification only on errors. Fixed MOVETO command which was incor

    /display/SBU8/SQL+Backup+3.1+release+notes

  18. Scheduling restores - create restore schedule

    Scheduling restore jobs > Select destination server and backups to restore > Select destination database > Specify file locations > Speci

    /display/SBU8/Scheduling+restores+-+create+restore+schedule

  19. Error - The database disk image is malformed

    On starting SQL Backup Pro, the following error may occur: The database disk image is malformed. This is caused by a corruption of the ac

    /display/SBU8/Error+-+The+database+disk+image+is+malformed

  20. SQL Backup Pro 7.7 release notes

    SQB files to native SQL backups Fixed spurious 976 error message when backing up an AlwaysOn secondary

    /display/SBU8/SQL+Backup+Pro+7.7+release+notes

  21. Creating backups - specify SQL Server

    Creating backups > Specify SQL Server > Select backup type and database > File settings > Processing and encryption settings > Verificati

    /display/SBU8/Creating+backups+-+specify+SQL+Server

  22. Scheduling backups - specify SQL Server

    Scheduling backup jobs > Specify SQL Server > Select backup type and database > Create backup schedules > File settings > Processing and

    /display/SBU8/Scheduling+backups+-+specify+SQL+Server

  23. New-InstantCloneClone

    Server database backed by a virtual differencing-disk, which references the snapshot file. A clone takes a few seconds to create and occu

    /display/IC0/New-InstantCloneClone

  24. Save-InstantCloneSharedSnapshot

    next to it in a json file. Anyone who sets his SharedSnapshotFolder to the value of your SharedSnapshotsFolder will be able to clone snap

    /display/IC0/Save-InstantCloneSharedSnapshot

  25. Scheduling backups - review summary

    Scheduling backup jobs > Specify SQL Server > Select backup type and database > Create backup schedules > File settings > Processing and

    /display/SBU8/Scheduling+backups+-+review+summary


Didn't find what you were looking for?