M$ SQL verses Sybase

hortoristic · February 18th, 2004, 04:40 PM

I was pushed into a demo to our business are to explain why moving to M$ SQL
from Sybase is such a good move. I'm struggling for ideas to elaborate on -
I'm a programmer not a presentation person.

Anyone got lots of good ideas why it's better to be on M$ SQL instead of Sybase?

_________________________
Joe Horton
Database Developer / Software Engineer
WISHA/Legal Services Software Development
Department of Labor and Industries
Voice (360) 902-5928 fax (360) 902-6200

planoie · February 18th, 2004, 05:00 PM

If you are using or plan to use .NET, the .NET framework has native SQL client classes built into it which make it very fast to talk with MS-SQL databases. Also, visual studio.NET can connect and browse MS-SQL servers with ease making development much easier. (The future version of MS-SQL, code named Yukon, is built on the .NET framework so it will even more tightly integrate with .NET applications further increasing performance.)

sal · February 18th, 2004, 07:11 PM

It is an old product and there is no support for it. I am having to deal with it on a project and it is not as robust as SQL Server.

Also now SQL Server 2000 comes with a free license to SQL Server Report Services. To my understanding and from seeing the product I think that the reports are very simmilar to Access reports as far as the designing goes.

In the long run your company will save money by using only one vendor.

Sal