You can use: SELECT name FROM sys.master_files WHERE database_id = db_id() AND type = 1 Log files have type = 1 for any database_id and all files for all databases can be found in sys.master_files. EDIT: I should point out that you shouldn’t be shrinking your log on a routine basis. Your transaction log should … Read more
You could use the undocumented DBCC LOG(databasename, typeofoutput) where typeofoutput: 0: Return only the minimum of information for each operation — the operation, its context and the transaction ID. (Default) 1: As 0, but also retrieve any flags and the log record length. 2: As 1, but also retrieve the object name, index name, page … Read more
The transaction log is an integral part of the backup. You can’t tell SQL Server to ignore the transaction log, because there is no way to let’s say restore and shrink the transaction log file at the same time. However, you can take a look at DBA post to hack the process, although it is … Read more
Okay, here is a solution to reduce the physical size of the transaction file, but without changing the recovery mode to simple. Within your database, locate the file_id of the log file using the following query. SELECT * FROM sys.database_files; In my instance, the log file is file_id 2. Now we want to locate the … Read more
Making a log file smaller should really be reserved for scenarios where it encountered unexpected growth which you do not expect to happen again. If the log file will grow to the same size again, not very much is accomplished by shrinking it temporarily. Now, depending on the recovery goals of your database, these are … Read more