Sunday, 26 May 2013
       
AUSQLUG Forums Home   Search   Login   Register   Member List  

  Viewing User Profile for: prfbrown
 About  Contact
Joined: 09 Aug 2005 10:43 PM
Last Login: 01 Mar 2007 10:04 AM
Website:
Location: Unavailable to anonymous users.
Occupation: Unavailable to anonymous users.
Interests: Unavailable to anonymous users.
Signature:
Email: Unavailable to anonymous users.
MSN IM: Unavailable to anonymous users.
AIM: Unavailable to anonymous users.
Yahoo IM: Unavailable to anonymous users.
ICQ: Unavailable to anonymous users.
 Post Statistics
prfbrown has contributed to 5 out of 1,787 total posts (0.28% of total).
Most Recent Posts:
GO MANLY 2/06/2006 5:46:25 PM   (Total replies: 0)
"Up the Eagles" for 2006.

LittleSteps: RDBMS portal software for SQL Server 7/09/2005 10:28:18 PM   (Total replies: 0)
This post is to introduce the resourcefulness of an extremely versatile tool in the SQL Server database environment. We have called the tool LittleSteps, due to the simple and sure methodology of approach by which one can develop and implement information reporting applications, and immediately distribute them in an organisationally sensitive manner to the end user. Its claim to "new technology" is by way of the method of development of applications, both reporting applications and data ...

A Brief History of IT Management and the RDBMS 10/08/2005 6:36:43 PM   (Total replies: 0)
This article is a series of articles outlining the emergence of the RDBMS in the last 30 years from the perspective of IT management during that period of time. The index page for the article is located here: http://www.mountainman.com.au/software/history/ Enjoy.

Re: searching for documents of stored procedures 10/08/2005 6:12:35 PM   (Total replies: 0)
I have found one of the best references in creating stored procedures is simply the Transact SQL Help File within Query Analyser (QA). A stored procedure is really just a bit of TSQL code that has been designed to do a specific task. The TSQL code is then prefaced with: create procedure STORED_PROC_XYZ001 as << TSQL Code then sits here >> When this is run in QA, a stored procedure is created. So therefore, IMO, it is the TSQL documentation that will best assist the design of the code ...

Re: Rowcount revisited 10/08/2005 6:03:37 PM   (Total replies: 0)
You may also want to routinely write the rowcounts for your tables into a rowcount history table seeing as though you have them being gathered. Retrospective analysis of rowcount change is sometimes useful for planning. The TSQL code that gathers the rowcount can also gather a number of other parameters (eg: space allocations for table data and indexes) and therefore you are able to extrapolate trends towards capacity planning. I have some further information about rowcounts on the web ...

Search for more...