i think the issue is related to teh name not being #tbl_temptable, but actually [#tbl_temptable[100underscores]0000000000F0]

for example. if you do this after you know your table exists :

SELECT table_name,

column_name 'Column...

the INTO belongs outside of the openquery:

CODE

SELECT *

into #tlb_testfile

FROM OPENQUERY(test_TERADATA,

'select *

from databse.file

where

datacode=''49548''

;')

if you have a datetime column for WHEN the data was actually entered, you could compare that to a TallyCalendar table(which you wanted to avoid) and get the DST offset.(ie...

sp_changeobjectowner 'wrongschema.procname','dbo'

a lot of the work around examples so far would return false positives if the values are two or more digits, thought right? 2|5|21|23|55 for example

redesign, or split the data...

there. fixed it for you. 😛

ok peers: poke holes in this: this seems to do what the oldstype autfox would do, right?

well...this just generates the statements...i'd have to execute them:

SELECT CASE

...

daveriya (11/11/2011)

---

no its not in the master database or under system stored procedure.Any other option,while creating it i didint use 'USE DATABASENAME'.

but i know i have selected correct database on...

in theory, we should start using the ALTER USER xxx WITH LOGIN =xxx syntax for fixing orphaned users now, right?

what do you typically do if a USER exists in a...

make sure you didn't create it in the master database by mistake.

it's possible that it is in the "System Stored Procedures" folder if someone ran EXECUTE sp_ms_marksystemobject 'YourProcName' on the...

kick yourself:

EXECUTE @sqlstmt looks for a stored procedure.

EXECUTE (@sqlstmt) executed they dynamic query.

dammit...tricked into doing homework again, is that what you are saying, my friend? 😀

is the server witht eh memory problem one of many on the same virtual server? could it be that instances are eating up 100% of the available memory, and #20...

there's no need to test an EXISTS either...if you are in the trigger, of course there are rows.

this will be what you are after i think:

CREATE TRIGGER Trgr_Update_LastModifiedOn

ON SERVERINFO

AFTER UPDATE

AS

...

NO.

your error is a logical one:

look at your trigger, it says this:

UPDATE SERVERINFO

SET LASTMODIFIEDON = GETDATE()

that...