If I understand your requirements correctly, then you have your constraints the wrong way round. You say

How can I implement both relations, if SQL Server don´t allow me to do...

You're hired Gus... when can you start?:-D

Why did you rule out Log Shipping?

Replication isn't really the tool to use here... even with Merge replication, you still have the concept of a Publisher, Distributor and a Subscriber....

On that...

I think Silverfox and I are in agreement (maybe because we're both in the UK)... I have never worked at a client were there has been such a rigid distinction...

Nope, putting the database into STANDBY won't break the log chain... you can switch between the 2 whenever you want.

GSquared (10/20/2009)

---

If all they're going to do is administer, not performance tune or write code, I'd focus on questions about backup chains and types, I/O performance, that kind of thing....

Just a quick observation... voluntaryprojectid and commercialprojectid are superfluous... projectid should be the primary key (and foreign key) for your specialisation tables.

Just restore the transaction logs "WITH STANDBY" instead of "WITH NORECOVERY" and you will be able to query the secondary database.

Restores take longer using WITH STANDBY, as SQL Server has...

Tut, tut Paul... you're not advocating using undocumented features in production code are you? 😉

The %%PhysLoc%% doesn't really fit the bill here, as the 6th row to be inserted doesn't...

There are also other differences, which may affect the plan:-

@Address is nvarchar(23) in one, but varchar(200) in the other

@ZipCode is nvarchar(5) in one, but varchar(10) in the other

one query refers...

Try:

create procedure p2

with execute as 'my_login'

as

begin

select 1

end

Are you certain that's the SQL being executed when you get the error?

The SQL you posted doesn't have a syntax error, but the error you posted looks a bit like...

You've obviously created a table with some lengthy VARCHAR columns.

As the message tells you, the maximum size of a row is 8060 bytes.

Although the table has been created, and you...

RESTORE DATABASE <dbname>

WITH STANDBY = '<undofile name>'