Sorry but you CAN change the table columns not referenced by the VIEW even when it is defined with SCHEMABINDING!

Fix your "correct" anwers.

create table dbo.test ( col1 int, col2 int,...

Note that it didn't work while trying to delete files "across the network". but that does not means that it will never work.

In 2000

get the sql_handle for the spid and use

DECLARE @Handle binary(20)

SELECT @Handle = sql_handle FROM sysprocesses WHERE spid =

SELECT * FROM ::fn_get_sql(@Handle)

In 2005 use

SELECT session_id, text

FROM sys.dm_exec_requests...

note that stored procedures allow for deffered name resolution and you may be missing something although the procedure code didn't complain

From BOL: ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/d308d9cb-bb85-46f6-93c6-e2ddd0fa01c3.htm

Note:

AWE is not needed and cannot be configured on 64-bit operating systems.

Tables partitioning are not *that* great either. Be really careful before you jump into that, thinking that "peformance" is its primary feature, it is *not*.

In addition when replication is involved...

First suggestion: UPDATE your STATISTICS. when you installed the SP you may have flushed the cache

Suggestion #2 NOLOCK statements on the FROM of an update statement are supposed to be...

this is *really* funny

space available: xp_fixeddrives

can you post the DDL for dbo.afectacion table ?

Timestamp is *not* a datetime in MSSQL

check your app.

SET PARSEONLY ON

-- Execute your query

SET PARSEONLY OFF

The functions of this service remain unchanged: These are the functions described in the 2000 version of the product

http://support.microsoft.com/kb/934459

If the view can be converted to an "indexed view" it *is* possible to replicated the view as a table.