I would go with a check constraint on a column with unique constraint to make sure there can only be one row.

Add a instead of delete trigger to prevent deleting...

Here are a couple of suggestions you could try.

Change the query in your fucntion to this. I think is is also logically better, because it prevents the possibility of...

DHeath (2/15/2008)

---

Hey MVJ,

Not sure if this is asking too much but are those scripts something you have available and willing to share or are they something that i would need...

Don't forget the last step:

4) Fire Navision consultants who accidently deleted important business data from our database.

DHeath (2/15/2008)

---

So i take it the "suite of scripts" are already prewritten specific to the server. I used SQLIO but didnt have anything to increase the stress as it...

I install SQLIO and run a suite of scripts to get an initial performance benchmark for all disks when I setup a new server.

I save the test output so that...

I think the issue of how to store money is different than the issue of how to cast it properly for calculations.

If you are doing financial calculations that use built-in...

create table #RunningJobs

(

... column definitions ...

)

insert into #RunningJobs

exec msdb.dbo.sp_help_job @execution_status = 1

Jeff Moden (2/12/2008)

---

I'm confused... I believe the cross-join is to generate a million rows... not to generate the 7 digits. Perhaps I was looking at the wrong post. ...

I don't think it's a stretch of the imagination to believe that a query that is a cross join (probably unnecessary, since you only need 7 rows) between system views...

Matt Miller (2/12/2008)

---

Of course - why generate each digit separately, when you get get them all at once?

Should you need a few million (or in my example, 1 million) at...

If you load your date table with the function on this link, it has columns for quarters and many other date attributes built in.

Date Table Function F_TABLE_DATE:

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61519

John Beggs (2/12/2008)

---

I think you'll find that the difference between 1ms and 1ms is pretty negligible. Feel free to test for yourself.

What boundary would you set for flexible coding...

Perhaps, but but my solution involves no table access, so it should perform better.

Ordering is only guaranteed within a SELECT with an ORDER BY clause.

Ordering during an INSERT may or may not happen the way you hope in any version of SQL Server.