Converting a Sybase database to an SQL Server database is a feat that can be accomplished, but there are a number of differences between the two products that must be addressed. Depending on the size of your application, this conversion could turn into a lengthy process. You don't have to rewrite the whole application, but there are a fair amount of show-stoppers.
However, look on the bright side: I can't think of an easier conversion between two major database packages than this one, and a successful conversion is highly probable because of the products many similarities. Happy migrating!
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
SQL Server 
/ 38 
Using Triggers In MS SQL Server
