I'm used to that :w00t:

1) married

2) dba

:D:):P:w00t::hehe:

There is this very nice and eye-opening article concering ranges ...

Called "The "Numbers" or "Tally" Table: What it is and how it replaces a loop."

http://www.sqlservercentral.com/articles/TSQL/62867/

Please read this little guideline to get the info you want asfast as you want.

Forum Etiquette: How to post data/code on a forum to get the best help

http://www.sqlservercentral.com/articles/Best+Practices/61537/

No problem...

What version are you on

Select Serverproperty( 'BuildClrVersion' ) as BuildClrVersion

, Serverproperty( 'Collation' ) as Collation

, Serverproperty( 'CollationID' ) as CollationID

, Serverproperty( 'ComparisonStyle' )...

I'm still inivestigating the cause for this issue, but I suspect the automatic updates just ruined my 24/7 (MOM) db server. :crazy:

http://www.sqlservercentral.com/Forums/Topic571088-146-1.aspx

I must admit, at the plant where I have...

and make the

part distinctive !

(so you don't update the same 1000 rows every time and again...

declare @startdate datetime, @enddate datetime

SELECT @startdate = dateadd(dd, (-6 - DATEPART (dw, getdate())),DATEADD(dd,DATEDIFF(dd,0,getdate()),0))

, @enddate = DATEADD(dd,DATEDIFF(dd,0,getdate())+ 1 ,0)

--print...

are you using the same service account for all the instances ?

if not, you need to grant loging for all service accounts to all the instances

SELECT object_name(i.object_id) as Table_Name

, i.name as Index_Name

, i.index_id

, STATS_DATE(i.object_id, i.index_id) as Statistics_Date

FROM sys.objects o

INNER JOIN sys.indexes i

ON o.object_id = i.object_id

order by Table_Name, i.index_id ;

GO

You can also inspect the last time stats have been updated :

SELECT i.name as Index_Name

, STATS_DATE(i.object_id, i.index_id) as Statistics_Date

FROM sys.objects o

INNER JOIN sys.indexes i

ON o.object_id = i.object_id;

GO

here's another test with the timestamp datatype:

/****** test script timestamp ******/

set nocount on

go

/*

@@DBTS returns the last-used timestamp value of the current database.

A new timestamp value is generated when a...

I'm sorry for the xpost.

I originally posted in the wrong forum (sql2005)

Please reply to the sql2000 forum at

http://www.sqlservercentral.com/Forums/Topic571090-48-1.aspx

select dateadd(wk,36,master.dbo.fn_ALZDBA_convert_date2WeekRangeALZDBA ('20080104', 'F'))

, dateadd(wk,37,master.dbo.fn_ALZDBA_convert_date2WeekRangeALZDBA ('20080104', 'F'))

, dateadd(wk,38,master.dbo.fn_ALZDBA_convert_date2WeekRangeALZDBA ('20080104', 'F'))

, dateadd(wk,39,master.dbo.fn_ALZDBA_convert_date2WeekRangeALZDBA ('20080104', 'F'))

it depends ..... What's your week 1 ??

Microsoft starts week 1 at 1/1 :crazy:

In my company, week 1 is the week which containns Jan 4th.

So we always need to check...

Jason Selburg (9/16/2008)

---

I have a PK on the table, and the original file's line number is all that is important. That is, I'm not concerned how it is stored in...