Seek42
https://seek42.net:443/phpBB3/

SQL Server Data Migration and Configuration Woes
https://seek42.net:443/phpBB3/viewtopic.php?f=6&t=21805		 Page 1 of 1
Author:  zeroluck [ Thu 02-11-2010 11:43PM ]
Post subject:  SQL Server Data Migration and Configuration Woes
Well, I'm at it again at a local business office, and I am having severe trouble with SQL Server 2005. Has anyone had experience configuring this?

What's going on is I have a MSSQL database on a client machine 'acting' as a server. I bought a Dell T110 tower server with a 2.4 4 core xeon in it to boost their speed and such, plus the machine they had it on was nearly dead, in danger of losing 5-7 years of data.

I have successfully moved the database using the detach and attach method in SQL Server Management Studio. (it's the crude unsophisticated way to move it, but it's quick) The problem: only one machine will connect to the database. Not one machine at a time, just the one machine.

Right now, I have 5 client machines, each of which can connect to the old database server, but when i try to attach them to the new one, only one works. I have tried disabling firewalls, matching configurations exactly, etc. I must be missing something, so if anyone has any experience in this area, it would be greatly appreciated and well recieved.

z3r0
Author:  heretic [ Sun 02-14-2010 2:51PM ]
Post subject:  Re: SQL Server Data Migration and Configuration Woes
Out of curiosity, which machine is able to connect? Is it the same machine that's also acting as a client?
Author:  zeroluck [ Sun 02-14-2010 4:26PM ]
Post subject:  Re: SQL Server Data Migration and Configuration Woes
heretic wrote:
Out of curiosity, which machine is able to connect? Is it the same machine that's also acting as a client?


correction: i can connect from the server (i.e. management studio) and one client. so yes, the client that can connect is a client. that sounds stupid now, but i may have misstated earlier. i actually have this resolved now, but not exactly satisfactorily. by default this application connects via named pipes. i had never had any success with winsock on this application, but after trying it with the working server, and with the new one and using wireshark to analyze the packets, I realized it was sending the SQL sa password in plaintext, and that it was hardcoded into the client program, so the sa password has to be that particular pw for it to run. (very stupid and insecure) but winsock is measurably faster due to less two way communication so it's a good thing that we're on the new system now.

anyway i set the password to that and now its working.

but then i upgraded their quickbooks to the multi-user license 2009 edition that they bought at staples, and it grew the database to 180 megabytes--a size quickbooks support told me is dangerous, and may result in data loss, mostly because of deliberate design sabotage designed to force users to upgrade to the $3000 'enterprise' solution, which uses the term enterprise loosely, as it limits to 30 users... lol... anyway, the owner is pissed due to costs being like 5x higher than anticpated, but everything is nearly working. i just have to hook up the datalink between the SQL program and quickbooks and i'm done.
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
http://www.phpbb.com/