SQL Server | How to Backup and Restore Databases (Part 1)

SQL Server | How to Backup and Restore Databases (Part 1)


– What’s up, everyone?
(slow music) Welcome to Josh Burns Tech. In this video I’m gonna show you how to backup and restore
databases in SQL Server, as well as create a Maintenance Plan for automated database backups. Coming right up.
(music intensifies) When you start working with SQL Server, whether you’re a DBA, SQL developer, you’re in the process
of learning SQL Server, or you’re the accidental DBA where your business decided to throw SQL Server responsibilities
into your job duties, knowing how to backup
and restore databases are a couple of tasks that you need to learn how to do really well early on. This video is meant for
any version of SQL Server. Now, there are differences in
versions 2005 and previous, however, I will cover those
differences in this video. I’m also gonna show you how to create an automated database
backup maintenance plan so you can schedule full database backups to occur automatically. And this is part one of a part-two series in which part two I’m gonna show you how to take differential and
transaction log backups so that you can add those
into your mix as well, creating automated database
backup plans for those to give you a point-in-time recovery to allow your business to successfully be able to restore back
to a certain point in time if corruption or some other type of database issue occurs
needing a recovery. If you get value from this video and you enjoy it, please give it a Like, and also I want to know what line of work each of you are in, so if you’re a DBA, SQL
developer, an accidental DBA, or you’re just interested in
learning more about SQL Server, leave that in the comments
section of this video. And to be notified when my
weekly tech videos are uploaded, such as the second part
of this part-two series, make sure you subscribe and
hit the notification bell. So, let’s go ahead and take a look at how to backup and restore
databases in SQL Server. So, the first thing
that I’m gonna show you how to do is take a full database backup. So, to take a full database backup of the JoshBurnsTech database we’re gonna right-click on it, we’re gonna go to Tasks, and then we’re gonna click on Back Up. (clicking) So, first we’re backing up the JoshBurnsTech database, which we right-clicked
and went to Task Back Up. The backup type is set to
Full because that’s the type of database backup that we’re taking. There’s also Differential
and Transaction Log backups, which we’re gonna take a look
at in part two of the series. So, again, if you haven’t subscribed and hit the notification bell, be sure to do that now so you’ll be updated when part two is uploaded. So, we’re gonna leave this on Full. We’re backing up to Disk, and this location that’s
already pre-populated is a previous manual Full database backup, that’s why it’s showing up in here. So, we’re not gonna overwrite
this database backup. We’re gonna take a new one. So, what we’re gonna do is click Remove and then we’re gonna click Add. (clicking) So, this location is a default location for database backups on
my SQL Server instance, which I set up in Properties, so let’s go ahead and take
a look at that real quick, and now we can see the default location for backups on this SQL Server instance. So, that’s why when we
clicked on the three dots it automatically took us to that location, because I had it pre-configured in the properties of
my SQL Server instance. So, now we’re back in
that default location. We’re ready to type a file name
in for our database backup. So, we’re in the default location of the D drive, MSSQL, Back ups, and now we’re ready to type the file name. So, we’re gonna name this backup (typing) JoshBurnsTech, and then we’re gonna do an underscore and just today’s date. (typing) And here’s a key point that you don’t want to miss right here. You have to type in the
.BAK file extension. If you don’t, it’s gonna
save your backup as a file and you won’t be able to restore it or do anything with it until you rename it as .BAK so it gets the right extension. So, I’m gonna type in .BAK, (typing) and now we’re ready to
click OK. (clicking) And click OK one more time. (clicking) And now we have the correct path and file name for the database backup that we’re gonna take. Next we’ll click on the
Media Options tab. (clicking) So, the main action that
you want to check on this tab is Overwrite
existing backup sets. So, if you left it on Append
it would basically append it to an existing backup set
that you already had in place, but we want to overwrite it
and take a new database backup. Next we’ll click on
Backup Options, (clicking) and on the Backup Options
tab we’re gonna select Compress backup under
Set backup compression. So, if this is already set up as default on the SQL Server instance, it will automatically compress the backup. We’ll take a look at that in a moment. However, one other thing I want to note is that in certain versions of SQL Server, like the Web Edition,
compression isn’t supported. So, make sure you check
this option regardless. And then for versions like
SQL Server 2005 and previous, compression is not
supported in those versions. But regardless, make sure you check out the Backup Options tab to see
if compression is supported, because you want to use it. For instance, say you’re backing up a database that’s a terabyte in size. I’ve been compression be able to compress that down to 100-gig or less. So, now all the options are configured that we want for our database backup. One other thing I want to show you is that we can also script this out to a new query window, or a file. So, if we do this it will script it out to a new query window, and personally, I think this is important if you’re interested in
learning about SQL Server and that’s your goal,
because when scripting it out you can see the T-SQL backup syntax, which is something that
you need to learn as well. So, the T-SQL that’s generated
is doing backup database, JoshBurnsTech, to disk,
specifying the path, and then these are all the default options that we set up when clicking
on the different tabs. For instance, you can see
compression right here. (clicking) So, now at this point we’re ready to take the
full database backup of the JoshBurnsTech database. This database is very small in size, so this will go really quick. So, I’m gonna go ahead and click OK. (computer dings) And just like that it finished instantly. Like I said, very small database. So, we’ll go ahead and click OK. So, now we can navigate
to the backup’s location, D drive, MSSQL, Back Ups, and we can see the database
backup that we just took. And like I said before with compression, we can set that at the
instance level as well. So, if I right-click the
instance and go to Properties, and then I go down to Database Settings, Compress backup is already checked, so it’s gonna compress
my backups by default. So, you might want to check
this on your SQL Server instance level as well to
make sure you have it checked. Something else I want to show you is actually a script that you can run, and it will return all the database backups for the previous week. So, in this script that
I just ran we can see the server name, database
name, start time, finish time, the location of the backup
file, and the name as well. The backup type was database. If it was a log it would be ‘log.’ The backup size and
backup set name as well. So, if you want this script as well, check out the description
box of this video. I’m gonna paste a link
to JoshBurnsTech.com. For the blog post
associated with this video it’ll have a code clock
and you can actually copy this code out, paste it
into your environment. Now that we’ve successfully
taken a full database backup, we’re ready to create a Maintenance Plan to automate this process so that we can schedule it and it will run automatically. So, on my SQL Server instance I’m gonna come down to Management, expand it. I’m going to expand Maintenance Plans. You can see I don’t have any
currently. (right-clicking) We’re gonna right-click Maintenance Plans, select New Maintenance Plan, type in a name for our Maintenance Plan. So, this will also be the name for your SQL Server Agent job, so if you go by naming convention for your SQL Server Agent jobs,
be sure to use that here. So, for my naming
convention I’m gonna use uj, which stands for user job, _DBA, (typing) so this places all my DBA jobs together so I can view them all in sequence, _Backup, (typing) _JoshBurnsTech,
(typing) _FULL. (typing) So, the naming convention that I use specifies uj for user job; DBA to place some of my
DBA jobs I create together; Backup, since this is a backup,
maintenance plan, and job; JoshBurnsTech, the
database name we’re using; and then Full for the type of database backup that we’re taking. And now this opened the
Maintenance Plan Design window so we can start designing
our maintenance plan. So, the first thing that I do when creating Maintenance
Plans is change the subplan, and we can do that by double-clicking where it says Subplan_1. (clicking) So, now the Subplan
Properties window is open and we can start modifying it. When we click Save at the end to create the maintenance plan, what this does is it creates a
SQL Server Agent job as well, and what shows up at
the end of the job name after our uj DBA Backup, at the end of that
there’s gonna be a period and then it’s gonna have the Subplan name. So, Subplan_1 is what would
appear there right now. So, for this specific Maintenance Plan we’re gonna name it Cleanup,
(typing) _Backup. (typing) And what I also do is I
copy out the name, (typing) and then I paste that into
the Description. (typing) Now, the only place you’re gonna see the Description is in the Maintenance Plan whenever you open it and you’re
viewing the contents of it. You’re not gonna see it in the Agent job in the name or anywhere like that. So, that’s why I just copy and paste a name into
the Description field, since it’s not really
visible anywhere else, except when you’re viewing
the maintenance plan. Now, we can also set the schedule to have it run automatically. We’re not gonna do that yet. We’re gonna go ahead
and create the contents of the maintenance plan,
add in our different tasks, and then we’ll jump back and
create the schedule after that. Now we’re ready to start building the maintenance plan
and adding in our tasks. So, I’m gonna jump over to
Toolbox on the left hand side of SQL Server Management
Studio, click on it, come down to Maintenance
Cleanup Task, click on it, and then drag it over to our window. Now we can move this
around anywhere we want. I’m just gonna position it right here. So, now I’m gonna jump
back over to Toolbox, come down to Back Up
Database Task, click on it, and drag it over beneath the
Maintenance Cleanup Task. And I’m gonna position it as well. Now we’re gonna click on the
Maintenance Cleanup Task, grab the green arrow, and then connect it to the Back Up Database Task. So, what we just told the
Maintenance Plan to do is when this job executes
it’s first gonna run the Maintenance Cleanup Task to clean up old database backups. We’re gonna go ahead and set the contents and the properties of that up in a moment, but what we’re telling you to do is execute the Cleanup Task first and then move down to the
Back Up Database Task. Now we’re ready to set the properties of the Maintenance Cleanup Task, and to do that we’re gonna click on the Maintenance Cleanup Task (clicking) and then we’re gonna double-click
it. (double-clicking) You’re gonna leave the
Connection as it is, ‘Local server connection.’ You’re gonna leave the ‘Delete
files of the following type: Backup files,’ as is, and now we need to specify where our backup folder resides at. So, where it says ‘Search folder ‘and delete files based on an extension,’ we’re gonna click on the
three dots right here. (clicking)
(soft music) Now we need to navigate to the drive and then the sub=directory
for where our backups reside. So, if you remember, our backups are on the D drive, MSSQL, (clicking) Backups. So, I just opened Windows Explorer, and now I’m gonna navigate
to our Backup folder. (clicking)
(soft music) I’m gonna hit New folder, and then I’m gonna type in
the name of our database, which is JoshBurnsTech.
(typing) (clicking) Now we’re gonna jump back over to our Maintenance Plan. (clicking) We’re gonna minimize
the D drive. (clicking) We’re gonna expand it again, (clicking) and go back to our parent folder, and now click on our
subfolder of JoshBurnsTech. Click OK. (clicking) Now, the file extension part is just as important as selecting
the correct folder. If you don’t put anything in here nothing’s gonna get cleaned up. So, we need to tell it to delete the full backup extension, which is .BAK. So, all you type in is BAK. (typing) ‘Include first-level subfolders,’ we’re gonna leave it unchecked. So, if you just had a specific maintenance plan to delete backups, you could basically
give it a parent folder, have all your different
database subfolders within it, tell it to delete the
first-level subfolder, BAK, Full backup extensions it would go through each of the subfolders and delete the backups based on the retention date that you give it. However, we’re gonna have this specific to the actual database, so we’re gonna leave it unchecked. And then next we need
to specify a file age. So, this is how long we
want to retain backups. The default is four weeks. So, at this rate you’re
gonna keep your backups for four weeks before
any of them get deleted. I’m gonna go ahead and just bump this down to let’s say two weeks. Again, if you’re interested in looking at the T-SQL that’s generated by the Maintenance Plan, click on View T-SQL. You can copy this out, paste it into a query editor window to view it as well. Now we’re gonna go ahead
and click OK. (clicking) Let’s move on now and edit the properties of the Back Up Database Task. So, we’re gonna do the same thing by clicking on it (clicking) and then double-clicking
it. (double-clicking) The Backup type is Full because we’re doing a
Full database backup. We’re gonna select our
Database, so click the dropdown, and then we’re gonna select JoshBurnsTech, and then click OK. (clicking) Backup component is Database, and we’re backing up to Disk, so now we’re gonna click on Destination. ‘Create a backup file for every database. ‘Create a sub-directory
for each database.’ So, this is where we could’ve
created a sub-directory via the Maintenance Plan. We went ahead and did that ourselves, so we’re gonna leave this unchecked. So, we need to click on the three dots, navigate to our Backup directory, and then select JoshBurnsTech, and click OK. (clicking) The Backup file extension
is .BAK for full backups. Again, you can look at the
T-SQL if you would like. Now, we looked at compression
earlier at the instance level. I had it set to compress backups, so any backup that’s taken
on my SQL Server instance, it’s gonna be compressed automatically to save storage space. However, if you didn’t have
this set at the instance level, or you weren’t sure about it, you could click the dropdown
and select Compress backup. Now, what I always do is I just double-check everything I just set, so I’ll jump around, go to Destination, just do a quick glance,
make sure it looks good, General, everything’s good, so I click OK. (clicking) Now we can also
see some of the settings that we just set in the task as well. So, we can see ‘Maintenance Cleanup’ and ‘Local Cleanup,’ ‘Older than 2 weeks.’ Back Up Database Task,
the type is a Full backup, JoshBurnsTech database, and
then Backup Compression as well. So, we have everything set
now except for the schedule. Like I said, we were
gonna come back to it. So, to set the schedule we’re gonna click on the schedule icon right here. As I stated before, this is
part one of a part-two series. We’re gonna assume that the JoshBurnsTech
database is really large, so we don’t want to take
a full backup every night because it’s gonna consume
a ton of storage space. In the second part to this series what we’re gonna do is set up differential and transaction log backups as well, adding those into the mix. That’s gonna give us a
point-in-time recovery, as well as save a lot of storage space. So, the reason I just stated that is because we’re gonna leave
the frequency on weekly, and we’re gonna leave it on Sunday, and we’re gonna leave it at 12:00 AM. Now, you can modify any of
these around that you wish. These are all the ones that we’re gonna leave set for our full database backup in this maintenance plan. So, in the description you can see this occurs every week
on Sunday at 12:00 AM. And it’s important when
you’re setting the schedule, check to see if it’s gonna conflict with any other jobs on your server. It’s best to stagger SQL Server Agent jobs and not have them all kicking
off at the exact same time. And for the maintenance plans
or SQL Server Agent jobs that I create, whether it’s a backup, it’s index maintenance, it’s DBCC CHECKDB, any of those different types of jobs, I also run those somewhere between the hours of 12:00 AM to 4:00 AM. I just stagger them within those windows. That’s typically down time, or not down time specifically, but non-peak hours for my clients, so if I run those type of
jobs during those hours it’s not gonna affect any users. And that’s something
you should keep in mind when you’re scheduling things like this. Don’t schedule these
to run during the day, during peak hours when you have
a ton of user sessions open. Schedule these in non-peak hours. So, now we’re ready to click Save, and when we click the Save option it’s going to create our SQL
Server Agent job as well, which we can find right here. Rather than waiting until
12:00 AM for this to execute, we’re gonna test it by right-clicking it and selecting Start
Job at Step. (clicking) So, now our Agent job
successfully finished and backed up our database,
and we’ll go verify that. So, I’m gonna open up
Windows Explorer again, click on out database, (clicking) and there’s our backup file. (clicking) Now, what we can do to verify the schedule that we created is we can
come to the SQL Server Agent, double-click Job Activity
Monitor, (double-clicking) we’re gonna highlight our job, (clicking) and we’re gonna look
at the Next Run column. So, we can see that it’s set to run on May 19th, 2019, at 12:00 AM. That’s thing upcoming Sunday. Now we can close out of the Maintenance Plan Creation window, and it won’t show up over here, Maintenance Plans, until we do a refresh. And we’ll expand it again, and
there’s our maintenance plan. So, we have our maintenance plan and we have our Agent job
for the maintenance plan, and as I said before,
there’s the .Cleanup_Backup that we added for the subplan. So, we just successfully created a Full database backup maintenance plan for our JoshBurnsTech database. We set a schedule for it to
run on Sundays at 12:00 AM. We set a retention of two weeks, so any backup that’s older than two weeks is gonna get deleted every
time this maintenance plan and Agent job runs, and
we’re ready to go now. Everything is done for
the maintenance plan. It ran successfully, it
scheduled a run on Sunday. We’re good to go. Now that we successfully took
a manual full database backup, we set the maintenance
plan and Agent job up to run it automatically,
we’re ready to do a restore. So, I’m gonna show you how to restore the JoshBurnsTech database from the backup that we just took. I know this should go without saying, however, I’m gonna go
ahead and say it anyway, if you’re gonna test this restore process, make sure you’re in a test environment or you’re running SQL Server
on your own local machine, something like that. Don’t test this on a production machine. You don’t want to overwrite an existing database on accident. So, just make sure that you’re testing this on a test machine or a dev machine, not a production instance. So, to restore the JoshBurnsTech database we’re gonna right-click
it, (right-clicking) we’re gonna go to Tasks, and then we’re gonna click
on Restore and Database. Now, our goal here is to find
the backup that we just took, the full database backup,
we’re gonna restore it. So, for the Source, we need
to change this to Device, and then we need to click on
the three dots. (clicking) And if you have your database settings set correctly at the instance level, it’s gonna automatically take you to where your backup directory resides at, so when I click Device
and click the three dots it took me directly to
my database backups. So, now we need to double-click the JoshBurnsTech folder
to go within it. (clicking) Here’s the backup that we took. (clicking) So, we’re gonna click on it
and we’re gonna click OK. And we’re gonna click OK one more time. So, by switching it to Device
and grabbing our backup, what we did is we switched
it to look at Disk, so we can see the full path to
where our backup resides at. This is the backup we’re
gonna be restoring, and we’re restoring it from this source onto the destination, which is the JoshBurnsTech database. Now, the destination is
extremely, extremely important. No matter what version of
SQL Server that you’re on, always make sure you
check this destination, it’s a best practice. You don’t want to be a
DBA that goes and restores a database without fully
checking all the settings. Restoring a database is
something that’s really crucial. It can go very wrong. You can overwrite databases
that you don’t mean to. There’s just so much that can go wrong, so just make sure you’re following all the right precautions. So, on Destination make
sure your destination is a database that you want to restore. So, as we can see here,
Destination is JoshBurnsTech, that’s the database
that we want to restore, and if you look at the
Restore plan we can see more details about the
backup that we’re restoring. We can see the name, it’s
a full database backup, so we know we’re restoring
the right type of backup. Database was JoshBurnsTech. It shows you the LSNs. Start date, finish time,
and user name as well. So, everything on this
first page is correct, so what we can do now is go to Files, and now these are the files
that we’re gonna be restoring. So, with SQL Server 2008 and newer, what happens on the Files
tab is it automatically detects the files that you’re restoring. You don’t have to change anything here. You just need to come
in and double-check it. I definitely recommend that
you still come here regardless, take a look at the Restore As column, make sure you’re
restoring the right files. So, let’s say we have two databases. We have JoshBurnsTech and
we have JoshBurnsTech_Test. So, the test database is
obviously for testing. We’re gonna do all of our testing
there for the application, make sure everything’s working
well and try new things out. When having a test database, obviously you want to
refresh it from time to time with a copy of your production data. So, obviously in best
practice environments you’re gonna have your production SQL Server instance on its own server, a test SQL Server instance
on its own server, and a development SQL Server
instance on its own server, and in some cases a QA instance as well. However, anyone that works in SQL Server knows you’re gonna have
clients that have tight budgets or the business doesn’t
give them the money they need to have all
these different servers. So, let’s just say for
example we were forced to put the production
JoshBurnsTech database and the test JoshBurnsTech database on the exact same server
and SQL Server instance. Now the time comes you
need to refresh the data. You take a full database backup of your production JoshBurnsTech database and you go to restore it onto the JoshBurnsTech_Test database. We go through all the different
options on the General tab, and then we come to the Files tab. So, what happens on SQL
Server 2005 and previous, so SQL Server 2005 and 2000, on the Files tab what would happen is that the Restore As column for the MDF and LDF would actually have the name of the production database in it. So, it creates a threat that you could actually end up restoring your production MDF and LDF file when you
meant to restore the test, so if for some reason, hopefully not, you work with a client or someone that’s running SQL Server
2005 or SQL Server 2000, make sure you come to this Files tab and make sure that you
change the MDF and LDF names. So, you have to come in here, you would have to click on the three dots beside each one of these, and you would want to
give it a different name. So, just put _Test
before the .MDF and .LDF to make sure you’re not gonna overwrite your production files. Now we can click on the Options tab since everything looked good on Files. Make sure you select Overwrite existing database with replace. So, we’re not restoring any differential or transaction log backups in this video. That’s gonna be part two, so make sure you check out part two of this video that’s gonna be coming
in the next couple weeks. Make sure you subscribe and
hit the notification bell so you get notified about that video, because in that video we’re gonna be working with differential and transaction log backups as well, so what that’s gonna require
is that’s gonna require, so change this option to
restore with no recovery so we can apply those differential and transaction log backups as well when we’re doing the restore
for point-in-time recovery. So, we’re leaving this
as restore with recovery. So, we don’t need to
take a tail-log backup. If you know what this is it’s basically gonna back up everything since the last log backup in the transaction log. We’re just restoring our
full database backup, so we’re just gonna uncheck it. Server connections,
obviously you cannot restore a database that has user
sessions open within it. So, if you had users
connected to a database, best practice is to get the
users to disconnect from it. If you’re running an ERP
application for OLTP, the best case scenario,
get your users out, shut down the services
for your ERP system. That will disconnect all the
sessions from the ERP instance and they won’t reopen once
you have people close. If you select this option to close existing connections to
the destination database, two things I want to point out. Number one, it can take a
long time for this to happen. If you have a lot of user sessions open in the database it could take a while for SQL Server to close those out itself. Second thing, take a look at this. ‘This may leave the destination ‘database in single-user mode.’ If you don’t know what
single-user mode is, this means that whatever session is doing the restore is the only session that’s gonna be open in
that entire database. It won’t allow anything
else to connect to it. If it doesn’t switch back
to multi-user on its own you would have to do that
yourself, likely through T-SQL. So, again, I would recommend just getting your users out of your database. If you have an application
that connects to your database, shut it down while
you’re doing the restore. And obviously that just applies to if you’re restoring a production database. If you’re just doing testing, which we’re doing now,
testing should be easy. You should just be able to get
your users our of the system, or any user that has a session
open in the test database, if they’re running queries,
something along those lines, if you are, just get all
those sessions closed out. So, now what we can do, which we’ve done in previous steps already,
is double-check everything. So, restore options, reset to overwrite. Everything looks good
here, we’ll go to Files. Again, this is gonna be set correctly in newer versions of SQL Server, but we’ll just double-check it anyway. Looks good, and back to the General tab we have the correct database backup, which we can see on Device. We have the correct destination database, which is the most important
thing on this page, and now we’re ready to click OK and restore the JoshBurnsTech database. So, I’m gonna go ahead and click OK. (dings)
(soft music) And just like that, the restore finished. Now, this database was really small. Like I said, it finished extremely fast. If you were restoring a database either a terabyte or larger, this would obviously
take way longer to run. So, we just successfully restored the JoshBurnsTech database
from our full database backup. Now, there’s a lot of ways that you can check the last restore date of a database. What I’m gonna show you is a script. There’s a lot of scripts
similar to this one. I’ll put this one on the
JoshBurnsTech blog post as well, so you can go to that code block, you can copy the script out, and you can run it in your environment. So, we can see the destination
database of JoshBurnsTech and we can see the restore
date, which just occurred, and something else cool that it gives you is the actual backup file for the restore. So, again, this script will
be on JoshBurnsTech.com and a blog post, you can go to it. There’s gonna be a code block and you can copy it out.
(whooshes) So, we just successfully took a full database backup of the
JoshBurnsTech database, we created a maintenance
place and SQL Server Agent job to perform the backup
automatically for us, so we don’t have to manually do it, and then we restored the
JoshBurnsTech database from our full database
backup that we took. In part two of the
series I’m gonna show you how to take differential database backups and transaction log database backups, and then restore those as
well to a point-in-time, so if you had an error
occur in a database, you had corruption or something like that, let’s say it happened 15 minutes ago, I’m gonna show you how you can set up automated plans involving
transaction log backups, differential backups,
and full database backups that will allow you to restore right before the error occurred, preventing your business from
losing critical business data. So, again, if you’re not
subscribed to the channel I highly recommend doing that now so you don’t miss that video. Also, I want you to leave a
comment below on this video with the main version of SQL Server that you’re using right now in production environments
or test environments. As you probably know,
Microsoft is dropping support fully for SQL Server 2008 and 2008 R2 really, really soon, so I want to know what
versions of SQL Server that you guys are working with the most to see how many of you
are on newer versions and how many of you are on
older SQL Server versions. And obviously if you
guys have any questions about anything we just
did, the restore process, setting up the maintenance
plan, any of that, be sure to leave a comment below. I always reply to comments
and I will check yours out. On this end screen I recommend
checking out these videos, and be sure to hit that round Subscribe button for weekly tech videos, and hit that notification bell so you don’t miss anything. Thank you for watching
and until next time. (soft music) (soft music)

Danny Hutson

8 thoughts on “SQL Server | How to Backup and Restore Databases (Part 1)

  1. Compress backup not only saves space, it is much faster to backup/restore as the bottleneck is usually the IO to disk, not the CPU compressing/decompressing. Really Microsoft should make this the default.

  2. @josh burns tech..is it possible to restore that same database on another sql server that are joined together

  3. Want to Learn more about SQL Server? Checkout my Playlist! https://www.youtube.com/playlist?list=PL2RRbYdV_lUTzRCwfY9nTgsiQ7BkVkzoi

Leave a Reply

Your email address will not be published. Required fields are marked *