Will backing up a particular database from SQL Studio Manager during production hour interrupt other databases within the SQL Server?

I need to backup one particular database during production hours to fix an issue. If i run the backup from within SQL Studio Manager, will it slow down other databases as well? I know it's best to do this after production hours, but we need to fix this ASAP.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
It will slow down everything using the same disk system - maximum disk I/O is the bottleneck. How much depends on your equipment. If your db is not going into large gb figures, you should be OK to take the "risk".
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
No, it shouldn't.  Backup does not require lots of memory or CPU cycle, however, it will generate read IOs which should be fine with any modern server.  If there are resource utilization, under most circumstances, it is negligible.
Anthony PerkinsCommented:
I agree.  Backing up the databases on modern servers has no real impact on performance.
SolarWinds® VoIP and Network Quality Manager(VNQM)

WAN and VoIP monitoring tools that can help with troubleshooting via an intuitive web interface. Review quality of service data, including jitter, latency, packet loss, and MOS. Troubleshoot call performance and correlate call issues with WAN performance for Cisco and Avaya calls

joukiejoukAuthor Commented:
The SQL server is 2005 on win server 2003.
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
That is both outdated, and so the hardware is presumably too. Breaking up might have an effect. Nevertheless, you probably have no choice...
Vitor MontalvãoMSSQL Senior EngineerCommented:
Backup is basically a read operation (read data pages blocks) followed by a write on disk operation performed by sqlwrite process, so backups have small impact in performance specially if the destination drive is not being used by others databases.
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
As Vitor explained, performance could be impacted if you are backing up to a destination where there are database files or log files residing.  If you are writing to a tape or another drive then it should be negligible.  Are you experiencing any performance issues right ow?
Jose TorresCertified Database AdministratorCommented:
Take differentials during business hours.  Will take less time.  Further iterations will take a little longer based on data changes on the database but not nearly as long as taking a full.
Scott PletcherSenior DBACommented:
It depends.  Backing up a small db typically won't have much impact.  Backing up a (very) large db certainly could, but even then it also depends on how much RAM and how many buffers SQL has readily available.  If taking the backup forces memory swaps and/or hard page faults, it would degrade the overall performance of the server.  If not, and you have sufficient I/O capacity, you won't see any loss of performance.

The easiest way to check for this is to look at existing RAM and buffer usage.  If the system is not under pressure, then the backup shouldn't cause a noticeable loss of performance.  If the system is already under max or near max load, then a backup on top on that cause a noticeable slow down for some other task(s).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
As you can see, noone is able to give a definitive answer - because we can't. You'll have to try ;-).
Jose TorresCertified Database AdministratorCommented:
Are you talking t-log backups during the day?
We make production data changes all the time to correct bad data or add data to reference tables or add or modify objects.  For non break fix changes these are scheduled after hours and depending on the changes we will either perform a diff or a full.
First thing we do is perform a t-log backup
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.