![]() ![]() I fired up Web Platform Installer and from the what's new tab I installed SQL Server Management Studio and browsed the db to make sure the data was there.Īt that point i tried the tool included with MSSQL "SQL Import and Export Wizard" but the result of the csv dump only included the column names. one will be the actual database and the other the log file.ĭisk='c:\temp\mydbName-v10.bak' WITH MOVE 'mydbName' TO Once you have this installed click on the database selection ( you are also required to download Frameworks and Runtimes)Īfter instalation go to the windows command prompt and: This requires the download of the Web Platform Installer "wpilauncher_n.exe" The method I used included part of Richard Harrison's method: together with this export tool and you will have an SQL script that contains the database. MOVE 'mydbName_log' TO 'c:\temp\mydbName_data.ldf' Īt this point you have extracted the database - then install Microsoft's "Sql Web Data Administrator". MOVE 'mydbName' TO 'c:\temp\mydbName_data.mdf', RESTORE DATABASE mydbName FROM disk='c:\temp\mydbName-v10.bak' This will list the contents of the backup - what you need is the first fields that tell you the logical names - one will be the actual database and the other the log file. restore filelistonly from disk='c:\temp\mydbName-v10.bak' There execute sqlcmd -S \SQLExpress (whilst logged in as administrator) So, install SQL Server Express edition, and open the SQL Server Powershell. SQL Server Express is free and will do the job. You will need to use SQL server to extract these. The bak file will probably contain the LDF and MDF files that SQL server uses to store the database. BAK files from SQL server are in Microsoft Tape Format (MTF) ref: Msg 3013, Level 16, State 1, Server DESKTO\SQLEXPRESS, Line 2The. SQL Server cannot process this media family. The media family on device 'C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Backup\test.bak' is incorrectly formed. Msg 3241, Level 16, State 1, Server DESKTO\SQLEXPRESS, Line 2 1> use newhouseĢ> restore database newhouserecovery fromģ> disk = N'C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Backup\test.bak'Ħ> move N'test' to N'C:\Users\me\Backup\test.mdf',ħ> move N'test_log' to N'C:\Users\me\Backup\test_log.ldf', Here is what I get on a fresh export running on the machine that has the account software itself. If the file is corrupted, than the program itself is exporting a corrupted version. bak or on another machine that I have transferred the file to. bak file is on the machine that create the. bak file created by this program whether the. ![]() ![]() I can open the file with gHex - a hex editor in GNOME - and read the data.Īs far as the question about the file being corrupted, I do not believe so. Update #2 - again in reply what I can tell, the file is not encrypted. bak file with fictitious data is available here. RESTORE HEADERONLY is terminating abnormally.ġ> restore headeronly from disk='/home/me/test.bak'Ī. VERIFY DATABASE is terminating abnormally.ġ> restore headeronly from disk='/home/me/test.bak' with nounload RESTORE DATABASE is terminating abnormally.ġ> restore verifyonly from disk='/home/me/test.bak' The media family on device '/home/me/test.bak' is incorrectly formed. ![]() SQL Server 2017 on a Linux machine and get the following output.ġ> restore database newhouse from disk='/home/me/test.bak'.SysTools SQL Backup recovery but it returns "Could not identify SQL Server version for the selected.Microsoft SQL Server Management Studio 18 but no backup sets are listed for restoration.I have tried the following SQL Server versions without success: bak files it creates to get all the data for importing into the new system. The program itself does not have a complete set of export tools so we are hoping to access the data from the. Our goal is to export the data from the program, reformat it, and then load it into another accounting system. In past correspondence, the provider told us that the product was built on SQL Server, but never told us what version. The background: we have a functioning invoicing program with over 10 years of data from a defunct provider. I could use tips on how to recover a non-standard SQL Server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |