Hi,

I'm currently working on a project that use MS SQL Server as Database Engine. I would like
give ability to run my software in MS SQL Server as well as a more economical solution
like ElevateDB. I have lot's of stored procedure and function in SQL Server that heavily
use of CURSORS, Temporary Tables, User Defined Functions (Scaler Function and Table Valued
Function)

Is it possible to execute the same stored procedures and function that I wrote in SQL
Server in ElevateDB? When I say the same stored procedures I did not mean EXACTLY the
same. If there are minor changes between SQL Server SQL and ElevateDB SQL, I could write a
parser that convert SQL dialect of SQL Server into SQL dialect of ElevateDB. But If
ElevateDB did not support CURSORS or Temporary Table or for example Triggers as SQL Server
support it would be very hard to convert the project.

Generally does you people here have same experience with something like this? Is there
more detailed document that describe SQL Syntax that ElevateDB support?

PS: If converting to ElevateDB require rewrite 20% of my SPs and Functions it could be
acceptable.

Hi Muhammad,

ElevateDB has not yet been released, so Tim is the only one with extensive
knowledge of PSQL at this moment. In my brief experience, the stored
procedure language in ElevateDB is similar to MSSQL, but has its own nuances
(as do all PSQLs). ElevateDB supports all the features you mention (RI does
not support cascading RI at this stage). I would suggest downloading the
public beta (if you are a DBISAM customer), or wait for a trial version when
ElevateDB is the released, and try converting some of your MSSQL procedures
etc.

HTH
--
Best regards

Steve

"Muhammad Mamouri" <mamouri@msn.com> wrote in message
news:5509B4F7-50C9-41A7-9FE5-4EFBEA926790@news.elevatesoft.com...
> Hi,
>
> I'm currently working on a project that use MS SQL Server as Database
> Engine. I would like
> give ability to run my software in MS SQL Server as well as a more
> economical solution
> like ElevateDB. I have lot's of stored procedure and function in SQL
> Server that heavily
> use of CURSORS, Temporary Tables, User Defined Functions (Scaler Function
> and Table Valued
> Function)
>
> Is it possible to execute the same stored procedures and function that I
> wrote in SQL
> Server in ElevateDB? When I say the same stored procedures I did not mean
> EXACTLY the
> same. If there are minor changes between SQL Server SQL and ElevateDB SQL,
> I could write a
> parser that convert SQL dialect of SQL Server into SQL dialect of
> ElevateDB. But If
> ElevateDB did not support CURSORS or Temporary Table or for example
> Triggers as SQL Server
> support it would be very hard to convert the project.
>
> Generally does you people here have same experience with something like
> this? Is there
> more detailed document that describe SQL Syntax that ElevateDB support?
>
> PS: If converting to ElevateDB require rewrite 20% of my SPs and Functions
> it could be
> acceptable.
>

Hi,
Actually I'm not customer of DBISAM. Although I worked with DBISAM, before when I was
hired by a company to develop and maintaince their project. I knew that ElevateDB is not
released, yet. I ask here about SQL syntax  because I could not test it by my own.

Does Tim could refer me to some document or help file (Even Draft) that describe this?

Regards


"Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote:

Hi Muhammad,

ElevateDB has not yet been released, so Tim is the only one with extensive
knowledge of PSQL at this moment. In my brief experience, the stored
procedure language in ElevateDB is similar to MSSQL, but has its own nuances
(as do all PSQLs). ElevateDB supports all the features you mention (RI does
not support cascading RI at this stage). I would suggest downloading the
public beta (if you are a DBISAM customer), or wait for a trial version when
ElevateDB is the released, and try converting some of your MSSQL procedures
etc.

HTH
--
Best regards

Steve

"Muhammad Mamouri" <mamouri@msn.com> wrote in message
news:5509B4F7-50C9-41A7-9FE5-4EFBEA926790@news.elevatesoft.com...
> Hi,
>
> I'm currently working on a project that use MS SQL Server as Database
> Engine. I would like
> give ability to run my software in MS SQL Server as well as a more
> economical solution
> like ElevateDB. I have lot's of stored procedure and function in SQL
> Server that heavily
> use of CURSORS, Temporary Tables, User Defined Functions (Scaler Function
> and Table Valued
> Function)
>
> Is it possible to execute the same stored procedures and function that I
> wrote in SQL
> Server in ElevateDB? When I say the same stored procedures I did not mean
> EXACTLY the
> same. If there are minor changes between SQL Server SQL and ElevateDB SQL,
> I could write a
> parser that convert SQL dialect of SQL Server into SQL dialect of
> ElevateDB. But If
> ElevateDB did not support CURSORS or Temporary Table or for example
> Triggers as SQL Server
> support it would be very hard to convert the project.
>
> Generally does you people here have same experience with something like
> this? Is there
> more detailed document that describe SQL Syntax that ElevateDB support?
>
> PS: If converting to ElevateDB require rewrite 20% of my SPs and Functions
> it could be
> acceptable.
>

