The collation of my database is sql_latin1_general_cp850_bin

is a binary collation, so yes, that is case sensitive;

unless you know it's a mistake, the collation must have been put in place for...

it depends on the collation of the database you are connecting to.

if you create a database with a case sensitive collation, all the tables and objects are going to require...

sql_butterfly (2/24/2011)

---

We have one procedure where after join some tables the records are put into one temporary table (this step is processed fast). Now at the end when we are...

I just checked, and if you restore from a backup, and change the database name to a new database, it does not trigger the create_database event...so my trigger example wouldn't...

I've done what you are asking with a server wide DDL trigger that looks for the CREATE_DATABASE event;

basically, my example is whenever a database is created, a suite of specific...

this is the syntax I typically use;

looks the same as yours too me:(the forum hates{slash n} so you have to html escape it)

CREATE TABLE BULKACT(RAWDATA VARCHAR (50),MoreData varchar(50))

BULK INSERT BULKACT...

SKYBVI (2/23/2011)

---

Thats wrong ,

How can u add the 90 degrees between 3 and 6...

if time is 3:40, the hour hand has moved a lot towards 4.....

Just give it a thought.

Thats...

I...

ok, you should be able to streamline your trigger, and configure it for multiple rows as well.

see if this makes sence to you:

ALTER TRIGGER [dbo].[Update2ndTable]

ON [dbo].[Table1]

AFTER INSERT, UPDATE

AS

--if there is...

mzettler (2/23/2011)

---

with no...

you'd need a lot more details to get a more refined answer, but offhand, this might get you started:

SELECT

'http://tgl.test.com/plc/login/confirm.asp?'

+ 'c=' ...

there's no need;

SQL server is designed to work in sets; so the time it takes to apply a calculation against 1 row of data is about the same as 10K...

this is a fairly common requirement.....delete lots of data, but not the look up tables kind of thing.

the things to watch out for are the order of the deletes...you can't...

personally i use an integer with a check constraint limiting values to 0 and 1;you could use a BIT data type,but I like an integer to anticipate those situations where...

here's a cursor example that is based on what you posted:

DECLARE @CustNo VARCHAR(MAX)

DECLARE @SQLQUERY VARCHAR(MAX);

SET @SQLQUERY = ''

declare c1 cursor for

select

CustNo

...