http://sqlforums.windowsitpro.com/web/forum/default.aspx?forumid=10 FuseTalk.Net (http://www.fusetalk.com) http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=66&threadid=93621 2009-11-18 03:23 PM -07.00 backup exec won't remove your database. it'll just stop taking backups if removed. so you should be good <img src="i/expressions/face-icon-small-smile.gif" border="0"> <br> <br>-- Russell -- <br>------------------------------------------ <br><b>SQL Server Magazine Forum Pro</b> bmorency http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=66&threadid=93621 2009-11-18 01:44 PM -07.00 ok thanks for the tip. My main concern with using the same instance was that if backup exec was removed for some reason I didn't want it to remove the entire DB with my contact data. <br> <br>As for backup I will make backup exec backup the .bak files. <br> <br>Thanks <br> <br> bmorency http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=66&threadid=93621 2009-11-18 01:25 PM -07.00 I'd create a new db on the same instance. <br> <br>As for backups, you should be using native backup to the file system and let symantec tape of the .bak files <br> <br> <br>-- Russell -- <br>------------------------------------------ <br><b>SQL Server Magazine Forum Pro</b> bmorency http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=66&threadid=93621 2009-11-18 12:45 PM -07.00 HI, <br> <br>I have sql server 2005 installed on our sbs 2008 server. I want to install the database for outlook business contact manager on the server but I am not sure if I should create a new instance or not. I have about 1gig or RAM that is either being used as cache or free. <br> <br>But my concern is that I have two instances that were created by symantec backup exec and if I install another instance it will use up a lot more RAM. <br> <br>So my question is should I create another instance for the contact manager DB or use the existing one? I am also worried that if something happens to symantec backup exec the data for the contact manager might also be affected. <br> <br>Any tips? <br> <br>Thanks <br> <br> bmorency http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=66&threadid=93553 2009-11-05 07:11 AM -07.00 Have a look <a target=_blank class=ftalternatingbarlinklarge href="http://www.microsoft.com/learning/en/us/certification/cert-sql-server.aspx">here</a> for information on getting certified. Start with your MCTS. <br> <br> <br>-- Russell -- <br>------------------------------------------ <br><b>SQL Server Magazine Forum Pro</b> christien.jazz http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=66&threadid=93553 2009-11-05 01:21 AM -07.00 i m doin engineering from india. looking for future in database ...nd which course i should study first nd am also looking to certification course in database...so which certification should i give nd from which organisation.thanks christien.jazz http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=66&threadid=92742 2009-10-07 08:08 AM -07.00 Use Pascal Casing ( or Hungarian Naming after Charles Simonyi) like: <br> <br>SalesOrderHeader, SalesOrderDetail, Product, ProductPhoto, ProductDocument <br> <br>If you inherit a table with spaces in name, you will be married to [table name] (square brackets) for ever! <br> <br>Underscore (_) still around in some system table names, kind of old-fashioned. <br> <br> <br>Kalman Toth, SQL Server 2008 Training <br><a target=_blank class=ftalternatingbarlinklarge href="http://www.sqlusa.com">http://www.sqlusa.com</a> tombloom http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=66&threadid=93317 2009-09-25 08:48 AM -07.00 All of the mentioned approaches will work it is really a question of what suites your requirements more. You really need to write down (not here <img src="i/expressions/face-icon-small-smile.gif" border="0"> ) what all your requirements are for all aspects of the enviorment. Things such as how stale can the data be, what limitations do you have, how available all the parts need to be, how long canany given piece be off line and what will the impact be etc. etc. Then list the pros & cons of each of the approaches and see which fits your requirments best. Don't count SSIS out before hand just based on the amount of work to be done. That is what SSIS is designed for and I can assure you there are lots of companies doing extremely heavy massaging of data with SSIS every day. But at the same time there may be a slightly more simple approach that suites your needs as well. But the only way to know is to list every possible issue / requirement and go from there. moflaherty http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=66&threadid=93317 2009-09-25 08:06 AM -07.00 There is a fair amount of conversion and massaging of data that we felt it merited it's own server that is in isolation. The change tracking has some performance overhead as well (based on our testing.) [I know replication does too.] It seemed easier for us to bring the data from three locations into one server, especially because two of the sites are remote on a slow connection. (The plan is to dial up the update interval from once a day to something more often at the two locations and measure the performance.) We also felt that propogating the data into the server does create another potential backup location (though not the driving factor here.) I am ok considering running change tracking at three locations, though I was all excited about managing the code and processing from a single, detached location when I started. <br> <br>We can run the SSIS conversion package on our staging server say every 15m; it does not have to be real time. So I would assume the connection issue could be managed. I was just curious if you or anyone out here had experience with log shipping vs. other Microsoft approaches for syncing remote databases; it sounds like we have a few options with SQL Server and I didn't want to waste the time testing every possible approach if there was a consensus on what works best. If our scenario is not typical, or I can't adequately define the problem out here, we can certainly try everything. Just trying to save some time. <br> <br>Thanks! <br> <br> moflaherty http://sqlforums.windowsitpro.com/web/forum/messageview.aspx?catid=66&threadid=93317 2009-09-24 01:46 PM -07.00 It doesn't have to be a live user as any connection in the db needs to be killed before you can restore the next log. This sounds a little too complicated to get right on a forum post as there are lots of details that need to be considered to determien the correct strategy for your needs. I don't understand why you have a staging server in the first place. Why not use change tracking on each of the primary dbs and use SSIS to grab the data, convert it on the fly and update the target databases all in one shot? moflaherty