Developer edition to developer edition should do fine.

Perry Whittle (1/19/2009)

---

Matt, it would seem he has a mixture of sql2000 instances, 2 of the instances are the MSDE which SBS installs. The other 2 seem to be developer...

You can try right-clicking on one, then using open Table. That will allow you to browse the table.

Still - using this method to go in and edit values is...

Garadin (1/19/2009)

---

Thanks Matt. I've always known you could Schema Bind a view, but I've never needed to, so I didn't consider the reasons why you might do so. ...

shellyr (1/19/2009)

---

I can see from my last question that I cannot spell. Anyway we had a SQL DBA consultant working with us for about a year.

I called...

You'll want to peruse this BOL entry. It has to do with flagging your views as schemabinding to prevent such issues...

http://msdn.microsoft.com/en-us/library/ms187821.aspx

update tableA

set countyAbbrev = tb.newCountyAbbrev

from

tableA

inner join tableb tb on

...

I'm thinking you want the EXISTS to be part of your INSERT statement, and not AROUND it. That way you can do all of the inserts in one shot...

Malcolm - assuming I understand your current setup - that's not a supported upgrade path. According to the documentation about MSDE 2000 - the only version you can upgrade...

What is it you're testing for? Execution errors or whether it actually deleted anything?

If you're looking at Execution-type errors, I'd think BEGIN TRY...END TRY would be your friend (BOL...

If the client is SA on the box this is getting deployed it, the encryption is usually not going to be "enough" to prevent them from seeing what the code...

How about creating a table for this stuff? a simple lookup table should be infinitely easier to maintain than the function, and will run circles around it perf-wise too...

Static...

binary lumberjack (1/19/2009)

---

You can't shrink below the initial size. Your only option is to back up the database, drop and recreate it with a lower initial size, and then...

While you certainly could add a FOR XML to your query to spit it out in XML, actually applying an XSL transform to it in order to e-mail it is...

Depending on what the application requirements, if you have no use for knowing that a given column wasn't even by the user - it might be a whole lot easier...