BUG in SQL Server Manager - Default Schema

Hallo,
June CTP of SQL Server 2005 (NOT SQL Express)
########
Everything deleted from this post by Alle since it has no relevance to the RTM.
Unfortunately I can not delete the thread.
###########
Alle

There is now an invisible comment that has been added by a moderator (I hate that too, why isn't the comment / edit visible in the thread?) :

=== Edited by Paul Mestemaker - MSFT @. 28 Oct 2006 1:59 AM UTC===
This is a comment not a question. This bug has been fixed.

Paul,

you are absolutely right, it was fixed ages ago and in addition we are well over the CTP stage of SQL Server 2005 which was RTM one year ago.

Wouldn't it make much more sense to delete this entire thread since it now longer has ANY revelance?

I can't although I am the author (I tried).

Thanks,
Alle

BUG in SQL Server Manager - Default Schema

Hallo,
June CTP of SQL Server 2005 (NOT SQL Express)
########
Everything deleted from this post by Alle since it has no relevance to the RTM.
Unfortunately I can not delete the thread.
###########
Alle

There is now an invisible comment that has been added by a moderator (I hate that too, why isn't the comment / edit visible in the thread?) :

=== Edited by Paul Mestemaker - MSFT @. 28 Oct 2006 1:59 AM UTC===
This is a comment not a question. This bug has been fixed.

Paul,

you are absolutely right, it was fixed ages ago and in addition we are well over the CTP stage of SQL Server 2005 which was RTM one year ago.

Wouldn't it make much more sense to delete this entire thread since it now longer has ANY revelance?

I can't although I am the author (I tried).

Thanks,
Alle

buffered trigger

Hallo i need to read/write data using triggers between two remote MSSQL2K servers, over an unstable connection.
Can trigger operations be buffered, so they are completed when connection is on?
Or should i make the triggers to write into local tables, then replicated in merge? (i would like to avoid this)

No. Trigger is part of the active transaction so if you have an unstable remote connection, I would suggest you queue your data into a worker queue table and process it later. I suggest you take a look at Service Broker in book online. It's designed for message queue/processing.

|||

This asyncronous read/write data can be resolved using SQL Service Broker a feature of SQL Server Express 2005 (that is free).

My ideea is :

1.The trigger of SQL2K1 server write the data in a Table1 of SQL2K1

2.SSSBroker get the data of Table1 in a Table2 from SSEXPRESServer in a Database1

3.From Table2 SSExpress copy data to SQL2K2

HTH