Good luck. I'd be interested in hearing how this turns out and what the reactions are.

Steve Jones

steve@dkranch.net

You can designate any stored procedure to run at server startup. In sql 2000, you set the server to run these with:

sp_configure 'scan for startup procs', 1

Set the procedures with

sp_procoption

Sets...

Good idea. Also, if you can give the names of the columns and table that are not working, we will try to test it.

Steve Jones

steve@dkranch.net

I agree with Andy. Look at replication

Steve Jones

steve@dkranch.net

wow, covert DBAs, never dealt with any 🙂

Steve Jones

steve@dkranch.net

You could write a stored proc to do it and make it a startup proc.

Steve Jones

steve@dkranch.net

I wasn't aware they could be hidden? The default instance will respond on port 1433. Named instances use other ports, but I can't remember off the top of my head...

Not sur why that wouldn't work. Smalldatetime is just a little smaller (in size) than datetime.

Glad its mostly working.

Steve Jones

steve@dkranch.net

I also use David's technique.

Steve Jones

steve@dkranch.net

transactional isn't that much overhead, especially if you move teh distribvutor to another server. What's a lot of transactions? I've had this work in a few solutions as the overhead...

I've seent his before. We had to uninstall nad reinstall the client.

Steve Jones

steve@dkranch.net

Actually Andy, I found the skeleton for such a project on msdn. When i get back to work, I'll post the link.

btw, how do you get to presecute the offenders?...

no second case needed.

declare @cmd varchar( 100), @x int

select @x = 1

select @cmd = 'this' +

case when @x = 1

then ' or...

Its

select @cmd = 'update ' + @targettable + ' set ' + @variable + ' = ' +

case when @datatype = 'int'

...

character and date types need quotes.

Steve Jones

steve@dkranch.net