These are actually local windows groups that are created during the install. When configuring your system you could just add your domain user (or local user) to these windows...

Maybe something like this?

SELECT {columns}

FROM tables

WHERE {some filtering here}

ORDER BY CASE WHEN Type = 'TypeA' THEN 1

...

If you are running an AD domain - I would recommend using a domain account for your service line account. This will give you the ability to setup processes...

They can put the page file at whatever size they want. SQL Server shouldn't be using it - and if you are you have bigger problems.

If you are migrating...

The pagefile really shouldn't matter - since you really don't want SQL Server to be paging out to it anyways.

I would leave it alone.

What edition are you installing? Is...

GilaMonster (4/24/2009)[/b:-D

I actually had that happen when we moved to 2005, though it was not intentional.

All tests on dev were fine, all tests on UAT were fine. We upgraded production...

You don't insert columns - you insert rows. Each insert statement is going to insert 1 or more rows into that table.

It sounds like you are trying to update...

When you upgrade a system to SQL Server 2005 and above, the default for logins is to set the CHECK_POLICY property ON and to provide a new password for all...

See if you have a column defined in MyTable with a default defined as 'TBD'.

When inserting into a table, you have to provide values for all columns that do not...

Nick (4/24/2009)

---

Aha... great point re. version of client tools.

Here's one for ya... I applied a hotfix to my My SP2 server to fix an SSRS issue which brought the version...

Or preferably test it before you upgrade, by setting up the DB on a test server with 2005 on.

Though, I must admit, there's little that gets adrenaline pumping more than...

20 million rows is not really a lot these days. One thing you could do is create a new table with the columns structured the way you want, insert...

This may have already been asked previously, but - have you verified that the client tools have been upgraded to at least the same level as the server you are...

You need to verify the security permissions on the new 'server'. Most likely, your account does not have the necessary permissions to update the database anymore.

How are you showing the results view? Is that in some application that you have, or is this in SSMS? If this is in SSMS - and you...