Sounds like client side setting issues. Are you running any antivirus on the server? Which is the rpc error you are experiencing?

To start if you encrypt the data you will complicate queries etc on the back-end and you could even loose the index usability (depending on the encription)  on that column. On...

>> Sorry if I seem ignorant, but what is a bad practice? <<

 To have owners on objects other than dbo.

I would like to stress though that there are very very ... did...

I think PW is in the right track. At insert/Update time you could pass from the client the Value needed (max/min/arcosh..) then your query will be a simple select

1. it should be UNION ALL (not UNION).

2. I would do it with a combination of inline functions instead of UDF is the set is large

3. SQL is optimized for ROW...

Yes you should even though it is a bad practice (everything should be owned by dbo) I would check and to change that you need

sp_changeobjectowner 'objname', 'user/role' -- preferably a...

alternative you could use

select serverproperty('ProcessID') -- on each instance.

you can use DMO to loop through the isntances and retrieve the ProcessID property of the SQLServer object if you need...

Both data and structure updates

It is my opinion that the UI really does not matter. you can even create a script with osql and run it using a pointer to...

In SQL Server you have two options.

1. Repeat the expression

2. Use the expressions on a subquery like

Select .... NewAlias + ....

from ( select *, (fld1+fld2 * fld3 ) as NewAlias from...

you don't need a join for that, just:

SELECT QtyContracted1,ContractPrice,  Amount*2   

FROM 

      (select *, (QtyContracted1*ContractPrice) AS  Amount from  TCA20007 ) a

HTH

OR you could install the Developer Edition

been there done that

the following procedures require securityadmin at least

sp_password

sp_sqlagent_msx_account

sp_revokelogin

sp_remoteoption

sp_defaultlanguage

sp_helplogins

sp_grantlogin

sp_dropremotelogin

sp_droplinkedsrvlogin

sp_denylogin

sp_addlinkedsrvlogin

sp_defaultdb

sp_droplogin

sp_addlogin

sp_validatelogins

sp_addremotelogin

the following statements also

GRANT ALL

GRANT CREATE DATABASE

Therefore you could either grant permissions to an special login (which I don't recommend) or The logins...

 >> I think that SELECT @err = @@error will ALWAYS resolve to 0<<

Allow me to differ.

You MUST use  Select @err = @@error, @cnt = @@rowcount because is the only way...

Just see my comments about some ways of implementing pesimistic locking mechanisms on sql server on this thread:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=152781#bm152867

HTH