Count us in on the disconnecting SQL. My dad's office is setup very basic for a Microsoft Windows based network. Server is a home-built system with an Intel Core 2 Duo 2.13Ghz, 8GB DDR2 RAM, Four Seagate 10k-rpm 136GB SAS disks on a 3Ware 9690SA-4I running in RAID-10 with write cache enabled. Windows Server 2008 Standard 64-bit is installed. The entire machine is built for speed. We have 7 other computers with AC installed to connect to that main server. The other computers are a mix of wired desktops and wireless laptops. We are using Symantec Endpoint for virus and intrusion protection.
We continually have users get kicked out of Amazing Charts and presented with the "browse to database" screen when they try to get back in. Running Amazing Utilities and repairing connections seems to do the trick and then everyone can get back in. My dad is one of the culprits who has about 300 messages in AC inbox, so perhaps it is the same issue as the slow V5 thread. I'll know soon hopefully as my dad is cleaning out his and the other staff inboxes. After that we will try to get brave and upgrade to a 180-day trial of SQL Server 2008.
Is there any reason why AC isn't web-based yet? I would think going to a web-based platform would not only allow you to keep things very stream-lined (think very thin clients) but you wouldn't have the issues of AC disconnecting as much from SQL because that is all handled server-side.
I would LOVE to see AC support MySQL, as that would allow almost everyone to use a very rock-solid and performance driven SQL server without shelling hundreds (or thousands!) of dollars to Microsoft. Personally I will be looking into changing all of our desktops to Linux machines and using RDP to connect our users to this single server for access to AC. I'm just tired of the issues in the "peer to peer" and the "client to server" AC environment.
