I couldn't agree more with "vegas205". If you are not specific on the question the ONLY answer is to disable.

Brian, disabling TCP/IP doesn't mean that you can not reach the...

The question didn't specified ANY version. I hope if you are using SQL Server you have SP3a on it!

Disabling the port is BY FAR the BEST!!! way.

This port is not indispensable for an application, in fact that’s why firewalling was suggested.

If you firewall the port, it is...

To add my two cents if you use the quoted value on a parameter that is used for dynamic TSQL take a look at QUOTENAME on BOL

HTH

you could follow this steps:

1- remove all those users from the DB

2- use sp_addalias 'userlogin', 'dbo'

3- repeat step2 for all those users

Procedures created with those logins will have dbo.procname form!!!!

Note:

-...

if accurate timing is needed you should use DBCC FREEPROCCACHE before running each one of them otherwise you may be using a precompiled plan

just my 2 cents

The solution to this problem is to handle the error message on the CLIENT side. In other words use structured exception handling, trap the exception and translate the message to...

quote:

---

WORKGROUPS

----------

38.0 1.0 100.0 Styling 0

39.0 2.0 100.0 Non Surgical 0

40.0 2.0 105.0 Nails 0

41.0 2.0 110.0 Wax/ Electro 0

DEPARTMENTS

-----------42

38.0 100.0 Cut/Finish...

The Identity Seed Gets incremented every time you insert a record!

if you want to reuse the Identity value that you deleted then you must run:

DBCC CHECKIDENT ('able Name', RESEED, 'reuse...

There are other implications that were not mentioned here like:

DTS DOESN'T WORK on fiber mode and that is huge for some enviroments.

You have several options. These are just some:

1- you could use a trigger in one to update the other using three part names

2- you could use a linked server...

For the intended purpose TRIGGERS are the way to go without barely any effort

I believe this code:

 

IF NOT EXISTS (SELECT 1 FROM MyTable WHERE MyField = @Value)

    BEGIN

       ...

In my opinion this is a design issue. I would change from View to a Stored Procedure with the parameters necessary on your Where Clause.

IF it has to be used...

Just One more thing. You are using a One-Statement Update, so The BEGIN TRANSACTION and COMMIT TRANSACTION Statements are NOT neccessary, in fact they are NOT recomended for a single...