read ldf file

method. It's easy to conquer this headache problem. The next step is how to open the SQL Server file, if necessary. MDF and. ldf two files.If the path to the two files is E:/a.mdf,e:a_log. LDF. Enter into Navicat premium and connect to SQL successfully, then click Query to create a new query input statement: EXEC sp_attach_db ' netking ', ' E:\A.mdf ', ' E:\A_l

problem. The next step is how to open the SQL Server file, provided you have to. MDF and. ldf two files. Assume that the path to the two files is E:/a.mdf,e:a_log. LDF, enter into NAVICAT Premium and connect SQL successfully, then click Query to create a new query input statement: EXEC sp_attach_db ' netking ', ' E:\A.mdf ', ' E:\A_log.ldf '. Where Netking is th

number of MB allowed to be shrunk is displayed. Enter this number directly and click OK. You can also use SQL statements. (Note: the LDF file size does not change after you use the Enterprise Manager to perform the shrink operation. Use the following SQL command) -- Shrink DatabaseDBCC shrinkdatabase (database name) -- Contract the specified data file. 1 is

Tags: arc arch database. com truncation NTB Fast automatic archive in SQL Server, where the transaction log is often large, in addition to setting the database to auto shrink, you can use the following SQL command to quickly clear the transaction log in the database as follows:-First step: Empty the logDUMP TRANSACTIONDatabaseName withno_log--Step two: Truncate the transaction logBACKUP LOGDatabaseName withno_log--Step three: Shrinking the databaseDBCC shrinkdatabase (databasename) Some points n

Attach the database.Additional database:Enterprise Manager-- Right-click "Database"-- All tasks-- Attach a database-- Select your. mdf file name-- OK-- If no. ldf file is displayed and whether to create it, select "yes"Query the method in Analyzer:-- Data files and log filesSp_attach_db 'database name', 'Data file name

0. View the database file name and physical file nameSELECT as current_file_location from Sys.master_files1. Run the command UseMaster--Run from MasterALTER DATABASEdbmodifyFILE(Name='DB', filename='C:\NewPath\Database.mdf');ALTER DATABASEdbmodifyFILE(Name='db_LOG', filename='C:\NewPath\Database_log.ldf');ALTER DATABASEDbSETOFFLINE with ROLLBACKIMMEDIATE;2. Move files, check permissions* Move database fil

SQL Server deletes the log file after the LDF saves the steps:Create a new database first,Remove the new. mdbOverwrite with the MDB you want to restoreExecute the following statementALTER DATABASE ' Db_core ' SET RECOVERY simple;ALTER DATABASE Db_core SET emergencyALTER DATABASE Db_core set Single_userDBCC CHECKDB (' Db_core ', Repair_allow_data_loss)DBCC CHECKDB (' Db_core ', repair_rebuild)ALTER DATABASE

Address: http://blog.csdn.net/gaoling179/article/details/5971100 When using visualdsp ++ 5.0 update7, when creating a project, select Add LDF and startupCodeOptions, as shown in: However, LDF and Code are not added to the generated project file, The following error is prompted: Error: Incorrect quantifiers (Microsoft JScript compilation error)Error: t

meaning of "MSSQL" MDF, NDF, LDF file2012-09-03 15:32:56| Category: SQL database | Report | Font size Subscription MDF is the abbreviation of primary data file;NDF is the abbreviation of secondary data files;LDF is the abbreviation for log data files.Not the first letter of the word.There are three types of files in a SQL Server 2000 database:MainThe prima

After a closer examination, it is found that there are too many MDF and LDF files in the Mssqldata folder, and several are several G-sizes. This is actually the two files. Usually a variety of restore library, also do not pay attention to this, did not expect the consequences so serious, so the search on the Internet to study how to transfer these files. To sum up: Like my library test_db. /* Set Offline */ ALTER DATABASE [TEST_DB] set

server| Recovery The transaction log file (LDF) is deleted when the SQL Server service is not started (SQL Server cannot delete the log file while it is working), in which case the corresponding database is flagged as suspect (suspend) status after the SQL service is started According to the current results of my experiment, the recovery method is as follows:1,

Label:The "cause of the problem" SQL Server service cannot be edited as long as it is started."Workaround-1":1) in the Start-Run dialog box, enter "Services.msc" to display the following interface:2) Close the selected service as above3) Copy MDF, LDF file4) Restart the selected service"Workaround-2":Opens the SQL Server surface Area Configurator--service and connectivity surface Area Configurator-->database engine--> Service--"Stop"--copy MDF,

Label:SQL2008 Empty Delete log:' Clearing the log in SQL2008 must be done in simple mode, and then back to full mode when the cleanup is complete.----------------------------------------------------------------Use [master]GOALTER database name SET RECOVERY simple with no_waitGOALTER database name SET RECOVERY Simple--Easy modeGOUse database nameGODBCC shrinkfile (N ' database name _log ', one, truncateonly)GO' Database name _log If you don't know what the name is in sys.database_files, you can q