Why keep counts at all?

Let all logic live in the view, then while any entry in the view, remove

ALTER PROCEDURE [dbo].[usp_VTrickleDeleteEvent]

AS

SET NOCOUNT ON

SET QUOTED_IDENTIFIER OFF

BEGIN

WHILE exists (Select 1 from...

Keepers are fine, if you care

For LinkedIn? My PW is password (or Passw0rd, if they are more pesky)

For my Bank login? password isn't gonna go there, that's where...

Shrinking should be left

And Scheduable

Why? I work, largely, in Development databases

On a BAD day there may be 4 users in a single DB - Most of the...

Next step would be, in non-destructive scripting, foreach

e.g.

(Using 2 batch files)

In first, pick which files to run:

@Set Svr=ServerToRunAgainst

@Rem For Non-Integrated @Set lgn=-U sa -P password

@Set lgn=-E

@Set Db=-d SOMEDB

@for /R "..\Create...

Example of SQL ITSELF being unclear:

mtassin showed that it's NOT usable within a Function, even passing a static seed value - (Non Deterministic here)

The Select Rand(),NewID() showing SAME values for...

How about Select Rand(), NewId() from #Temp?

What happens?

Get single value for Rand

Get DIFFERENT Value for NewID

So in this scenario, Rand IS deterministic, else Sql would re-evaluate for each row, correct?

Yet...

No disagreement with specifying a seed causes a deterministic value

How about this?

Set Nocount On

Create Table #Temp

(

Val int

)

Insert Into #Temp values (1)

Insert Into #Temp values (2)

Insert Into #Temp values (3)

Insert...