The T-SQL is very similar, but there are subtle differences that, when going from MS to Sybase, can get you (i.e.: Sybase does not have/allow: set @memvar=value; left() function; cast function). Robert Bradley
Sr. DBA, some big company
cheap prints and oil paintings:
Sybase requires you to use SELECT to set the value of a variable, while MS will accept either SELECT or SET. Because MS supports SET, you can do the neat-o trick of assigning incremental values to rows after the rows were created in MS, but not Sybase.
Alternative to LEFT(): SUBSTRING( , 1, )
Somewhat of an alternative to CAST: CONVERT.
BTW, those three were just some examples of the differences, not a complete list by any means. Other examples are the MONTH and REPLACE functions.
Robert Bradley
Sr. DBA, some big company
cheap prints and oil paintings:
And then we get into UI tools: I haven't used Sybase 12.5, but for earlier versions at least the Sybase tools aren't as full-featured as the Microsoft tools such as Enterprise Manager and Query Analyzer. Robert Bradley
Sr. DBA, some big company
cheap prints and oil paintings:
firstly, microsoft and sybase used to share the the same engine, however over the past years have started to diverger. one big difference is platform... sybase runs on microsoft or unix. a big advantage when you get into enterprise level apps.
microsoft has started to move away in things like pagesize. ms is now 8K sybase is still 2k. many more datatypes in MS than in sybase... things like DTS now exist and you can't forget that honey. can't comment on price. Paul
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.