Hi Muhammad,

The ElevateDB V1 SQL Manual is online at :

http://www.elevatesoft.com/edb1sql.htm

"SQL/PSM Statements" is the section you will want to look at.

Good luck,
--
Best regards

Steve

"Muhammad Mamouri" <mamouri@msn.com> wrote in message
news:7763C786-0CC8-4AB5-B3A6-9C03E61BD1A7@news.elevatesoft.com...
> Hi,
> Actually I'm not customer of DBISAM. Although I worked with DBISAM, before
> when I was
> hired by a company to develop and maintaince their project. I knew that
> ElevateDB is not
> released, yet. I ask here about SQL syntax  because I could not test it by
> my own.
>
> Does Tim could refer me to some document or help file (Even Draft) that
> describe this?
>
> Regards
>
>
> "Steve Forbes" <ozmosys@spamfreeoptusnet.com.au> wrote:
>
> Hi Muhammad,
>
> ElevateDB has not yet been released, so Tim is the only one with extensive
> knowledge of PSQL at this moment. In my brief experience, the stored
> procedure language in ElevateDB is similar to MSSQL, but has its own
> nuances
> (as do all PSQLs). ElevateDB supports all the features you mention (RI
> does
> not support cascading RI at this stage). I would suggest downloading the
> public beta (if you are a DBISAM customer), or wait for a trial version
> when
> ElevateDB is the released, and try converting some of your MSSQL
> procedures
> etc.
>
> HTH
> --
> Best regards
>
> Steve
>
> "Muhammad Mamouri" <mamouri@msn.com> wrote in message
> news:5509B4F7-50C9-41A7-9FE5-4EFBEA926790@news.elevatesoft.com...
>> Hi,
>>
>> I'm currently working on a project that use MS SQL Server as Database
>> Engine. I would like
>> give ability to run my software in MS SQL Server as well as a more
>> economical solution
>> like ElevateDB. I have lot's of stored procedure and function in SQL
>> Server that heavily
>> use of CURSORS, Temporary Tables, User Defined Functions (Scaler Function
>> and Table Valued
>> Function)
>>
>> Is it possible to execute the same stored procedures and function that I
>> wrote in SQL
>> Server in ElevateDB? When I say the same stored procedures I did not mean
>> EXACTLY the
>> same. If there are minor changes between SQL Server SQL and ElevateDB
>> SQL,
>> I could write a
>> parser that convert SQL dialect of SQL Server into SQL dialect of
>> ElevateDB. But If
>> ElevateDB did not support CURSORS or Temporary Table or for example
>> Triggers as SQL Server
>> support it would be very hard to convert the project.
>>
>> Generally does you people here have same experience with something like
>> this? Is there
>> more detailed document that describe SQL Syntax that ElevateDB support?
>>
>> PS: If converting to ElevateDB require rewrite 20% of my SPs and
>> Functions
>> it could be
>> acceptable.
>>
>
>

Muhmmad,

<< Is it possible to execute the same stored procedures and function that I
wrote in SQL Server in ElevateDB? When I say the same stored procedures I
did not mean EXACTLY the same. If there are minor changes between SQL Server
SQL and ElevateDB SQL, I could write a
parser that convert SQL dialect of SQL Server into SQL dialect of ElevateDB.
But If ElevateDB did not support CURSORS or Temporary Table or for example
Triggers as SQL Server support it would be very hard to convert the project.
>>

EDB supports all of these features.  The main difference between the MS SP's
and EDB SP's is that EDB uses dynamic SQL for all non-control related
statements in an SP, whereas MS SQL Server uses static SQL that may or may
not be bound to the catalog for the database.  For example, in MS you would
write this:

DECLARE TestCursor SENSITIVE CURSOR FOR SELECT * FROM MyTable;

OPEN TestCursor;

FETCH......

In EDB you would write this instead:

DECLARE TestCursor SENSITIVE CURSOR FOR Stmt;

PREPARE Stmt FROM 'SELECT * FROM MyTable';

OPEN TestCursor;

FETCH......

Also, because EDB uses dynamic SQL for all non-control statements, you can
use DDL in an SP (especially with temporary tables) without it causing a
recompile of the SP like it does in MS SQL Server.  It also gives you the
flexibility to determine when and where you want to use pre-compiled SQL
statements (PREPARE/EXECUTE) vs. one-off SQL statements that are only
executed once (EXECUTE IMMEDIATE).

<< Generally does you people here have same experience with something like
this? Is there more detailed document that describe SQL Syntax that
ElevateDB support? >>

You can find SQL/PSM statement reference here:

http://www.elevatesoft.com/edb1sql_sql_psm%20statements.htm

<< PS: If converting to ElevateDB require rewrite 20% of my SPs and
Functions it could be acceptable. >>

I think that, apart from the dynamic SQL issue, most of the SQL should move
over just fine.

--
Tim Young
Elevate Software
www.elevatesoft.com