Database

DECLARE @rc AS INTEGER
Select * from #temp
SET @rc = @@rowcount 
print @rc
while @rc <> 0
begin
----
----
---
end 

DECLARE @rtDayofWeek VARCHAR(10) 
DECLARE @dtDate datetime
DECLARE @endDate datetime
SET @dtDate = '8/25/2010' 
SET @endDate = '8/27/2010' 
WHILE @dtDate <= @endDate
	BEGIN
	SELECT @rtDayofWeek = CASE DATEPART(weekday,@dtDate)  
	WHEN 1 THEN 'Sunday'  
	WHEN 2 THEN 'Monday'  
	WHEN 3 THEN 'Tuesday'  
	WHEN 4 THEN 'Wednesday'  
	WHEN 5 THEN 'Thursday'  
	WHEN 6 THEN 'Friday'  
	WHEN 7 THEN 'Saturday'  
	END  
PRINT @rtDayofWeek
SET @dtDate = DATEADD(Day,1,@dtDate)
END

None

• Script your entire database, in the version that you're releasing to the customer(s).
• Archive them somewhere safe (SourceSafe - don't forget to label it, or even burned and nicely indexed on CD)
• Include all unit-tests for your procdures!
• Consider whether the sprocs have any dependencies themselves, like functions, views or other procedures.
• A scripter[^] might come in handy.

I are Troll

modified on Thursday, August 26, 2010 6:22 PM

Eddy Vluggen wrote:

The database itself doesn't version the procedures,

SilimSayo wrote:

PIEBALDConsult wrote:

Another argument against using stored procedures.

The database does not version any objects [Tables, Views, Triggers, Functions and Stored Procedures]; so using your argument, should we avoid databases altogether?

I are Troll