Book a Demo

Author Topic: Importing MSSQL stored procedures  (Read 3742 times)

alexv

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Importing MSSQL stored procedures
« on: June 06, 2006, 10:38:51 am »
Hi,

I got latest version of EA (build 791) and it fails to parse all MSSQL2K stored procedures that have "$" (dollar sign) in the name of stored procedure or have "[]" (square brackets) around special "reserved" variable names (specifically at definition of these variables like "[name]") or have "/* comment */" comment right after the definition of the stored procedure name (after keyword AS). MSSQL validates these procedures just fine, but EA fails to parse them. Is it a bug in EA or am I missing something? ???

Thanks!

Alex V.

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Importing MSSQL stored procedures
« Reply #1 on: June 06, 2006, 12:29:43 pm »
Don't know about the rest, but does it catch the "$" procedures if you ask it to import system objects?
No, you can't have it!

alexv

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: Importing MSSQL stored procedures
« Reply #2 on: June 06, 2006, 01:13:25 pm »
When I tried to import system tables, then it complained about some system keywords, I didn't notice it complaning about $ sign. For example, it complained about "begin" line here:

/*
**
Add an object to the dtproperties table
*/
create procedure dbo.dt_adduserobject
as

set nocount on

/*

** Create the user object if it does not exist already

*/

begin transaction

alexv

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: Importing MSSQL stored procedures
« Reply #3 on: June 06, 2006, 01:16:26 pm »
I checked the system tables and none of them had $ sign in the name of procedure.

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Importing MSSQL stored procedures
« Reply #4 on: June 06, 2006, 01:37:55 pm »
I think you need to report this as a bug.

However, before you do, it would probably be best to wait and see if any of the other forum members have some insights into this.

IMHO something like this must be pretty common. You just cannot be the first person who has run up against it.

David
No, you can't have it!

alexv

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: Importing MSSQL stored procedures
« Reply #5 on: June 06, 2006, 01:49:27 pm »
Using $ signs in procedure names and reserved words for variable names isn't the best practice around, but MSSQL allows it. Besides, the application has been around for a long time and I have to deal with it in "as is" form.

I posted this issue as a bug to SPARX Systems. Let's see what reply I will get, because I have to start using EA asap.
« Last Edit: June 06, 2006, 01:49:57 pm by alexv »

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Importing MSSQL stored procedures
« Reply #6 on: June 06, 2006, 07:09:23 pm »
In the meantime, there are two things you should do.

First, make sure you have asked for notification of replies to this thread. If you did not do so when you started the thread, use the Notification link at the top of the board.

Then take the time to search the forum for possible leads. As I said earlier, someone must have run into this by now, and there may be discussion that will either give you the solution or point you to it. YABB (the forum application) is a bit strange when you query, so try a range of keywords.

David
No, you can't have it!