I've just copy/pasted the script and added the last inner-join-part.

It returned rows. (with sql2000 and with sql2005)

This is the full script, copy/paste it and run. It should give results if...

just to add to the other replies :

you could use triggers to enforce this check constraint.

Although its better to avoid ....

CREATE TRIGGER mytrigger _IU ON mytable  

FOR insert, update

AS

BEGIN

if exists...

or maybe even replace the complete where clause with

inner join

 ( select job_id, max(run_date) as Max_run_date

  from msdb.dbo.sysjobhistory

  group by job_id ) jhMAX

on jh.job_id = jhMAX.job_id

and jh.run_date = jhMAX.Max_run_date

there is also a litle pitfall with ...

and jh.run_date = convert(int,

- how long is it taking the system to allocate 200GB ?

- did you try to copy a 200Gb file to that logical disk ? And how long did that...

so this may be I/O related.

keep in mind that files are being initialized (=nulled out) at allocation time (unless you specify not to).

What filesize are you trying to allocate ?

how about :

declare

@daysago int

set

@daysago = 7

Select

j.name as

thanks for the feedback.

Indeed the GUI stuff is very slow.

IMO the datapart is greath.

regading you filegroup-slowness ... I didn't encounter this.

Is it with the creation of the filegroup, or of the files within...

did you install MSDE ? use SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE

or did you install a personal edition ? use SQL2000-KB884525-SP4-x86-ENU.EXE

or did you install only client components ? use SQL2000-KB884525-SP4-x86-ENU.EXE

and do you also have Analysis...

- I'd start with a stop/start of sqlserver (to clear the performancerelated dmv's)

- then I'd do the standard maintenance !

   dbcc dbreindex / sp_updatestats / dbcc updateusage ('yourdb')

- Then I'd start...

depending on the amount of data you'd expect ....

- you could setup replication to your needs and sync nightly

- you could use the tablediff.exe (check books online).

        this ms-util generates...