InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 06:26:42 GMT20http://www.sqlservercentral.com/Forums/Topic1453242-384-1.aspxHello,I am wondering if anyone has experience with AppAssure and disaster recovery of SQL Server databases? I have googled (a lot for many weeks) and I cannot find anyone who hassaid anything about using AppAssure to restore databases. The marketing literature says that the database will just be restored perfectly to the point in time of the last snapshot. I am specifically curious if there are any gotchas or caveats that anyone knows of or there literally is nothing for the DBA to do after a disaster when one has AppAssure. Just to clarify, I'm not worried about the data loss between the snapshot and the restore for the sake of this discussion. i want to focus in on whether anything needs to happen after the AppAssure restore of a volume (e.g. reseed identity columns, first aid for SQL Server Replication, etc.) Any thoughts from those who know about AppAssure would be much appreciated.P.S. I don't have the ability to do a mock restore, my management has said they don't want to do that. Trying to duplicate our complex prod environment at home isn't an option either.Thanks.Wed, 15 May 2013 11:42:28 GMTpharmkittiehttp://www.sqlservercentral.com/Forums/Topic1445743-384-1.aspxI'm currently looking into the possibility of configuring a 2008 R2 failover cluster for my organisation. I'm curious as to what I will need to do. Is there some best practices guides or reference material that is a good place to learn about this?Has anyone had any experience with this and got any info on what to do and what not to do? I'm going to be implementing it in a virtual environment. Does that change anything?Thanks for your help.Tue, 23 Apr 2013 19:35:24 GMTDraelithhttp://www.sqlservercentral.com/Forums/Topic1441632-384-1.aspxMy company is implementing Asigra as a backup solution for our server. Does anyone have any experience of using Asigra to generate SQL backups via VSS? How well does it work? Or am I likely to be better off backing up to disk and letting Asigra collect those files?Thanks in advanceFri, 12 Apr 2013 04:53:56 GMTtomgoughhttp://www.sqlservercentral.com/Forums/Topic1440138-384-1.aspxHi Everyone,I Have disabled database mirroring on principal server using below command for restoring database over a mirrored database because it was not allowing me to restore.ALTER DATABASE AdventureWorks2012 SET PARTNER OFF;after executing above command i was able to restore the database , now i want to enable back database mirroringcan some please help me with the steps.Thank you in advance for looking into my post.Mon, 08 Apr 2013 22:33:28 GMTdataboyhttp://www.sqlservercentral.com/Forums/Topic1427213-384-1.aspxHi all, ldf file will maintain all transactions based on recovery mode.but when we can use that ldf file and how?Wed, 06 Mar 2013 00:41:20 GMTkuppurajdpmhttp://www.sqlservercentral.com/Forums/Topic1408619-384-1.aspxWe are replacing our tape backups with something "better", my backup expert tells me that Quantum is the best, especially the deduping functionality. Is anyone using this? My fear is recovery time is going to be way longer than normal. However tapes stink. Thoughts?Thu, 17 Jan 2013 14:29:44 GMTSarah Wagnerhttp://www.sqlservercentral.com/Forums/Topic960026-384-1.aspxI have a production server and a log shipping server which are acting as a primary and secondary server respectively in the log shipping setting. If I create a disaster recovery plan for my production server, what all steps should I includewrt to log shipping?Wed, 28 Jul 2010 07:30:00 GMTSKYBVIhttp://www.sqlservercentral.com/Forums/Topic1213537-384-1.aspxHi There,We are implementing SAN level replication for our SQL Databases. Can you direct me to any links that guides on step by step activities to be done on the DR server to bring up the database.Cheers,GaliTue, 29 Nov 2011 13:50:45 GMTvenk_ithttp://www.sqlservercentral.com/Forums/Topic665105-384-1.aspxIn order to achieve quick failover (and failback) in the event of the loss of a data centre we are considering using SAN based replication (SRDF in this case). This is on physical SQL servers not virtual. The OS and therefore some parts of SQL is installed on the local C drive, whilst the rest of the SQL installation is on SAN drives. SRDF only replicates the SAN drives so how do we keep the C drive in synch across the two servers.?where I see this being a problem is when SQL upgrades are applied as this will make changes to the SAN drives and the C drives and so not all changes made will be replicated. This even applies to minor changes like how many error logs are kept, or default database directories, as these values are reflected in the registry.Does anyone else out there do DR in this way and what procedures do you use to handle this situation?thanks in advancegeorgeThu, 26 Feb 2009 09:17:34 GMTgeorge sibbaldhttp://www.sqlservercentral.com/Forums/Topic1388192-384-1.aspxI'm going on an extended holiday soon. (NZL :-D)It's so happens that I had to restore this week.Combining the 2 previous sentences, I came up with a question.Who will do restores (If needed) when I'm away?Turns out none of my colleagues knew how. So, "How to" documentation time! All is well again, until the question : But how will that affect the replication?After a bit of research, I couldn't give a proper answer.As far as i'm concerned you don't overwrite DBs when restoring. Rename and/or recreate the publications via "Generate Scripts...".Therefore you shouldn't need to take any extra steps. But according to MS then you should restore the system databases at the time you restore your user DB.This sounds a bit dodgey to me. What about all the changes to any other DBs or jobs changed created between the backup of the troublesome DB and the point it needs to be restored to?One DB per instance? Doesn't sound very handy.So what am I not getting here. I have never had to do File restores so don't know how this fits in.Never restore using REPLACE? When testing this, it worked ok on a subscriber. Replication kicked in again after updating a published table.Restoring a publisher with REPLACE, KEPP_REPLICATION did not go so smoothly. Had to recreate the replication.Does anyone ever restore a DB with overwrite? Or does this just earn you a spanking?Now i'm not sure if our backup strategy is sufficient.Your wisdom and experience in this would be much appreciated.(Sorry about the long post, got a bit carried away....:-P)Resources:[url]http://msdn.microsoft.com/en-us/library/ms151152.aspx[/url][url]http://msdn.microsoft.com/en-us/library/ms151152%28v=sql.90%29.aspx[/url][url]http://msdn.microsoft.com/en-us/library/ms152560.aspx[/url]Fri, 23 Nov 2012 09:03:30 GMTDennis Posthttp://www.sqlservercentral.com/Forums/Topic1385599-384-1.aspxEnvrionment:1. 1 Production server (VMWare, Server 2008, SQL Server 2008 R2 Enterprise)2. 1 SAN ( SQL server storage allocated 3.5TB (600GB SAS drives X 12)) 3. 100 databases (avg size 25GB, largest DB 980GB, sum DB sizes 2.6TB)Currently:SQL Server OS vmdk has image level snapshot copied to archive, to be stored offsite daily.Backups made of critical databases: Full daily, 15 minute trans; Full weekly, daily diffs, 15 minute trans; Daily Fulls; Weekly Fulls; Monthly Fulls with Daily diffs, in order of criticality and Acceptable Loss policy.Backups stored on seperate server (not on SAN, not virtualised, Unix)Differences between backups copied offsite, weekly full sync of all databases.Scenario 1: Full server failure and all database destruction.Best way to mitigate this? Best practice?My intention is to have a secondary server offsite in standby mode ready with latest backups restored in read-only mode (much like log shipping, but bulk imports are recorded too).Scenario 2: Individual Database corruption of 1 or more databasesBest practice?My SQL Server can restore a database to a point in time prior to detected corruption, if corruption is within Acceptable Loss policy restrictions.If only a table is corrupted, a restored database to a different server can be used as a source to repair the affected table.These are the two main scenarios, total server failure, and undetected corruption, and I was wondering if this is as good as it gets?The last time we had to do a restore of one of the larger databases it took 8 hours. We used VDI devices, striped across as many stripes as we have CPU's. If I had to restore all my databases to recover from Scenario 1 it would like take more than 24 hours. What's the best way to get the users back to work fast?If you have had the unfortunate experience of needing to rebuild a whole server, with recovery using restores, or other ways, give us a detailed description of what went wrong (scenario), what you needed to do (number of databases, size of data) and how long it took and what hardware you had it on. Also what you do differently now that you have had this experience.Fri, 16 Nov 2012 04:39:46 GMTAlocytehttp://www.sqlservercentral.com/Forums/Topic1380263-384-1.aspxScenario:I have Databases which are backed up every night (Full Backup); the Backups are saved on a Tape then deleted from the Sever after three days. 1.The Backups are taken at 8pm the previous day and if something goes wrong, for example at 4ppm the next day I would have to Restore the last Backup then rerestorell the Log files since the last Backup (The Log Backups are done every 15 minutes), imagining the Database will need to be Back online as soon as possible; the procedure will take a very long time.I wanted to know if there is a better way of performing a Disaster Recovery other than the following Procedure: RESTORE DATABASE DB_TestLSN_RestoreFROM DISK = 'c:\Backup\DB_TestLSN.bak'WITH MOVE 'DB_TestLSN' TO 'E:\MSSQL\DATADB_TestLSN_Restore.mdf',MOVE 'DB_TestLSN_log' TO 'F:\MSSQL\LOG\DB_TestLSN_log_Restore.ldf',NORECOVERY, NOUNLOAD, STATS = 10GORESTORE LOG DB_TestLSN_RestoreFROM DISK = N'C:\Backup\DB_TestLSN_LOG1'WITH NORECOVERY, NOUNLOAD, STATS = 10GORESTORE LOG DB_TestLSN_RestoreFROM DISK = N'C:\Backup\DB_TestLSN_LOG2'WITH RECOVERY, NOUNLOAD, STATS = 10GOAnd so on until the last log is Restored.2. Is there a way, if possible just to restore a single table if for example something gets deleted or if the table becomes corrupted?Thank you in advance!Fri, 02 Nov 2012 04:37:17 GMTtt-615680http://www.sqlservercentral.com/Forums/Topic1383460-384-1.aspxI'm in the process of implementing a Data Warehouse.I have a Staging Database and a DatawArehouse Database.I have data feeds from DB2, Oracle and SQL Server.The DB2 feed is very large, from a remote location and the bandwidth is slow.I have the Staging Database set to Simple Recovery primarily because I want to minimize the load time to fit within a narrow window.I currently have the Data Warehouse Database set to simple recovery model.It was suggested that I use log shipping as a Disaster Recovery methodology but for obvious reasons that is not going to work.I was considering Mirroring and Snapshot Replication but it is my understanding that Replication was not intended to be a DR Solution?Any thoughts on this?Sun, 11 Nov 2012 12:24:59 GMTWelsh Corgihttp://www.sqlservercentral.com/Forums/Topic892880-384-1.aspxI'm in the process of putting together a DR solution and was wondering who has used 3rd party software for replication of their SQL system. I just watched a webcast about CA's XOSoft aka ARCserve Replication and High Availability which is replication technology for the whole network. CA touts it's a High Availability solution for ANY application or ANY server (Virtual, MS, Linux etc.). Sounded great but I didn't know what kind of impact some of these applications have on SQL or what benefits they have over or don't in comparision to SQLs native replication processes. They said it provides realtime replication and failover for a "seemless" transition in case of diaster. Any thoughts?Tue, 30 Mar 2010 08:54:45 GMTAVBhttp://www.sqlservercentral.com/Forums/Topic1373240-384-1.aspxNot long ago I came across a graph plotting acceptable system downtime and acceptable data loss in an easy-to-understand format in the context of disaster recovery. The idea of the presentation was that acceptable maximum downtime limits and maximum data loss limits should be agreed with the business/customer in the SLA, and these thresholds guide the DBA's disaster recovery strategy.I've seen this graph/concept before in a couple of places, and it has a specific name, too, but it's eluding me. Does anyone know what I'm talking about and can post a link or more details (or did I just dream the whole thing up?)Thanks!Tue, 16 Oct 2012 07:24:20 GMTderek.colleyhttp://www.sqlservercentral.com/Forums/Topic1369105-384-1.aspxHello all,My manager just create a new project for implementing SQL Server using Amazon RDS. He asked me to develop a plan on how to do it, choose the best scenario in terms of cost, performance, latency, disaster recovery, etc.As till now, Amazon RDS - MultiAZ deployments are not yet supported to any version of SQL Server, what are your thoughts on how to get the less downtime possible?I'm a little bit confused about it as I see a lot of marketing but no example or suggestions for SQL Server....Thanks you all in advance for any help.CheersFri, 05 Oct 2012 08:42:03 GMTjoao.loretihttp://www.sqlservercentral.com/Forums/Topic1364336-384-1.aspxhii need to know ,what will you do for disaster recovery for your database.i need any article and anything you have .thanksTue, 25 Sep 2012 16:08:20 GMTharri.reddyhttp://www.sqlservercentral.com/Forums/Topic1312275-384-1.aspx[b]Can’t remember your Windows 7 password? [url=http://www.windowspasswordreset.net/article/forgot-windows-7-password.html]Forgot Windows 7 password[/url]?[/b]Question1: I set my user login password on Windows 7. After setting new password, I just forgot it. Now I start my computer, then login windows appears and asks me password. Thus I could not be logging in system, please help as soon as possible!Question2: I totally omit my Windows 7 password to log on my laptop…I am the only user…it’s not letting me to log on and I didn’t do a password hint, how should I do?Every single day I read posts about lost passwords. Yes, it can happen that people forget even they use them on a daily basis. Today, in this article I’d like to share some effective ways to reset forgotten Windows 7 password. (Note: This ways could be suitable for other Windows operating systems too such as Windows XP, Vista, 2000, 2003, 2008 etc.)[b]Efficient and safe ways to reset forgotten Windows 7 password[/b]If you unremember Windows 7 password, then follow the below ways, you will be guaranteed to regain access to your Windows 7 machine![b]Method 1:Reset lost Windows 7 password with Windows password reset disk.[/b]A forgotten or lost Windows 7 password can be easily and quickly reset by a created Windows password reset disk. Below are the simple steps:If you enter the wrong password when you attempt to log on, Windows displays a message that the password is incorrect. Click “OK” to close the message.Click “Reset password”, and then insert your password reset disk.Follow the steps in the Password Reset Wizard to create a new password.Log on with the new password. If you forget your password again, you can use the same password reset disk. You don't need to make a new one. However, you may ask: “What if I don’t have such a disk?” Well, take it easy, you can resort to other ways.[b]Method 2: Try Windows 7 built-in Administrator to break forgotten Windows 7 password.[/b]There is a built-in Administrator account on any Windows operating system. It is hidden without a password protected by default. This is way you cannot see it or even do not know it either. If you didn’t ever set a password for it and you can unhide it to break your forgotten Windows 7 password.Firstly, you start your computer and press “Ctrl+Alt+Delete” twice at the Login Screen.Secondly, you just type Administrator in the username box and leave the password box blank.Thirdly, you hit Enter key and then log into Windows system.Finally, you go to “Start->Control Panel->User Accounts” to change the forgotten password.[b]Method 3: Reset Windows 7 password with [url=http://www.windowspasswordreset.net]Windows Password Reset.[/url][/b]If you cannot regain access to your locked Windows 7 machine with the above 2 methods, then using a professional Windows password reset tool like Windows Password Reset is the best choice. Below are the simple steps to use this tool:Step1: Get Windows Password Reset Standard from: http://www.windowspasswordreset.netStep2: Create a CD/DVD Windows password reset disk with the tool.Step3: Boot your locked computer from USB or CD/DVD.Step4: Select a user you want to reset its password.Step5: Click Reset button to start Windows 7 password reset.Step6: Reboot computer and login with blank password.Wed, 06 Jun 2012 21:57:45 GMTtengzong0214http://www.sqlservercentral.com/Forums/Topic1316492-384-1.aspxWe are currently looking at options for a new database which will be mainly storing BLOB data and what our options are for DR.This is what I know far.DB has grown to 1 terabyte in a year.SQL Server 2008 R2 EnterpriseDon't have details on daily activity yet, so no idea if a heavy insert or update environment yet.But we need to have some form of DR in place.We have four options;ClusteringMirroringThird Party / customSAN replication.And whether to use Filestream or have "pointers" to he BLOBs.So the question is has anyone had experience of mirroring / clustering with the BLOBs as part of the Database, and any issues concerns?Or should we be looking at storing the BLOBs outside the DB.My feeling is as Filestream and use Clustering or mirroring, but this is probably dependent on the through put of the data? is there much latency with BLOB data and mirroring for example?Goggled this and found a white paper from MS on RBS but this doesn't seem to cover DR.Any thoughts?Cheers,Rodders...Fri, 15 Jun 2012 04:59:16 GMTrodjkiddhttp://www.sqlservercentral.com/Forums/Topic1205163-384-1.aspxIn case of a Log Shipping, I'm aware that if you do if you do T-Log backup maybe through maintenance plan on the same machine (Primary), it will break the log backup chain on the secondary machine that receives the log.However, in case of DB mirroring, if you do T-Log backup on the Mirroring Principal, does that break the log chain on the Mirroring Partner?Mon, 14 Nov 2011 07:59:59 GMTJakeSAhttp://www.sqlservercentral.com/Forums/Topic1272469-384-1.aspxHi All,We need a favour from your side. It is regarding mirroring setup in our environment what happens if for any reasons like n/w fluctuation mirroring get disconnected it’s not giving retry for synchronising with mirror database if we do the manual failover of resources at DR side then it get restarted but automatically it’s not retry for syncing.Please provide your expert comment regarding in this matter.Regards,SachinMon, 26 Mar 2012 01:13:04 GMTdbasachinkumarhttp://www.sqlservercentral.com/Forums/Topic908575-384-1.aspxI have this really annoying problem.I've had to reconfigure log shipping for a no. of dbs. I have 3 distinct servers, prim, 2ndary, monitor.I unchecked log shipping from the primary db, checked all meta data was deleted from all, checked jobs were deleted, rebacked up, restored & reconfigred log shipping. The backup job worked fine. @ 1st the copy job failed. I noticed missing meta data from monitor & 2ndary & inserted this - not ideal, but I've tried this many many times now via SSMS.Now, the jobs all work BUT, on the monitor server & 2ndary, the last copied file / date & last restored file / date fields in the log shipping tables (that I inserted, leaving these fields as null), doesn't update.Any ideas?Prob tables are:mon: log_shipping_monitor_secondary2ndary: log_shipping_monitor_secondary log_shipping_monitor_secondary_databasesOpen to ANY ideas!!Thank you.Thu, 22 Apr 2010 07:10:40 GMTbaby_cheeseshttp://www.sqlservercentral.com/Forums/Topic935967-384-1.aspxHi I need to recover data from .LDF file whereas I have lost my .MDF file. My database was in Full Recovery Mode, I have full backup of a day back, but no transactional backup. Having full backup of Thursday, changes made in database on Friday. I dont have any backup of Friday, I need to recover till Friday. How can I overcome this problem, I have only .ldf file, please give me some solutions. Thanks in advance.Fri, 11 Jun 2010 06:50:01 GMTbeejug1983http://www.sqlservercentral.com/Forums/Topic1074735-384-1.aspxHi allWe have a scenario like we have 6 physical boxes on which sql server is running and no of dbs are approx 200.Now we are planning a DR for all these dbs.Can you pls suggest me best solution for this condition?We are planing to build a single high end vmware servers and make it a DR server for all through Metro clustering,is it possible?or just create a consolidation server and move all 6 boxes into one box and create a single DR box in separate location ?Tue, 08 Mar 2011 06:20:27 GMTManvendrahttp://www.sqlservercentral.com/Forums/Topic1238803-384-1.aspxWhen log shipping is out of sync and we try to restore the transaction logs ,it gives error that the LSN number.....is too late to restore, try a earlier one.And at that time how can we know the LSN number of the transaction logs (which to be applied).Thu, 19 Jan 2012 09:09:23 GMTreggie burns-317942http://www.sqlservercentral.com/Forums/Topic1211093-384-1.aspxDoes anyone know if one database can be mirrored to two different locations with the generic database mirroring set up?Please advise.Wed, 23 Nov 2011 08:41:06 GMTspenn6367http://www.sqlservercentral.com/Forums/Topic1205237-384-1.aspxMy understanding is only the t-log backup will truncate the log and delete the inactive log entries in the t-log, but I still encounter DBAs who say the full database backup will do so for its t-log. Anyone know for sure?Mon, 14 Nov 2011 08:50:54 GMTJakeSAhttp://www.sqlservercentral.com/Forums/Topic1177603-384-1.aspxI have synchronous mirroring between Win 2008 R2 64 bit and Win 2003 Std 32 bit. Both are running Windows 2008 R2 32 bit.When doing Windows update on the mirrored servers, can someone advise what steps can be taken that will not require breaking the mirroring and re-setting up the mirroring after Windows update please? Links are appreciated if available. Thanks!Mon, 19 Sep 2011 20:21:49 GMTgeuncho6http://www.sqlservercentral.com/Forums/Topic837623-384-1.aspxhow many DR types there are? could you name 3 of them?Mon, 21 Dec 2009 15:56:34 GMTbluepaperbagshttp://www.sqlservercentral.com/Forums/Topic1170245-384-1.aspxI have mirrored databases at an off-site location and perform daily full back-ups burnt to disc how safe is my plan.What do you recommend?Tue, 06 Sep 2011 04:47:32 GMTkapfundestanleyhttp://www.sqlservercentral.com/Forums/Topic1170274-384-1.aspxHello,looking for a better insight into this error.My other databases are already mirrored if i want to reconfigure the mirroring this error keeps popping up.After numerous and painful repeats my mirroring is re-established.Tue, 06 Sep 2011 05:26:43 GMTkapfundestanleyhttp://www.sqlservercentral.com/Forums/Topic1170260-384-1.aspxI have a mirroring session working fine,stops whenever my domain machine is down.Is it possible to have a set-up so that my mirroring is always up regardless of whether the domain machine is up or down.Appreciate your advice.Tue, 06 Sep 2011 05:11:55 GMTkapfundestanleyhttp://www.sqlservercentral.com/Forums/Topic1168626-384-1.aspx(sql2005EE sp3)Someone just launched BACKUP LOG WITH TRUNCATE_ONLY for his database.( I know, I shouldn't have provided dbo auth, but you know how that goes )Apparently the default trace doesn't record this event :-(In the instances errorlog file it only states:[quote]MessageBACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.[/quote][b][msdb].[dbo].[backupset] Doesn't record this breach :angry: [/b]Of course, regular scheduled log backups fail after this event because of the lack of a valid full backup.For now I've launched a trace to capture "audit backup/restore events", so I'll know the origin by tomorrow :cool:[u]The question is: [/u][b]Where and how could I have discovered / prevented this ?[/b]Thu, 01 Sep 2011 06:50:04 GMTALZDBAhttp://www.sqlservercentral.com/Forums/Topic1143331-384-1.aspxIn regard to physical tape/drive backups, what are the mandatory regulations relating to data backup. I'm aware of standards such as FDA and SOX compliance, but I believe they are voluntary compliance standards, not mandatory, such as the data protection act. Currently, I physically take a tape backup each night, in protection against damage/destruction to the main office - so does my accommodation need to be compliant in any way?Mon, 18 Jul 2011 05:05:11 GMTrobertprice45http://www.sqlservercentral.com/Forums/Topic1120894-384-1.aspxcan i apply the service pack if some database are in restoring state. Regard's----------shenkar gadeTue, 07 Jun 2011 05:28:26 GMTshenkar.ghttp://www.sqlservercentral.com/Forums/Topic1141497-384-1.aspxHIAny any one could you help me..Encrypt the two column in table. in sql server 2005Example :Table Name: Accontcolum : ssn int, bdate date need two column encryption with certifcate level..Help meThaksJerry Thu, 14 Jul 2011 00:54:14 GMTsolomon.jernashttp://www.sqlservercentral.com/Forums/Topic1136941-384-1.aspxIn SQL Server 2008, if database mirroring breaks for some reason, and you want to resume mirroring with the principal again taking on the role of the principal after the mirroring temporarily served as principal, do you need to go back to square one? Meaning do you need to do full backup and t-log backup of the principal database and restore it on the mirror with no recovery? Or can you just run the below on the principal without without going back to square one:[b]Use Master;GOAlter Database MyDB Set Partner Resume;[/b]I belive going back to square on would not be needed, and above command or simply click Resume in Database Properties > Mirroring Page.Tue, 05 Jul 2011 17:38:04 GMTgeuncho4http://www.sqlservercentral.com/Forums/Topic1121540-384-1.aspxDear All, Dear All, I am working as Junior DBA in a banking domain , in our environment we have a database mirroring and replication and SQL version is 2005 with SP@. now this is big task for me . Database mirroring is : high safety with witness serverReplication : transaction replication.Please help me for the following topics :How to me monitor the mirroring performance and failover.?How to me monitor the mirroring performance and errors failover?regards -----------shenkar gadeWed, 08 Jun 2011 00:53:49 GMTshenkar.ghttp://www.sqlservercentral.com/Forums/Topic1128902-384-1.aspxHi , how can i find out the SQL server memory used by session wise ?Tue, 21 Jun 2011 05:33:43 GMTshenkar.ghttp://www.sqlservercentral.com/Forums/Topic1117729-384-1.aspxI have been tasked with updating our DR documentation, which has gotten woefully out ofdate. My only question concerns the resource database. In SQL Server 2005, it was among thesystem databases and had to remain in the same location as the master database. In SQL Server2008, it was moved to the bin folder in the SQL Server install directory. Am I correct in assuming that the resource database contains only objects, but no data? If this is so, can I safely ignore this database for purposes of DR, as long as my DR server is at the samerelease level(service pack, CU, etc.) as my production server? If I must account for the resourcedatabase, how do I go about it. I know I cannot backup the database, but must copy the dataand log files, but do I need to shutdown SQL Server before I do the copy? What order do I do therestore? Do I restore the master database first, then the resource database, or do I restore theresource database first, then the master?Tue, 31 May 2011 13:58:44 GMTBrian Brown-204626