i think you answered this in your first post...but just in case...

can you go to this spot and put sql files in there? does that make any difference?

i know...

show us your trigger, and we can help you tweak it to handle multiple rows as a set based solution..

as far as whether it's insert/update/delete, if there is any data...

there is a view you can use, that is mostly correct:

SELECT OBJECT_NAME(REFERENCING_ID),* FROM sys.sql_expression_dependencies

WHERE OBJECT_NAME(REFERENCING_ID = 'YourProcName'

issues can arise sometimes, becasue you can create a view that references tables...

definitely the conversion in there: here's a stark example...you'll see none of the results are the same,all due to the conversion issues:

/*

(No column name)(No column name)(No column name)(No column name)(No...

ok, i can duplicate some of what you are seeing...

try this, which is barely modified form what you posted....

i get chinese characters from my loginnmae due to the conversion:

what i...

as far as I know, the data type and sizes should always be varvbinary 128 and nvarchar(64), right?

wouldn't an implcit comversion form nvarchar to varchar mess up the data?

or is...

you can do what you want with the dateadd/datediff functions

In this case, one easy way to do it is to find the beginning of the month for the date in...

as far as i know, you could use a case sensitive specific, but all the examples i've tripped on here in the forums always go compare binary; some collations cannot...

i think you'll have to bulk insert into a staging table, and then move fromt he staging table to a final table. BULK insert doesn't have any data massaging like...

yes...all you have to do is COLLATE using a case sensitive collation just for the comparison/where statement:

...where name <> upper(name) collate Latin1_General_BIN

SELECT

CASE

WHEN 'India'...

Stefan one of the things i love to do is test the permissions... you don't need to login as them or anything.

for example, supposed add a user to a database......

Stefan Krzywicki (6/7/2011)

Thanks, I'll take a look at that. It is actually a single person I'm granting access to a single table. In the scenario I described, they shouldn't see...

not really a basic question; usually developers are used to having full permissions on everything, and preventing access isn't really part of the picture until later.

SQL is deny by default...so...

is every field dbl quote delimited, regardless of value being integer, decimal or string, or just strings?

please post back if it works for you; this same issue comes up on otehr posts, this is the first time i really jumped in at it.