Hi, Typically the install configuration would have your CF server and your Db server separate anyways.
I think from memory you will find that SQL server will write to your log first, and then to the physical database table. So don't forget to place your log on a fast disk\network as well. The scenario you describe that another sql server will 'kick in' can be dealt with in a number of scenarios. Hardware clustering of your SQL servers for example will allow another to kick in if one server stops. Each solution has its benefits and pitfalls. Many of them being cost $$. A simple cost effective solution may be log shipping.. if you have another server handy. That may mean you have to point your DSN to the different server if things go pear-shaped. You could even try catch a specific database error code and change your DSN in a variable.. Scott Thornton, Programmer Billing Unit, Hunter-New England Area Health Service ext: 51762 p: +61 02 491 51762 m: 0413 800 242 >>> "Steve Onnis" <[EMAIL PROTECTED]> 13/10/2008 10:28 am >>> My network is gigabit so i am hoping it wont be too bad. The database server is currently on a different system to the web server anyway. What i am wanting to know is if the data is written to the MDF file as quickly as it would if it was on the same physical system as the sql server itself, or if there is a delay. I mean redundant as in like a seconday mail server, but sql server. If one sql server goes down, the other one will kick in and take over. Stee -----Original Message----- From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Scott Thornton Sent: Monday, 13 October 2008 8:24 AM To: cfaussie@googlegroups.com Subject: [cfaussie] Re: OT : SQL server over a network HI, There will be an inherent delay in DB access across a network. It will only be as fast as the slowest piece of your network. That's why we put our DB databases on disks in a SAN, all connected up with gigabit ethernet. Pretty much next to the database server in a rack. What do you mean redundant server? You may like to check out the terms "Replication" and "Log Shipping" for making hot-standby by copies of your database. Also clustering sql server for the ultimate in redundancy. Scott Thornton, Programmer Billing Unit, Hunter-New England Area Health Service ext: 51762 p: +61 02 491 51762 m: 0413 800 242 >>> "Steve Onnis" <[EMAIL PROTECTED]> 12/10/2008 10:39 pm >>> Hey guys Just curioud to know if anyone knows if there is a delay between data being written to an MSSQL data file or if it is immediate. I am looking at storing the SQL data files across a network on a file server and just wanting to try and find out any issues this would cause if something was to happen and the sql server died. Would the data be current or is there a latency between actions and writing the data out. Also, if anyone knows of any places to find out how to set up redundant SQL servers, or if anyone has done it them or even if its possible. Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
