Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.ms-sqlserver > #380

Re: SS 2008: Front-End Language Processor for Scripts

Show all headers | View raw

Gene Wirchenko (genew@ocis.net) writes:
>>They added more warnings to Perl in 5.12, so you get a lot of these
>>with AbaPerls. I have address these, but I have not made a public
> 
>      Warnings or errors?  By a warning, I mean emit error message and
> continue.  By an error, I mean emit error and stop.

Warnings. Had I meant errors, I would have said errors. :-)
 
>>I think Perl 5.10 is a better choice for the time being.
> 
>      Groan!  That will be three Perl downloads and installations.  I
> suppose I need the practice.

Bzzt! I have six Perl installations on my machine. And since they have
released 5.14, I will need two more. But, OK, I build Perl modules and
you don't (I assume).

 
>>       DECLARE @name sysname,
>>> Cannot change directory to NAMELESS\sql: No such file or directory
> 
>      And this?  Where is "NAMELESS\sql" coming from?
>...
>      No, c:\cbs2dev\SQLServer is the directory name.  I have not
> gotten into organising my SQL Server code into different directories
> yet.  I do not have very much.

Well, to use DBBUILD you will have no choice to adhere to the AbaPerls
Directory structure. Which means that stored procedures goes into
the SP directory, and they need to have the .sp extension. And so
on, see http://www.sommarskog.se/AbaPerls/doc/structure.html. (The
manual is also in your download.)

Furthermore, with the version of AbaPerls you downloaded, when you build
from disk without SourceSafe, you need to be in a directory two levels
above the SQL directory. You did not specify a subsystem name, why 
AbaPerls assumes the name NAMELESS. Whence NAMELESS\sql.

What is silly is that you should be able to run DBBUILD in your SQL
directory or in, say, SQL\Scripts, and I have fixed this, but it's
in the public release.

I'm afraid that using AbaPerls without reading the manual can be a rough 
ride, since there are some things you may not expect at first. And the
rules are complex - Hey, I started the develop AbaPerls in 1996, so it
has acquired some complexity by time.


-- 
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx

Back to comp.databases.ms-sqlserver | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

SS 2008: Front-End Language Processor for Scripts Gene Wirchenko <genew@ocis.net> - 2011-05-23 15:24 -0700
  Re: SS 2008: Front-End Language Processor for Scripts Erland Sommarskog <esquel@sommarskog.se> - 2011-05-24 07:21 +0000
    Re: SS 2008: Front-End Language Processor for Scripts Gene Wirchenko <genew@ocis.net> - 2011-05-24 17:21 -0700
      Re: SS 2008: Front-End Language Processor for Scripts Erland Sommarskog <esquel@sommarskog.se> - 2011-05-25 12:39 +0000
        Re: SS 2008: Front-End Language Processor for Scripts Gene Wirchenko <genew@ocis.net> - 2011-05-25 12:46 -0700
          Re: SS 2008: Front-End Language Processor for Scripts Erland Sommarskog <esquel@sommarskog.se> - 2011-05-25 23:33 +0200
            Re: SS 2008: Front-End Language Processor for Scripts Gene Wirchenko <genew@ocis.net> - 2011-05-25 15:21 -0700
              Re: SS 2008: Front-End Language Processor for Scripts Erland Sommarskog <esquel@sommarskog.se> - 2011-05-26 23:44 +0200
                Re: SS 2008: Front-End Language Processor for Scripts Gene Wirchenko <genew@ocis.net> - 2011-05-26 15:24 -0700
  Re: SS 2008: Front-End Language Processor for Scripts Bernard Peek <bap@shrdlu.com> - 2011-05-25 17:27 +0100

csiph-web