Personal History

Started: 1978 UCSD Dept of Education providing on and off support for teachers

 

1980-1983 US Air force / Electronics / Avionics

1983-1987 General Dynamics Space Systems Division

Ø  Computer modeling of space craft environmental survivability

1988-1992 Owner Imaginative management

Ø  Business Consulting integration with Windows Office Products

1992-1996  Director of Information Systems Desire incorporated

Ø  Developed multi-site POS system

Ø  Internet Marketing and Web development

1996 -  Current CEO YDPages Inc

Projects under YDPages include;

Ø  7 Contracts at Microsoft as an Engineer

Ø  Kibble & Prentice

Ø  Space labs Healthcare

Ø  Interpol

Ø  Dept of homeland Security (DHS)

Ø  Transportation Security Administration (TSA)

Ø  Dept of Alcohol, Tobacco and Firearms (ATF)

Ø  North American Conveyor Corporation (NACC)

Ø  VCI Services

 

Currently engaged on campus at Microsoft  wrapping up a Monitoring Aggregation and Ticketing solution for the Windows Device Group.

sp_help_executesproc

I have never liked the output of SSMS script to execute , so I built my own tool.

http://ydpages.com/utility/sp_help_executesproc.sql.txt


exec sp_help_executesproc 'sp_help_executesproc'

Gives you the following output:

DECLARE @procname sysname = null

,@schema sysname = null

,@verbose bit = null

,@debug int = null

SELECT @procname = @procname --sysname

,@schema = @schema --sysname

,@verbose = @verbose --bit

,@debug = @debug --int

EXECUTE [dbo].sp_help_executesproc @procname = @procname --sysname

,@schema = @schema --sysname

,@verbose = @verbose OUTPUT --bit

,@debug = @debug --int  I always build my procedures with the assumption that users will give me invalid data at every opportunity, so I always allow null to be acceptable and validate all inputs before doing any damage.

Put this one in Model to make it available over time.