July 25, 2011 at 10:28 am
Gianluca Sartori (7/25/2011)
Ninja's_RGR'us (7/25/2011)
There's just no reason to shutdown the server to take a backup.... unless you're working with Oracle. :Whistling:
It's called "cold backup" and it's advertised as "the only consistant backup". Strange, isn't it?
halifaxdal, if you have an Oracle background, forget everything you know about backups: it's a totally different story with SQL Server.
What??!? And they claim to be ahead of sql server :sick:
July 25, 2011 at 10:30 am
halifaxdal (7/25/2011)
Brandie Tarvin (7/25/2011)
halifaxdal (7/25/2011)
SSMS is not reliable and it's very buggyWhat sort of problems are you having with it? If you post detailed problem descriptions / error messages, we might be able to assist you more.
Thank you, too many trivial things, fixable but annoying
Annoying is never trivial. There may be a service pack to fix your problem. Or it might be a case of you using a task for a purpose it wasn't meant for. We can help you if you let us. Then you never need fear SSMS again.
July 25, 2011 at 10:32 am
Ninja's_RGR'us (7/25/2011)
Gianluca Sartori (7/25/2011)
Ninja's_RGR'us (7/25/2011)
There's just no reason to shutdown the server to take a backup.... unless you're working with Oracle. :Whistling:
It's called "cold backup" and it's advertised as "the only consistant backup". Strange, isn't it?
halifaxdal, if you have an Oracle background, forget everything you know about backups: it's a totally different story with SQL Server.
What??!? And they claim to be ahead of sql server :sick:
They are.
In prices, mainly. 😀
-- Gianluca Sartori
July 25, 2011 at 10:32 am
halifaxdal (7/25/2011)
Ninja's_RGR'us (7/25/2011)
halifaxdal (7/25/2011)
Roy Ernest (7/25/2011)
I am not sure why you want to do this. You can just take back ups. On SSMS, you can use the maintenance plan to set up Back up of DB. But just because you took a back up does not mean that it is safe. You have to make sure that the Back up is valid and not corrupted. The best way to do it is to restore it to another server.In the maintenance plan, you can set up daily Job for back up and also log back up (Once ever 1 hr or any other interval depending on your SLA). If you can apply these log back ups to another server, then you have a Standby server as well. This will help you in disaster recovery.
All jobs are stored in MSDB.
SSMS is not reliable and it's very buggy
err NO.
Maintenance plans used tobe buggy. But it still works better than copying files manually.
This is the best AFAIK.
You are right, the server needs to be made offline for a while, this approach applies to only small server/DB.
BTW: no one has answered my question, where is the job stored in SQL?
How large is your DB?
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
July 25, 2011 at 10:35 am
Gianluca Sartori (7/25/2011)
Ninja's_RGR'us (7/25/2011)
Gianluca Sartori (7/25/2011)
Ninja's_RGR'us (7/25/2011)
There's just no reason to shutdown the server to take a backup.... unless you're working with Oracle. :Whistling:
It's called "cold backup" and it's advertised as "the only consistant backup". Strange, isn't it?
halifaxdal, if you have an Oracle background, forget everything you know about backups: it's a totally different story with SQL Server.
What??!? And they claim to be ahead of sql server :sick:
They are.
In prices, mainly. 😀
Let's not reactivate this religious war... don't have time to really get into it ATM :w00t:.
July 25, 2011 at 10:47 am
You're right.
I'll stop it here. Would have lots to say, but I'll stop it here. 😉
-- Gianluca Sartori
July 25, 2011 at 10:51 am
I got this idea from Mark Armer, I agree that in some/or many cases SQL cannot be stopped however I still think his idea is surprised, unexpected and workable especially to some non-critical databases/servers.
July 25, 2011 at 10:53 am
halifaxdal (7/25/2011)
I got this idea from Mark Armer, I agree that in some/or many cases SQL cannot be stopped however I still think his idea is surprised, unexpected and workable especially to some non-critical databases/servers.
No it's not.
I've taken millions of backups and I NEVER had to shutdown a server to do it. This is no merit whatsoever unless you can show me a very specific case with weird requirements in it.
July 25, 2011 at 11:02 am
halifaxdal (7/25/2011)
I got this idea from Mark Armer, I agree that in some/or many cases SQL cannot be stopped however I still think his idea is surprised, unexpected and workable especially to some non-critical databases/servers.
I agree it would work for those. And it's definitely out-of-the-box thinking and all that. I just can't see the merit to it. Yes, you can safely stop the server if it's not in use, but the question becomes why bother? It's more work, it doesn't scale well, and there's no benefit to it that I can see.
It probably isn't hurting anything, except taking more work to do, so go ahead with it if it solves some problem for you. But it does make me curious as to what benefit you get from it that you can't get by just issuing "backup database" commands.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 25, 2011 at 11:19 am
Gianluca Sartori (7/25/2011)
Ninja's_RGR'us (7/25/2011)
Gianluca Sartori (7/25/2011)
Ninja's_RGR'us (7/25/2011)
There's just no reason to shutdown the server to take a backup.... unless you're working with Oracle. :Whistling:
It's called "cold backup" and it's advertised as "the only consistant backup". Strange, isn't it?
halifaxdal, if you have an Oracle background, forget everything you know about backups: it's a totally different story with SQL Server.
What??!? And they claim to be ahead of sql server :sick:
They are.
In prices, mainly. 😀
And EGO
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 25, 2011 at 11:20 am
I have to agree with Gus & Ninja. Yes, you can do it, but there are so many things that can go wrong with that method (like accidentally deleting the files instead of copying them) that I just don't care to risk my databases to do it.
I've only ever used this method on non-Production databases when I'm doing "screwy stuff," and never as an actual method of backup.
Besides, you can't restore to Point in Time using this method.
July 25, 2011 at 12:13 pm
It's always good to have multiple options to accomplish a task, but in this case there are several detriments to the proposed method, with no obvious advantages. If you want to copy the file for some reason instead of running proper backups, I would suggest detaching the DB, copy, then re-attach. At least this way you do not affect other databases that may need to stay online, or actively running jobs..
July 25, 2011 at 12:18 pm
Please not he said COPY and not MOVE. If something bad happens during the move you lose the DB, copy is safer there.
July 25, 2011 at 12:24 pm
I wouldn't advise such approach, just because of the reasons mentioned by the previous replies.
Best is to have an alike approach on _all_ your instances so anyone helping out doesn't have to guestimate but just has to confirm the procedure.
It is hard to get rid of bad habits, so do it properly, even for tiny instances.
Copy/paste attitude will cause this also to happen on large ones :crazy:
Besides that, keep in mind sqlserver will have to rebuild its cache (datapages, sqlplan, ...) and will start with a very small tempdb, needing to expand fairly soon ( unless you sized it )
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
July 25, 2011 at 12:28 pm
Ninja's_RGR'us (7/25/2011)
Please not he said COPY and not MOVE. If something bad happens during the move you lose the DB, copy is safer there.
Ninja, I'm sorry, but this reply makes no sense to me. Could you rephrase?
Viewing 15 posts - 16 through 30 (of 37 total)
You must be logged in to reply to this topic. Login to reply