The log shipping restore job restores a corrupted transaction log backup to a secondary database

Dear Sir,
I have primary sql instances in cluster node and it is configured with log shipping for DR system.
The instance fails over before the log shipping backup job finishes. Therefore, a corrupted transaction log backup is generated.how to handle the logshipping without break and how to know this transaction back is damaged.
Cheers,

Dear Sir,
I have primary sql instances in cluster node and it is configured with log shipping for DR system.
The instance fails over before the log shipping backup job finishes. Therefore, a corrupted transaction log backup is generated.how to handle the logshipping without break and how to know this transaction back is damaged.
Cheers,
Well when failover happens SQL Server is stopped and restarted on other node. So when SQL Server is stopped and it is doing Log backup the backup operation would stop and there would be no trn files . The backup operation wont complete and hence no backup
information would be stored in SQL Server MSDB and no .trn file would be generated.
You can run restore verifyonly on .trn file to see whether it is damaged or not. Logshipping is quite flexible even if previous log backup did not complete the next wont be affected because SQL Server has no information about whether backup completed
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Similar Messages

  • In the context of restoring a drive from a backup, i copied /etc/sudoers from my backup. Now it does not work due to the permissions not being correct (even though it was copied via sudo cp -rp)

    In the context of restoring a drive from a backup, i copied /etc/sudoers from my backup. Now it does not work due to the permissions not being correct (even though it was copied via sudo cp -rp)

    Most likely you have Office 2004 which are PPC-only applications and will not work in Lion. Upgrade to Office 2011. Other alternatives are:
    Apple's iWork suite (Pages, Numbers, and Keynote.)
    Open Office (Office 2007-like suite compatible with OS X.)
    NeoOffice (similar to Open Office.)
    LibreOffice (a new direction for the Open Office suite.)

  • Can we reduce the size of the disk having the Log files for a Dag Database

    There is an issue with disk space filling up for 4 databases part of the same DAG, each having 1 non lagged passive copy.
    The Disks containing the log files are from the VSphere Storage. The Disk size was temporarily expanded to avoid any outages.
    There is a full backup running currently, which is expected to clear the transaction logs on completion and that should be reducing the disk space utilized.
    The storage guys want to know whether they can reclaim the temporarily expanded disk size. i.e reduce the disk space from the storage containing Log Files without affecting anything.
    I couldn't find any documentation on this specific requirement, and want to confirm

    There is an issue with disk space filling up for 4 databases part of the same DAG, each having 1 non lagged passive copy.
    The Disks containing the log files are from the VSphere Storage. The Disk size was temporarily expanded to avoid any outages.
    There is a full backup running currently, which is expected to clear the transaction logs on completion and that should be reducing the disk space utilized.
    The storage guys want to know whether they can reclaim the temporarily expanded disk size. i.e reduce the disk space from the storage containing Log Files without affecting anything.
    I couldn't find any documentation on this specific requirement, and want to confirm
    I dont see why not. Once the logs are cleared, Exchange doesnt care.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • HT201210 I upgraded from iPhone 3G to 4S a few days ago. I choose the option to restore from my last 3G backup. It worked fine but I just realized that I do not have the new apps which come with the 4S. What should I do? Thanks for any help. Léo

    I upgraded from iPhone 3G to 4S a few days ago. When setting up the new 4S, I choose to restore my last 3G backup. It started by updating the OS to version 5.1 (9B179) then restored my apps and setting. Everything went well except that I realized I do not have the new apps which come with the 4S, like FaceTime, HD video and Siri.
    What should I do to correct this?
    Thank you in advance for any help on this.

    Ah, FaceTime is not an app, either. It's accessed by tapping the FaceTime button when you are in the contacts app and have selected a contact. This can also be done from the Phone app under the Contacts tab, or during a call, you can switch to FaceTime.
    Let me know what other apps/features you are missing.

  • Moving the log file of a publisher database SQL Server 2008

    There are many threads on this here. Most of them not at all helpful and some of them wrong. Thus a fresh post.
    This post regards SQL Server 2008 (10.0.5841)
    The PUBLISHER database primary log file which is currently of 3 blocks and not extendable,
    must be moved as the LUN is going away.
    The database has several TB of data and a large number of push transactional replications as well as a couple of bi-directional replications.
    While the primary log file is active, it is almost never (if ever) used due to its small fixed size.
    We are in the 20,000 TPS range at peak (according to perfmon). This is a non-trivial installation.
    This means that
    backup/restore is not even a remotely viable option (it never is in the real world)
    downtime minimization is critical - measured in minutes or less.
    dismantling and recreating the replications is doable, but I have to say, I have zero trust in the script writer to generate accurate scripts. Many of these replications were originally set up in older versions of SQL Server and have come along for the
    ride as upgrades have occurred. I consider scripting everything and dismantling the whole lot pretty high risk. In any case, I do not want to have to reinitialize any replications as this takes, effectively, an eternity.
    Possible solution:
    The only option I can think of is to wind down everything, such that there are zero outstanding uncommitted transactions and detach the database, delete the offending log file and reattach using the CREATE DATABASE xyz ATTACH_REBUILD_LOG option.
    This should, if I have understood things correctly, cause SQL Server to recreate the default log file in the same directory as the .mdf file. I am not sure what will happen to the secondary log file which is not moving anywhere at this point.
    The hard bit is insuring that every transaction in the active log files have been replicated before shutdown. This is probably doable. I do not know how to manually flush any left over transactions to replication. I expect if I shut down all "real"
    activity and wait for a certain amount of time, eventually all the replications will show "No replicated transactions are available" and then I would be good to go.
    Hillary, if you happen to be there, comments appreciated.

    Hi Philip
    you should try this long back suggested way of stopping replication and restore db and rename or detach attach
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/6731803b-3efa-4820-a303-4ffb7edf154a/detaching-a-replicated-database?forum=sqlreplication
    Thanks
    Saurabh Sinha
    http://saurabhsinhainblogs.blogspot.in/
    Please click the Mark as answer button and vote as helpful
    if this reply solves your problem
    I do not wish to be rude, but which part of the OP didn't you understand?
    Specifically the bit about 20,000 transactions a second and database size of several TB. Do you have any concept whatsoever of what this means? I will answer for you, "no, you are clueless" as your answer clearly shows.
    Stop wasting bandwidth by proposing pointless and wrong solutions which indicate that you did not read the OP, or do you just do this to generate points?
    Also, you clearly failed to notice that I was on the thread to which you referred, and I had some pointed comments to make. This thread was an attempt to garner some input for an alternative proposal.

  • Transaction log shipping restore with standby failed: log file corrupted

    Restore transaction log failed and I get this error: for only 04 no of database in same SQL server, renaming are working fine.
    Date                     
    9/10/2014 6:09:27 AM
    Log                        
    Job History (LSRestore_DATA_TPSSYS)
    Step ID                
    1
    Server                  
    DATADR
    Job Name                           
    LSRestore_DATA_TPSSYS
    Step Name                        
    Log shipping restore log job step.
    Duration                             
    00:00:03
    Sql Severity        0
    Sql Message ID 0
    Operator Emailed           
    Operator Net sent          
    Operator Paged               
    Retries Attempted         
    0
    Message
    2014-09-10 06:09:30.37  *** Error: Could not apply log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' to secondary database 'TPSSYS'.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred while processing the log for database 'TPSSYS'. 
    If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
    An error occurred during recovery, preventing the database 'TPSSYS' (13:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
    RESTORE LOG is terminating abnormally.
    Processed 0 pages for database 'TPSSYS', file 'TPSSYS' on file 1.
    Processed 1 pages for database 'TPSSYS', file 'TPSSYS_log' on file 1.(.Net SqlClient Data Provider) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  Skipping log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' for secondary database 'TPSSYS' because the file could not be verified.
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  Deleting old log backup files. Primary Database: 'TPSSYS'
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  The restore operation completed with errors. Secondary ID: 'dd25135a-24dd-4642-83d2-424f29e9e04c'
    2014-09-10 06:09:30.37  *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.37  *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-10 06:09:30.37  *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
    2014-09-10 06:09:30.38  ----- END OF TRANSACTION LOG RESTORE    
    Exit Status: 1 (Error)

    I Have restore the database to new server and check with new log shipping but its give this same error again, If it is network issue i believe issue need to occur on every database in  that server with log shipping configuration
    error :
    Message
    2014-09-12 10:50:03.18    *** Error: Could not apply log backup file 'E:\LsSecondery\EAPDAT\EAPDAT_20140912051511.trn' to secondary database 'EAPDAT'.(Microsoft.SqlServer.Management.LogShipping) ***
    2014-09-12 10:50:03.18    *** Error: An error occurred while processing the log for database 'EAPDAT'.  If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
    An error occurred during recovery, preventing the database 'EAPDAT' (8:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
    RESTORE LOG is terminating abnormally.
    can this happened due to data base or log file corruption, if so how can i check on that to verify the issue
    Its not necessary if the issue is with network it would happen every day IMO it basically happens when load on network is high and you transfer log file which is big in size.
    As per message database engine was not able to restore log backup and said that you must rebuild log because it did not find out log to be consistent. From here it seems log corruption.
    Is it the same log file you restored ? if that is the case since log file was corrupt it would ofcourse give error on wehatever server you restore.
    Can you try creating logshipping on new server by taking fresh full and log backup and see if you get issue there as well. I would also say you to raise case with Microsoft and let them tell what is root cause to this problem
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles

  • Can I restore the log to another DB?

    Thank you for reading my problem first
    For example, I have a database name DEMO, and for this DB, I have 1 complete data backup, and also have 1 log backup which was taken after the data backup.
    Now I want to restore this DEMO to another database DEMO_666, I am able to import the complete data backup into DEMO_666 with "db_activate recover" , but is it possible to import the log backup from DEMO to DEMO_666 as well?
    I dont know if I say it clearly, if you have any questions, please let me know  _
    Thanks for help.
    vivian

    wow, so quick ~ thank you!
    But I got some error message while trying to restore the log backup, can you help me see below and tell me what is the problem if you get it ? _
    and the source DB and target DB are both on same computers.
    Thanks,
    vivian
    dbmcli on demo_666>db_activate recover demo6_full
    OK
    Returncode              0
    Date                    20080924
    Time                    00171259
    Server                  IBM-L3GWY26.cn.ibm.com
    Database                DEMO1
    Kernel Version          Kernel    7.6.03   Build 015-123-173-107
    Pages Transferred       360
    Pages Left              0
    Volumes                 1
    Medianame               Demo6_full
    Location                D:\maxdb_data\backup\recover\demo1_full
    Errortext
    Label                   DAT_000000001
    Is Consistent           true
    First LOG Page          1177
    Last LOG Page
    DB Stamp 1 Date         20080923
    DB Stamp 1 Time         00135145
    DB Stamp 2 Date
    DB Stamp 2 Time
    Page Count              347
    Devices Used            1
    Database ID             IBM-L3GWY26.cn.ibm.com:DEMO1_20080923_135145
    Max Used Data Page      0
    Converter Page Count    8
    dbmcli on demo_666>recover_start demo6_log log 001
    ERR
    -24988,ERR_SQL: SQL error
    -903,Host file I/O error
    20000,no update of LogInfoPage: DeviceState = Cleared, LogIsEmpty = true
    6,k38headmaster, Error code 3700 "hostfile_error"
    6,RestoreLog, Error code 3700 "hostfile_error"
    Edited by: vivian shi on Sep 24, 2008 11:17 AM

  • HT4859 I turned off my iPad during the process of restoring it, will this mess up the iPad or my apps?

    I turned off my iPad during the process of restoring it, will this mess up the iPad or my apps?

    If you turned it off in the process of doing a full restore, yes.  If you turned it off in the process of restoring it from an iCloud backup, it depends.  You may be able to turn it on and resume the restore; otherwise you'll have to restore from the backup again.

  • Unable to take recovery to end of the log

    I got the below error. When i am trying to take recovery of a database to end of the log.(i.e, without taking the tail log backup). I am posting the details of that error also here.
    Microsoft .Net framework error
    Unhandled exception has occurred in a component in your application. If you click continue,the application will ignore this error and attempt to continue.
    An exception occurred while executing a Transact-SQL statement or the batch.
    Details of error
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
    ************** Exception Text **************
    Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: Database 'FullRecovery' is in transition. Try
    the statement later.
    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
    at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
    at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
    at System.Data.SqlClient.SqlDataReader.get_MetaData()
    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
    at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
    at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
    at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
    at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
    at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
    at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
    at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
    at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(String sqlCommand)
    --- End of inner exception stack trace ---
    at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteWithResults(String sqlCommand)
    at Microsoft.SqlServer.Management.Smo.ExecuteSql.ExecuteWithResults(String query)
    at Microsoft.SqlServer.Management.Smo.ExecuteSql.ExecuteWithResults(StringCollection query, Object con)
    at Microsoft.SqlServer.Management.Smo.ExecuteSql.ExecuteWithResults(String query, Object con)
    at Microsoft.SqlServer.Management.Smo.PostProcessDatabaseInsideAttribs.GetRowResults(DataProvider dp)
    at Microsoft.SqlServer.Management.Smo.PostProcessDatabaseInsideAttribs.GetColumnData(String name, Object data, DataProvider dp)
    at Microsoft.SqlServer.Management.Smo.DataProvider.ManipulateRowDataPostProcess()
    at Microsoft.SqlServer.Management.Smo.DataProvider.GetTable()
    at Microsoft.SqlServer.Management.Smo.ExecuteSql.ExecuteWithResults(StringCollection query, Object con, StatementBuilder sb)
    at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillData(ResultType resultType, StringCollection sql, Object connectionInfo, StatementBuilder sb)
    at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillDataWithUseFailure(SqlEnumResult sqlresult, ResultType resultType)
    at Microsoft.SqlServer.Management.Smo.SqlObjectBase.BuildResult(EnumResult result)
    at Microsoft.SqlServer.Management.Smo.DatabaseLevel.GetData(EnumResult res)
    at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
    at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
    at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
    at Microsoft.SqlServer.Management.Smo.ExecutionManager.GetEnumeratorDataReader(Request req)
    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetInitDataReader(String[] fields, OrderBy[] orderby)
    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.ImplInitialize(String[] fields, OrderBy[] orderby)
    at Microsoft.SqlServer.Management.Smo.SqlSmoObject.OnPropertyMissing(String propname, Boolean useDefaultValue)
    at Microsoft.SqlServer.Management.Smo.PropertyCollection.RetrieveProperty(Int32 index, Boolean useDefaultOnMissingValue)
    at Microsoft.SqlServer.Management.Smo.PropertyCollection.GetValueWithNullReplacement(String propertyName, Boolean throwOnNullValue, Boolean useDefaultOnMissingValue)
    at Microsoft.SqlServer.Management.Smo.Database.get_IsManagementDataWarehouse()
    at Microsoft.SqlServer.Management.Reports.ReportContext.ProcessConnection()
    at Microsoft.SqlServer.Management.Reports.ReportContext.get_Version()
    at Microsoft.SqlServer.Management.Reports.ReportsManager.OnReportsDropDownOpening(Object sender, EventArgs e)
    at System.Windows.Forms.ToolStripDropDownItem.OnDropDownShow(EventArgs e)
    at System.Windows.Forms.ToolStripMenuItem.OnDropDownShow(EventArgs e)
    at System.Windows.Forms.ToolStripDropDownItem.ShowDropDownInternal()
    at System.Windows.Forms.ToolStripDropDownItem.ShowDropDown(Boolean mousePush)
    at System.Windows.Forms.ToolStripMenuItem.OnMenuAutoExpand()
    at System.Windows.Forms.MenuTimer.OnTick(Object sender, EventArgs e)
    at System.Windows.Forms.Timer.OnTick(EventArgs e)
    at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5472 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    AppIDPackage
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/AppIDPackage.DLL
    System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    Microsoft.SqlServer.SqlTools.VSIntegration
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.SqlTools.VSIntegration.DLL
    Microsoft.VisualStudio.Shell.Interop
    Assembly Version: 7.1.40304.0
    Win32 Version: 7.10.6071
    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
    Microsoft.VisualStudio.OLE.Interop
    Assembly Version: 7.1.40304.0
    Win32 Version: 7.10.6070
    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
    System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    SqlWorkbench.Interfaces
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/SqlWorkbench.Interfaces.DLL
    Microsoft.SqlServer.SqlTDiagM
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.SqlTDiagM/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.SqlTDiagM.dll
    Microsoft.SqlServer.Instapi
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
    Microsoft.VisualStudio.Shell
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1826 (QFE.050727-1800)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.dll
    Microsoft.VisualStudio.Shell.Interop.8.0
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1826 (QFE.050727-1800)
    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.Shell.Interop.8.0/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.8.0.dll
    Microsoft.SqlServer.Management.SDK.SqlStudio
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.SDK.SqlStudio.DLL
    SQLEditors
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/SQLEditors.DLL
    Microsoft.VisualStudio.TextManager.Interop
    Assembly Version: 7.1.40304.0
    Win32 Version: 7.10.6070
    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.TextManager.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.TextManager.Interop.dll
    SqlMgmt
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/SqlMgmt.DLL
    Microsoft.SqlServer.Management.UserSettings
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.UserSettings.DLL
    EnvDTE
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1826 (QFE.050727-1800)
    CodeBase: file:///C:/Windows/assembly/GAC/EnvDTE/8.0.0.0__b03f5f7f11d50a3a/EnvDTE.dll
    Microsoft.SqlServer.Management.Sdk.Sfc
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Management.Sdk.Sfc/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Management.Sdk.Sfc.dll
    Microsoft.SqlServer.Management.Reports
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.Reports.DLL
    ObjectExplorer
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/ObjectExplorer.DLL
    Microsoft.VisualStudio
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1826 built by: QFE
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.dll
    System.Drawing.Design
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
    Microsoft.VisualStudio.Designer.Interfaces
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.Designer.Interfaces/1.0.5000.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Designer.Interfaces.dll
    ConnectionDlg
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/ConnectionDlg.DLL
    Microsoft.SqlServer.Management.Controls
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.Controls.DLL
    Accessibility
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    Microsoft.SqlServer.RegSvrEnum
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.RegSvrEnum/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.RegSvrEnum.dll
    Microsoft.SqlServer.Management.SqlStudio.Explorer
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.SqlStudio.Explorer.DLL
    System.Design
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Design/2.0.0.0__b03f5f7f11d50a3a/System.Design.dll
    System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
    Microsoft.SqlServer.Management.SqlStudio.Migration
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.SqlStudio.Migration.DLL
    Microsoft.SqlServer.Smo
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Smo/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Smo.dll
    System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    Microsoft.NetEnterpriseServers.ExceptionMessageBox
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.ExceptionMessageBox/10.0.0.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.ExceptionMessageBox.dll
    Microsoft.SqlServer.ConnectionInfo
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.ConnectionInfo/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.ConnectionInfo.dll
    Microsoft.SqlServer.Management.RegisteredServers
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Management.RegisteredServers/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Management.RegisteredServers.dll
    Microsoft.SqlServer.SqlClrProvider
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.SqlClrProvider/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.SqlClrProvider.dll
    System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    zvrwl7xb
    Assembly Version: 10.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    Microsoft.SqlServer.SString
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.SString/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.SString.dll
    xf4zos8t
    Assembly Version: 10.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    Microsoft.SqlServer.GridControl
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.SqlServer.GridControl/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.GridControl.dll
    System.Transactions
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
    CodeBase: file:///C:/Windows/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
    System.EnterpriseServices
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
    Microsoft.SqlServer.SqlEnum
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.SqlEnum/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.SqlEnum.dll
    Microsoft.SqlServer.BatchParserClient
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.BatchParserClient/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.BatchParserClient.dll
    Microsoft.SqlServer.BatchParser
    Assembly Version: 10.0.0.0
    Win32 Version: 2007.0100.1600.022 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.SqlServer.BatchParser/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.BatchParser.dll
    msvcm80
    Assembly Version: 8.0.50727.4940
    Win32 Version: 8.00.50727.4940
    CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc/msvcm80.dll
    Microsoft.DataWarehouse
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.DLL
    Microsoft.SqlServer.Dmf
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Dmf/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Dmf.dll
    Microsoft.SqlServer.PolicyEnum
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.PolicyEnum/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.PolicyEnum.dll
    System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
    Microsoft.DataWarehouse.SQM
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
    Microsoft.SqlServer.Sqm
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Sqm.DLL
    ObjectExplorerReplication
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/ObjectExplorerReplication.DLL
    Microsoft.SqlServer.Management.SqlStudio
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.SqlStudio.DLL
    tkrymgso
    Assembly Version: 10.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    Microsoft.SqlServer.Management.MultiServerConnection
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Management.MultiServerConnection/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Management.MultiServerConnection.dll
    RadLangSvc
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/RadLangSvc.DLL
    Microsoft.VisualStudio.Package.LanguageService
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1826 (QFE.050727-1800)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Package.LanguageService/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Package.LanguageService.dll
    Microsoft.SqlServer.SqlParser
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.SqlParser.DLL
    Microsoft.VisualStudio.TextManager.Interop.8.0
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1826 (QFE.050727-1800)
    CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.TextManager.Interop.8.0/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.TextManager.Interop.8.0.dll
    SqlManagerUI
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/SqlManagerUI.DLL
    Microsoft.SqlServer.Management.Scripting
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.Scripting.DLL
    Microsoft.SqlServer.DataStorage
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.DataStorage/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.DataStorage.dll
    Microsoft.SqlServer.Types
    Assembly Version: 10.0.0.0
    Win32 Version: 2007.0100.1600.022 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Types/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Types.dll
    Microsoft.VisualStudio.Design
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1826 (QFE.050727-1800)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Design/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Design.dll
    Microsoft.VisualStudio.Shell.Design
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1826 (QFE.050727-1800)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell.Design/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Design.dll
    Microsoft.SqlServer.Management.SqlStudio.Controls
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.SqlStudio.Controls.DLL
    Microsoft.SqlServer.WizardFramework
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.WizardFramework/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.WizardFramework.dll
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
    -- Thanks and Regards Srikar Reddy Gondesi, Trainee SQL Server Database Administrator Miracle Software systems, Inc.

    Hello Sir,
    I am using sql server 2008 evaluation edition.
    I did it using T-Sql only in SSMS.
    i am trying to restore database without taking the tail log backup.
    Actually i am learning how to do that. Instead of getting result, it is getting strucked in execution for a while and gave this error.
    I got this error yesterday evening.
    The below shown is the code which i used to restore.
    USE master
    GO
    --restore the full database backup
    RESTORE DATABASE FullRecovery
    FROM DISK='D:\SQLBackups\FullRecovery.bak'
    WITH NORECOVERY;
    --restore the log backup
    RESTORE LOG FullRecovery
    FROM DISK='D:\SQLBackups\FullRecovery_log.trn'
    WITH RECOVERY;
    I need to get the below mentioned error as mentioned in the book where i am reading from.
    Msg 3159, Level 16, State 1, Line 1
    The tail of the log for the database "FullRecovery" has not been backed up. Use BACKUP LOG
    WITH NORECOVERY to back up the log if it contains work you do not want to lose. Use the WITH
    REPLACE or WITH STOPAT clause of the RESTORE statement to just overwrite the contents of the
    log.
    Msg 3013, Level 16, State 1, Line 1
    RESTORE DATABASE is terminating abnormally.
    Msg 3117, Level 16, State 1, Line 5
    The log or differential backup cannot be restored because no files are ready to rollforward.
    Msg 3013, Level 16, State 1, Line 5
    RESTORE DATABASE is terminating abnormally.
    But i got the error which i mention in the first post.
    Thank you.
    -- Thanks and Regards Srikar Reddy Gondesi, Trainee SQL Server Database Administrator Miracle Software systems, Inc.

  • Third party backup software, how is the log sequence working?

    Me and a colleague had a discussion about how third party software and full backups locally on the SQL works together.
    If we use TSM that do full backups and then logbackups every hour in between for example.
    If I between the two full backups from TSM accidently do a "non copy-only" full backup do I then also break the whole log sequence backup from then and untill the next TSM backup is?
    Or can I use the full backup from my mistake and then take the log backups from TSM that occured after that fail and restore the database?
    I guess this depends on the third party backup software, but in my mind it should work but according to him it doesn't.
    Try to "paint" how I mean:
    I = full TSM backup
    - = log TSM
    F = my fail backup full but not copy only.
    I---F-------I
              ^ is where I would want to restore with both my full one and the logs from TSM. Hope you understand what I mean.

    yes, you should be able to use the full backup taken in middle and use the rest of the log backups taken afterwards to restore the database.while I do not use TSM, we use QUEST(DELL) LITESPEED, that takes full backup once a day and log backups
    every 15mins.
    if someone accidentally takes full backup in the middle of day with out 'copy only',
    log sequence will break and successive log backups depend on this full back up.
    while this should be prevented from happening in first place, you can still restore from native full backup and then apply log backups taken from third party taken after the  native Full backup.
    if this happens, I would restore the FULLBACKP with NORECOVERY using NATIVE SQL and then use  lite speed syntax to restore the log backups.Remember, native sql cannot read third party formatted backups(atleast litespeed), thats why I restore the full backup
    using native sql, since it was taken with native sql backup and log backups using litespeed syntax.
    Hope it Helps!!
    Thanks, well it was just a theory discussion we had about the issue. But none of us could find info on the internet easy to prove our point :) Thanks.

  • HT4859 how do i restore to a previous icloud backup

    How do I restore to a previous icloud backup.  I lost a lot of photos when I did the ios 5 update.

    Restore your phone using the settings > general > reset options.   You will be given the opportunity to restore from a previous iCloud backup.

  • Restoring from a Time Machine Backup on a new Hard drive

    Hi,
    I have a late 2009 iMac and I had the HD replaced (it was included in the recent HD recall).
    Before I had it replaced, I made a backup using my time capsule and it was on the latest version of Mountain Lion.
    My question is, since I have to install the OS using the original install discs which was Snow Leopard, if I use the restore from Time Machine using Mac OSX Utilities, will my Mac restore my Mountain Lion backup (and have everything like it used to before I had the HD replaced)? Or do I have to reinstall Lion then Mountain Lion then restore from there?
    It would be a pain to re download everything.
    Hope someone can help me out.
    Thanks in advance

    Please visit Pondini's Time Machine FAQ for help with all things Time Machine.
    You will find that Mountain Lion stores an invisible copy of the Recovery HD. You can boot from your Time Machine backup drive by restarting with OPTION boot:
    Boot Using OPTION key:
      1. Restart the computer.
      2. Immediately after the chime press and hold down the "OPTION" key.
      3. Release the key when the boot manager appears.
      4. Select the disk icon for your Time Machine backup drive.
      5. Click on the arrow button below the icon.
    Your computer should boot into the Recovery HD. You will be presented with a main window of options. Select the option to restore from a Time Machine backup then click on the Continue button.

  • How do I restore files from time machine backups made before reformatting macbook air?

    How do I restore files from time machine backups made before reformatting macbook air?

    The section titled "Restoring data from Time Machine backups" in the following may help: http://support.apple.com/kb/HT1427

  • SQL 2012 Transactional Replication Publisher is also AG Primary, AG fine, but Replication status continuously 'waiting for next Log backup'

    Hi,
    I have a SQL 2012 instance that hosts 3 databases that are publishers in (push) transactional replication to subscribers in other domains and are also primary in an Availability Group to other instances in the same domain.  The AG is healty (synchronized),
    and replication is ok for 2 databases, but the third continuously shows the Publisher to Distributor history status as 'Replicated transactions are waiting for next Log backup or for mirroring to catch up.'
    I have weekly full, nightly differential, and hourly log.  Those are running and I've tested restoring the publisher db from them into a test instance.  The option for sync_with_backup is 0.  I generated a new snapshot, no change (haven't
    reinitialized, that will be last possible option as this is production).  When the log backups run, status will briefly change to 'Approximately (x) log records have been scanned in pass # ..., 0 of which were marked for replication' and some data
    does replicate, but then status immediately changes back to the message about waiting for log backup.   We are only replicating tables (no views, sp's, etc).  All subscribers and AG secondaries are SQL 2012.  My db is less than 200
    GB data. 
    The jobs are continuously running and data updates are occurring on the primary.  The distribution database is on the same instance as the publishers.  Anyone have any ideas what could be happening? 
    Thanks greatly!

    Update - I resolved this. 
    We had added a new asynchronous instance to the AG, but hadn't added the databases on the new node to the AG yet.  Conceptually it seems that adding the instance must have marked the logs and interferred with transactional replication on the
    primary.  Once I added the databases to the AG on the secondary, then the replication status cleared on the primary and has remained cleared.  It is odd though that it only impacted one of the databases in the AG. 
    cheers. 

  • How to monitor Log Backups for MS SQL Server

    Hello all.
    We are running Solution Manager 7.1 on SP Stack 10 and have downloaded the latest template content.
    When configuring the templates for DB monitoring, we noticed that although there is a metric that monitors the age of the last DB backup, there is no such metric to monitor the age of the last successful Log backup, or even a metric to alert us on a failed backup / log backup.
    Has any of you ever had to create a custom metric to monitor either the age of the latest successful log backup for MS SQL Server, or a custom metric to alert on failed backups / log backups?
    If yes, could you provide some instructions on how to create such a metric?
    Thank you in advance for your answers.
    Phevos

    Divyanshu, thank you for your answer.
    I had a similar idea to check the DB log file for failed log backups. The problem is that when I opened the log file from the dbacockpit, I found no errors/warnings for the days that our log backups did not run or failed. Here is a small part of that log to show you what I mean. In this example, the log backup was not running from 25th of July until the 28th of July when we fixed the log backups again, after receiving a disk space warning (log disk drive was almost full):
    The last successful log backup is mentioned in the log: "20140724091524    Backup    Log was backed up"
    Then as the days go by, there is no backup failure entries whatsoever to look for them in the log:
    20140725000023    spid18s    This instance of SQL Server has been using a process ID of 1304 since 5/27/2014 11:50:00 PM (local) 5/28/2014 6:50:00
    20140725000023    spid18s    AM (UTC). This is an informational message only; no user action is required.
    20140726000020    spid21s    This instance of SQL Server has been using a process ID of 1304 since 5/27/2014 11:50:00 PM (local) 5/28/2014 6:50:00
    20140726000020    spid21s    AM (UTC). This is an informational message only; no user action is required.
    20140727000023    spid22s    This instance of SQL Server has been using a process ID of 1304 since 5/27/2014 11:50:00 PM (local) 5/28/2014 6:50:00
    20140727000023    spid22s    AM (UTC). This is an informational message only; no user action is required.
    20140728000022    spid17s    This instance of SQL Server has been using a process ID of 1304 since 5/27/2014 11:50:00 PM (local) 5/28/2014 6:50:00
    20140728000022    spid17s    AM (UTC). This is an informational message only; no user action is required.
    Until finally on the 28th we restored the log backup functionality:
    20140728042814    Backup    Log was backed up. Database: XXX, creation date(time): 2010/12/22(16:45:29)
    So, I find it difficult to deduce an appropriate string to look for in the log, in order to generate an alert when my log backups are not working.
    Any suggestions? Am I looking at the wrong place perhaps?

Maybe you are looking for