I don't deal much with proxy accounts myself, but SQL Server 2005 does offer the new "Execute AS" capability, where you can force the stored procedure to execute under the...

Actually, that's almost what we do in our shop.  The main difference is that we refresh Dev / Test / QC right before we put in (or start) a release cycle. ...

Stuff isn't working for me.  It's complaining that my subquery is returning more than 1 value.

I guess I am going to have to do this the hard way.  I really...

Except that still doesn't give me percentages.  I can't find a function that does.

Any thoughts?

You have to default any variables that you might potentially not receive from outside the stored procedure.  However, you can't actually use the DEFAULT keyword with variables that are passed...

Yes, you have the right idea, but your SP WHERE clause is wrong.

You can't use the WHERE clause to match the variables you are passing into the SP to each other. ...

JV,

Have you ever used SSIS before?  What about DTS?  If you've never used either, I recommend getting an SSIS book.  If you've used DTS but not SSIS, you might be...

You know, it occurs to me that you might be heading in the wrong direction.  Especially as some of your row results turn out to be column headers, but the...

First, do you have FULL Text Indexing set up on your SQL Server?

The CONTAINS keyword only works with that.  Same as FREETEXT, CONTAINSTABLE and FREETEXTTABLE.

Secondly, you have to code your...

Have you checked out the new PIVOT operator in Books Online?

I'm just learning it myself, so I can't give you a lot of information.  Though I'm not sure you can...

Paul,

Well, I'm good and stumped here.  The only thing I can think of is that maybe there's a hidden newline character somewhere in the date field, but I'm not...

Steve,

Maybe they are just using it in a colloquial sense, but there are a lot of people who would take the word "Snapshot" literally.  So I decided just to stick...

I don't recommend a snapshot, actually.  If the Developers are going to be constantly developing against a DB, a better practice would be to do a nightly restore of production...

Ariadne,

Remember also, that if you automate your backups via the Litespeed Enterprise console, it can self verify without you having to "wait until it's done" and running that extended sproc.

Actually, there's sound reason to move your SQL Server install to another drive.  If you have multiple drives, put your OS on the C: drive and then the SQL Server...