<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="https://www.sqlines.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://www.sqlines.com/feed.php">
        <title>SQLines Tools sybase-asa-to-sql-server</title>
        <description></description>
        <link>https://www.sqlines.com/</link>
        <image rdf:resource="https://www.sqlines.com/lib/images/favicon.ico" />
       <dc:date>2026-04-20T16:40:26+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://www.sqlines.com/sybase-asa-to-sql-server/call?rev=1727893280&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.sqlines.com/sybase-asa-to-sql-server/constraint_names?rev=1458142297&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.sqlines.com/sybase-asa-to-sql-server/dateformat?rev=1376338123&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.sqlines.com/sybase-asa-to-sql-server/list?rev=1727793379&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.sqlines.com/sybase-asa-to-sql-server/message?rev=1729088050&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.sqlines.com/sybase-asa-to-sql-server/sqlstate?rev=1728057951&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.sqlines.com/sybase-asa-to-sql-server/sqlstatus?rev=1728078008&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.sqlines.com/sybase-asa-to-sql-server/top?rev=1727864964&amp;do=diff"/>
                <rdf:li rdf:resource="https://www.sqlines.com/sybase-asa-to-sql-server/update_alias?rev=1727553017&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://www.sqlines.com/lib/images/favicon.ico">
        <title>SQLines Tools</title>
        <link>https://www.sqlines.com/</link>
        <url>https://www.sqlines.com/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="https://www.sqlines.com/sybase-asa-to-sql-server/call?rev=1727893280&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-02T18:21:20+00:00</dc:date>
        <title>CALL Statement - Sybase SQL Anywhere to SQL Server Migration</title>
        <link>https://www.sqlines.com/sybase-asa-to-sql-server/call?rev=1727893280&amp;do=diff</link>
        <description>Sybase SQL Anywhere CALL statement allows you to execute a stored procedure, while you have to use EXEC statement in SQL Server. Note that EXEC does not allow specifying parentheses around procedure parameters. 

Sybase SQL Anywhere:


  -- Sample procedure
  CREATE PROCEDURE greetings(IN @name VARCHAR(30))
  BEGIN
    SELECT 'Hello, ' + @name + '!'
  END;

  -- Execute the procedure
  CALL greetings('world');
  # Hello, world!</description>
    </item>
    <item rdf:about="https://www.sqlines.com/sybase-asa-to-sql-server/constraint_names?rev=1458142297&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-03-16T15:31:37+00:00</dc:date>
        <title>Constraint Names - Sybase SQL Anywhere to SQL Server Migration</title>
        <link>https://www.sqlines.com/sybase-asa-to-sql-server/constraint_names?rev=1458142297&amp;do=diff</link>
        <description>In Sybase SQL Anywhere (Sybase ASA), constraint names are unique per table while in SQL Server they must be unique within the database.

Sybase SQL Anywhere:


  CREATE TABLE sales 
  (
     id INT,
     name VARCHAR(100),
     CONSTRAINT id_unique PRIMARY KEY (id)
   ); 
   -- Ok
   
   CREATE TABLE orders 
   (
     id INT,
     name VARCHAR(100),
     CONSTRAINT id_unique PRIMARY KEY (id)
   ); 
   -- Ok</description>
    </item>
    <item rdf:about="https://www.sqlines.com/sybase-asa-to-sql-server/dateformat?rev=1376338123&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-08-12T20:08:43+00:00</dc:date>
        <title>DATEFORMAT Function - Sybase SQL Anywhere to SQL Server Migration</title>
        <link>https://www.sqlines.com/sybase-asa-to-sql-server/dateformat?rev=1376338123&amp;do=diff</link>
        <description>In Sybase SQL Anywhere (Sybase ASA), DATEFORMAT function converts a datetime value to a string using the
specified format. 

In SQL Server, you can use CONVERT or CAST functions to convert a datetime value (DATETIME, DATETIME2 data types i.e.) to a string.</description>
    </item>
    <item rdf:about="https://www.sqlines.com/sybase-asa-to-sql-server/list?rev=1727793379&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-01T14:36:19+00:00</dc:date>
        <title>LIST Function - Sybase SQL Anywhere to SQL Server Migration</title>
        <link>https://www.sqlines.com/sybase-asa-to-sql-server/list?rev=1727793379&amp;do=diff</link>
        <description>Sybase SQL Anywhere LIST aggregate function concatenates strings from multiple rows into a single string.

In Microsoft SQL Server you can use STRING_AGG function, but it is available since SQL Server 2017 only , so you can also use STUFF function and FOR XML PATH clause of SELECT statement.</description>
    </item>
    <item rdf:about="https://www.sqlines.com/sybase-asa-to-sql-server/message?rev=1729088050&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-16T14:14:10+00:00</dc:date>
        <title>MESSAGE Statement - Sybase SQL Anywhere to SQL Server Migration</title>
        <link>https://www.sqlines.com/sybase-asa-to-sql-server/message?rev=1729088050&amp;do=diff</link>
        <description>Sybase SQL Anywhere MESSAGE statement allows you to send a message to client or database message log. In SQL Server you can use PRINT statement

Sybase SQL Anywhere:


  -- Send message to client
  MESSAGE 'Hello, world!' TYPE STATUS TO CLIENT;


SQL Server:</description>
    </item>
    <item rdf:about="https://www.sqlines.com/sybase-asa-to-sql-server/sqlstate?rev=1728057951&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-04T16:05:51+00:00</dc:date>
        <title>SQLSTATE - Sybase SQL Anywhere to SQL Server Migration</title>
        <link>https://www.sqlines.com/sybase-asa-to-sql-server/sqlstate?rev=1728057951&amp;do=diff</link>
        <description>Sybase SQL Anywhere SQLSTATE string variable indicates the status of the last executed statement. Usually it is used to check the status of the recent FETCH statement.

In SQL Server you can use @@FETCH_STATUS variable.

 Sybase SQL Anywhere  SQL Server  SQLSTATE &lt;&gt; '02000'  Row found  @@FETCH_STATUS = 0  SQLSTATE = '02000'  Row not found  @@FETCH_STATUS &lt;&gt; 0 

Sybase SQL Anywhere:</description>
    </item>
    <item rdf:about="https://www.sqlines.com/sybase-asa-to-sql-server/sqlstatus?rev=1728078008&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-04T21:40:08+00:00</dc:date>
        <title>@@SQLSTATUS - Sybase SQL Anywhere to SQL Server Migration</title>
        <link>https://www.sqlines.com/sybase-asa-to-sql-server/sqlstatus?rev=1728078008&amp;do=diff</link>
        <description>Sybase SQL Anywhere @@SQLSTATUS variable indicates the status of the last executed statement. It can be used to check the status of the recent FETCH statement.

In SQL Server you can use @@FETCH_STATUS variable.

 Sybase SQL Anywhere  SQL Server  @@SQLSTATUS = 0  Row found  @@FETCH_STATUS = 0  @@SQLSTATUS = 2  Row not found  @@FETCH_STATUS &lt;&gt; 0 

Sybase SQL Anywhere:</description>
    </item>
    <item rdf:about="https://www.sqlines.com/sybase-asa-to-sql-server/top?rev=1727864964&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-02T10:29:24+00:00</dc:date>
        <title>TOP Clause in SELECT - Sybase SQL Anywhere to SQL Server Migration</title>
        <link>https://www.sqlines.com/sybase-asa-to-sql-server/top?rev=1727864964&amp;do=diff</link>
        <description>Both Sybase SQL Anywhere and SQL Server support TOP clause to limit the number of rows returned by SELECT statement after ORDER BY, but there are some differences that require conversion. 

Consider the following sample table:


  -- Sample table
  CREATE TABLE colors (name VARCHAR(30));
  
  -- Sample data
  INSERT INTO colors VALUES ('Red');
  INSERT INTO colors VALUES ('Orange');
  INSERT INTO colors VALUES ('Blue');</description>
    </item>
    <item rdf:about="https://www.sqlines.com/sybase-asa-to-sql-server/update_alias?rev=1727553017&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-09-28T19:50:17+00:00</dc:date>
        <title>UPDATE Statement with Alias - Sybase SQL Anywhere to SQL Server Migration</title>
        <link>https://www.sqlines.com/sybase-asa-to-sql-server/update_alias?rev=1727553017&amp;do=diff</link>
        <description>Both Sybase ASA and SQL Server support SQL UPDATE statement that allows you to modify the existing table rows, but there are some differences so the conversion may be required. 

UPDATE with Alias


Sybase ASA allows you optionally defining an alias for the updated table:</description>
    </item>
</rdf:RDF>
