Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeder.erje.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Bernard Peek Newsgroups: comp.databases.ms-sqlserver,microsoft.public.sqlserver.programming Subject: Re: SS 2008: Front-End Language Processor for Scripts Date: Wed, 25 May 2011 17:27:15 +0100 Lines: 24 Message-ID: <944ov3FetmU1@mid.individual.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: individual.net +vc3U8bhtJtVgFSvO8JPMAeYHBIB/yOLI+RPnw/eD4h2EQkyjb Cancel-Lock: sha1:tcyFFwDXHwdSTzWCCJOAq9BCDwc= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.databases.ms-sqlserver:373 On 23/05/11 23:24, Gene Wirchenko wrote: > Dear SQLers: > > I am trying to get around some of the limitations of T-SQL. > > I wish to run a preprocessor over script files much as the C > preprocessor does for C programs. File inclusion and symbol > definition commands are about all I need. Does anyone know of one > that will work well with SQL Server script files? > > I want to be able to define symbols like > #define ERRSTL N'50001: String %s is too long.' > in a secondary file and have statements like > raiserror(ERRSTL,16,1,N'ACUK) > expand to > raiserror(N'50001: String %s is too long.',16,1,N'ACUK) This is a simple substitution. Have you considered using sed? -- Bernard Peek bap@shrdlu.com