+ Reply to Thread
Results 1 to 4 of 4

Thread: .mdf file

  1. Junior Member Registered Member
    Join Date
    Jan 2016
    Posts
    1
    #1

    Default .mdf file

    Good afternoon.

    So there SCCM2012r2 mode primary site (PS), is 5t secondary site (SS).

    It so happened that the file is broken: master.mdf or mastlog on primary site, do not start sql-server, and SQL + SCCM one a server, there is no fresh backups, the last master.mdf (mastlog.ldf), 5-month-old, Compare 55-bit differences found with a broken. In an isolated network start his sccm2012r2 (primary site) to those files - start. After starting the differences between the broken files to and from backup (but where was the launch) - it was 48.

    Thanks in advance.
    Reply With Quote Quote  

  2. SS -->
  3. Senior Member cyberguypr's Avatar
    Join Date
    May 2007
    Location
    Chicago, IL
    Posts
    5,763

    Certifications
    GCFE, GCED, GCIH, CISSP, CCSP, and others that should never be mentioned
    #2
    Is there a question in there somewhere?
    Reply With Quote Quote  

  4. Junior Member Registered Member
    Join Date
    Feb 2016
    Posts
    1
    #3
    When you can’t restore .sql data via standard solutions make use of guide below or if even the guide can’t help you, it might be that your sql data was severely corrupted and you may get more powerful tips on next sources

    http://itknowledgeexchange.techtarge...-is-corrupted/
    http://forums.techguy.org/windows-xp...ml#post8996088
    https://sql.recoverytoolbox.com/ Recovery Toolbox for SQL Server

    Since I don’t have the system databases backups, the only option left for me was to rebuild the system databases in SQL Server 2008. So let’s go for it!
    1. If you have SQL Server 2008 Installation media available then insert the same into the disk drive and search for Setup.EXE file or else search for Setup.EXE file which will be available locally on your server. The default location of Setup.EXE file on your server will be C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Release.
    2. Right click Command Prompt and select Run as administrator as shown in the below snippet to open up command prompt with elevated administrative privileges.

    Important Note
    The command prompt must be run under Administrator privileges to successfully rebuild the system databases.
    3. In the command prompt window you need to enter the below mentioned command with appropriate values for each parameter and press enter to rebuild the system databases as per the syntax which is mentioned in MSDN.
    Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName
    /SQLSYSADMINACCOUNTS=accounts [/SAPWD= StrongPassword][/SQLCOLLATION=CollationName]


    If you want to change the server level collation then specify collation value for /SQLCOLLATION parameter. As /SQLCOLLATION is an optional parameter, if it is not specified then the current server collation is used to rebuild the system databases.
    4. Once the setup has successfully completed rebuilding the system databases it will return to command prompt and will mention the SQL Server Build Number as shown in the snippet below. In case if there are any syntax related or permission issues then the specific error message will be displayed within the command prompt window. You need to fix those issues before you can complete the activity.
    5. You can view the overall summary from C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Summary.txt

    In this article you have seen how to rebuild system databases in SQL Server 2008. You should rebuild system database only under conditions when you don’t have backups of system database or they are corrupted. When you rebuild system database it rebuilds MASTER, MSDB, and MODEL databases as a result you will lose all your Linked Server, Logins, SQL Server Job information.
    Reply With Quote Quote  

  5. Senior Member nachodba's Avatar
    Join Date
    Sep 2014
    Location
    Fairfax, VA
    Posts
    188

    Certifications
    MCSE: Servers, Sec +, MCITP:DBA 2008, MCSA SQL Server 2012/2014
    #4
    Great post above. Also, in the event you don't know which user accounts need to be created, setup a SQL Profiler trace to catch failed logins.
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks