You can use this statement as a base to accomplish what you want. (You still have to create your insert statement from this Common Table Expression)

;WITH myCTE(pid, yrs, lvl)

AS (

SELECT...

A quick comment, the datatype is missing for the amount column.

And yes, there is an alternative to cursor, i will try to post the solution later on (busy right now).

There are a couple of strategies you can use, mirroring / logshipping / replication. My recommendation will vary depending on what you want to accomplish, if you would like to...

Bruce W Cassidy (2/19/2009)

---

[font="verdana"]It's almost tempting to go into an interview with a harried expression, saying something like "I'm sorry, I'll have to reschedule the interview, one of our databases...

GilaMonster (2/19/2009)

---

swmsan (2/18/2009)

---

Errr, those are pretty trivial questions. If you don't know the answers, how...

swmsan (2/17/2009)

---

Can anyone send me some interview questions pls.

I recently got into DBA and I wanna stick to it as am very much interested in this.

The problem is that my...

Do you have a maintenance plan that check and backup the databases, rebuild indexes etc?

Do you have any blocking transactions ( use sp_who2 to look for blocking SPID in the...

Lempster (2/17/2009)

---

Hugo Kornelis (2/17/2009)

---

Hi Glen,

No, that's not correct. The upper limit in the BETWEEN proposition (2009-01-31 23:59:59.999) has to be converted to a proper datetime value. It can either be...

But you still have to remember that inserted/updated values will also be rounded. So if you try to insert '2009-01-31 23:59:59.999' it will be rounded to the next day. If...

The error message that we get is :

- Cannot create a column accessor for OLE DB provider "OpenLinkODBC"

Finally I found a solution that solved the problem. It seems like the...

Do you get this message in SQL Server log?

Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.

Try to run the statement RECONFIGURE and then...

The answer is incorrect since 2009-01-30 00:00:00:000 will not be returned. But you are pointing out a very important issue of SQL Server, datetime values are rounded to increments of...

Information about Msg 7399, Level 16, State 1, Line 1 from Microsoft knowledge base ( http://support.microsoft.com/kb/314530 ) :

"Error 7399 is a generic error message that the provider returns, which indicates...

Do anyone have experience of using the versioning capability of stored procedures? Whats your conclusion of this feature?

/Senior SQL Server DBA

SQL Server 2005 introduced partial support for the OVER clause and many important elements of the OVER clause are still missing, please read the following document from Itzik Ben-Gan: