ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Topics
    2. Tags
    3. sql server management studio
    Log in to post
    • All categories
    • scottalanmillerS

      SQL Server Express 2014 Extremely Slow on Network

      Watching Ignoring Scheduled Pinned Locked Moved IT Discussion rdbms sql server 2014 sql server management studio kennel connection kennel connection 7 windows 10
      12
      0 Votes
      12 Posts
      1k Views
      pmonchoP

      @scottalanmiller

      Did you ever solve this problem? Just wondering what you solution was if you did.

    • OksanaO

      Learn how to keep your sensitive data safe with SQL Server Always Encrypted

      Watching Ignoring Scheduled Pinned Locked Moved Starwind sql server always on sql server sql server management studio ssms azure powershell starwind
      1
      3 Votes
      1 Posts
      561 Views
      No one has replied
    • gjacobseG

      SQL Management - Backup to new DB

      Watching Ignoring Scheduled Pinned Locked Moved IT Discussion server2012r2 sql express sql server management studio sql server 2012 sql management
      8
      0 Votes
      8 Posts
      2k Views
      gjacobseG

      I got it restored to a new db,.. but i did have to change the file name.

    • gjacobseG

      Create SQL History Database

      Watching Ignoring Scheduled Pinned Locked Moved IT Discussion server 2012 sql server sql server 2012 sql server management studio database backup restore
      13
      1 Votes
      13 Posts
      3k Views
      gjacobseG

      In this case, it was a matter of the settings during the restore.

      Under GENERAL you had to select your source and destination as normal. Destination was changed so that it was the new History file. Under FILES you updated the DB and LOG files to reflect the new DB, otherwise you would over write the originals.

      This is where they borked it. They didn't mention FILES only going to OPTIONS, and there is where they mentioned updating the file names. The main discovery was that you need to uncheck LEAVE Source database in the restoring state.

      When I emailed them about removing the 'borked' databases I had created the called me back. I mentioned it to the fellow and we had a short discussion on the matter where he took notes and agreed that the directions were incorrect. When I got to the part about unchecking LEAVE Source database in the restoring state he mentioned that he uncheck Take tail-log backup before restore

      Hope this helps.

      0_1460118217976_2016-04-08 08_22_29-NTG - SSI-SQL01 - Connected.png

    • 1 / 1