Article View: bit.databases.mssql-l
Article #2122MS SQL Errors
From: MLipkie
Date: Mon, 24 Apr 1995 00:00
Date: Mon, 24 Apr 1995 00:00
16 lines
1584 bytes
1584 bytes
We are a small insurance company in Chicago Area that uses MSQ sql server as our database. We recently HAD to upgrade to version 4.21A because we added 10 new users to the system and could not buy a license upgrade. We were told that we had to buy the new client side licenses and upgrade the server (nice money maker for you, like you don't already have enough) and I must say that about HALF of my queries had to be rewritten. The inbedded sub selects did not work, the use of a where close in summary reports is now shakey, the list goes on and on. I can not beleive that the system is even remotely SQL complient. Has anyone else had this problem. Also, I can now get some stored procedures to fail with a server memory, read write violation on our two CPU production machne but not our test bed one processor machine. Great, nothing like paying extra money for a test machine when the results are not consistant over two different computers. Next time, I will convince the company to speend the money on a system that has a better track record. The money they spend up fromt will be saved in reengineering upgrade costs.
Technical Details
Message-ID:
<3nfgsc$e6g@newsbf02.news.aol.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f6611,c7635edc28d196e5,start X-Google-Attributes: gidf6611,public From: mlipkie@aol.com (MLipkie) Subject: MS SQL Errors Date: 1995/04/24 Message-ID: <3nfgsc$e6g@newsbf02.news.aol.com> X-Deja-AN: 101523273 sender: root@newsbf02.news.aol.com organization: America Online, Inc. (1-800-827-6364) reply-to: mlipkie@aol.com (MLipkie) newsgroups: bit.databases.mssql-l