The problem here is that the variables are declared outside the scope of the dynamic SQL statement...either declare the variable within the dynamic SQL (this might not be of any...

What kind of memory pressure errors are you seeing in the SQL error log? Are you using CLR TVFs, SPs or UDTs?

Have you applied SQL Server SP2? (there were CLR...

SQL 2005 has an additional security check to ensure that passwords for logins meet the strong password requirements (i.e. at least 8 characters long, combines letters,numbers and symbols etc

Either you...

you could also use joins...

SELECT t1.* FROM t1 INNER JOIN t2 ON t1.c1 = t2.c1 AND t1.c2 = t2.c2

Using the @query argument of xp_sendmail should (if I remember rightly) send the results of a query in the mail (in CSV format I think)...

Exec master.dbo.xp_sendmail @recipients = 'me@meltd.com',...

I don't think attach / detach are available from EM in SQL 7.0...you'd have to use the stored procedures for the same...

yes...the NEWNAME option was added in SQL 2000 and isn't available in SQL 7.0...the only workaround (AFAIK) was modifying the system tables directly ()

any specific reason...

did you try setting these options within the dynamic SQL??...something like :

EXEC('SET ANSI_NULLS ON SET ANSI_WARNINGS ON INSERT ' + @ServerDb + '.tblFileNumber (TitleworxFileNumber, OfficeID, RegionID) SELECT TitleworxFileNumber, OfficeID,...

sp_attach_db and sp_detach_db are available in SQL 7.0 also...these can be used to attach and detach databases in SQL 7.0...

works for me too (with and without the single quotes for the names)

ALTER DATABASE MetaData

MODIFY FILE(NAME=MetaData_Data, NEWNAME=MetaData)

GO

ALTER DATABASE MetaData

MODIFY FILE(NAME='MetaData', NEWNAME='MetaData_Data')

What is the exact error description you are seeing?

these can be obtained from IDENT_INCR and IDENT_SEED

SELECT

 Table_Name,

 Column_Name,

 IDENT_SEED(Table_Name) Seed,

 IDENT_INCR(Table_Name) Incr

FROM INFORMATION_SCHEMA.COLUMNS

WHERE

COLUMNPROPERTY (OBJECT_ID(Table_Name),Column_Name,'IsIdentity') = 1

TRUNCATE TABLE can't be run directly against the four-part name associated with a linked server. You'll need to wrap this up with an sp_executesql:

EXEC [AHL_SQL7\WORKSPACE].MarketingCF.dbo.sp_executesql N'TRUNCATE TABLE Mthly_LIF'

I'm not sure if I completely understood your problem -- if you can handle the error in the stored procedure then there should be no problem (i.e. within the stored...

From BOL ("deterministic functions" in the index keyword search):

All functions are deterministic or nondeterministic:

• Deterministic functions always return the same result any time they are called with a specific...

What is the result if 4 part naming is used to retrieve data??...i.e SELECT * FROM <servername>.<databasename>.<ownername>.<tablename> -- does this result in the rows being returned??

and perhaps using SET FMTONLY OFF in the...