Try:

Exec sp_CmdShell 'Echo Text for Line 1 & Echo Text for Line 2'

The "&" is the Command-Shell command separator. Of course, you could redirect this output to a file as...

Run Microsoft's dependency checker (depends.exe, ya, I don't care for the name either...) against your DLL. You will also need to load the DLL's that your DLL references. You probably don't...

So much for conventional wisdom...

This may not be what you want, but, try something like this:

Declare @Str VarChar(8000)

Set @Str=''

Select @Str=@Str+','Col1+','+Col2+','+...+Char(13)+Char(10) from dbo.[YourTable] where ...

Print @Str

You get the idea...

Try this:

-- Construct test UId table.

If Object_Id('Test') is not Null Drop Table Test

Select 0[UId] into Test

-- Obtain the next UId.

Declare @i Int

Update Test Set @i=UId,UId=UId+1

-- or --

Update Test Set @i=UId=UId+1

Which...

I use to write Extended Stored Procedures to handle the stuff that SQL wasn't "comfortable" with but XSProc are difficult to manage (versioning, interface requirements, environemtal requirements, testing, documentation... ad...

Use xp_CmdShell and START a copy of OSQL to run a script...

Ya, I use to use xp_FileExists, but, I figured there's less a chance of the Command Prompt stuff going away than xp_FileExists... but then, who ever would have thought that...

Try this:

If Object_id('test') is not null Drop Table Test

Create Table Test(Id int,ParentId int,[Name] varchar(256))

Insert Test Values(1,Null,'A')

Insert Test Values(2,1,'B')

Insert Test Values(3,1,'C')

Insert Test Values(4,2,'BA')

select

 Id,

 Name+Case IsNull((select top 1 t2.ParentId from test t2 where...

Ya, I know... here's the code...

Declare @v1 int,@v2 varchar(256)

Set @v1=123

Select @v1=456,@v2='789'

Paste the following into QA and click the "Display Estimated Execution Plan" tool button. Hang you mouse cursor over each "Select Cost 0%" page-image and you'll see that the "set"...

Uuups, sorry, its another "DOS" hack sproc in our common library system... Here's the code:

If you don't have an allergic reaction to xp_CmdShell you could...

Declare @rc Int

Exec @rc=master.dbo.xp_CmdShell 'If Exist "c:\boot.ini" (Exit 1) Else (Exit 0)',no_output

Select @rc[Return Code]

You a funny guy There is a practical limit to using this technique, I leave it up to you to make that call...

I hear ya... But, you write the code once... your run it a bazillion times.. having SQL use the proper indicies can cover for a little code bloat.

Why not use some code

If @p1 is Null Select * from Table

Else Select * from Table where c1=@p1