you normally need to set DCOM permissions, have you done this yet

to give permissions to all tables and views use the roles

DB_Datareader

DB_Datawriter

or just create scripts to grant the permissions to the tables (remove un needed permissions as required)

GRANT SELECT, INSERT, DELETE,...

Truncate is generally more efiicient when clearing the whole table and unlike delete will reset any seed value as well!

Hey, no problem. Remember also, only use EXECUTE AS if you want to inherit permissions from another database user!

just use the following pattern

GRANT permissions list ON OBJECT::storedprocname to databaserole

valid SP permissions to grant are alter, control, execute, take ownership, view definition

according to the KB article, yes.

as the link details the workaround is to un install the mismatched features

i too, use the RSS tool. Easiest way to migrate

has this server been renamed at some point?

Check this link[/url]

download and read the whitepaper

yes, it is.

if they wont convert then yes!! Look at this way, your job should be safe for sometime 😉

Guys, you get the message 'Current SKU is invalid' because of the licence key.

When you get to the part of node 2 install where you see the licence key, delete...

Table\index partitioning is exactly what it says. Within this there are 2 methods of partitioning

Horizontal partitioning - rows are separated into partitions

Vertical partitioning - columns are separated out into partitions

if the database is in Simple recovery the log will truncate on checkpoint, also the alter index is minimally logged so this should not need log file modifications