Interestingly enough I read the blog yesterday Colin. Very informative. Thank you very much.

My concerns with not allowing SQL to manage memory is that this is a clustered...

Yes, it is a ferret holding a beer. However his face has been blacked out to protect his identity so you were not supposed to know that. If...

Duran:

1. Is it better to configure backups through the backup snap-in or through maintenance plans?

Better is not really the question. It comes down to what you feel most comfortable...

Additionally, you can not completely avoid a SQL footprint on C. Shared tools, among other files, will be installed on C regardless of what you set up during the...

[font="Arial"]I am encountering similar issues on 2 of 3 nodes in our Clustered SQL 2005 Enterprise x64 environment. It appears to happen when Tivoli Storage Manager is writing from...

Your specs state your RAID setting for data is going to be 10. I recommend that you go with RAID 5 if performance is going to be a factor....

To follow up on the code presented by ksullivan:

create proc up_EmpDelete

@SSN char(9)

as

DELETE FROM employee WHERE ssn=@ssn;

You would then execute the stored proc as follows: to delete all records...

The reason I asked about the INSERTED and DELETED tables is that you'll query them for the value you just updated. The values from the last transaction are stored...

Glad to hear it. IMHO you should always use set-based queries whenever possible. Avoid functions in the WHERE clause.

- Tim

Grant, nice to hear from you man... missed you...

Are you familiar with the INSERTED and DELETED tables?

That's because all the data you inserted into the value field was able to be converted to BIGINT because it is numeric. That is why the error code is...

Don't use an IN/NOT IN clause, use a LEFT JOIN instead and throw the CAST on the BigIntColumn in the JOIN as follows:

--CREATE TABLES

CREATE TABLE datatable (BigIntCol bigint)

CREATE TABLE ExclusionsTable...

Don't forget INSTEAD OF triggers as well.

I think you should look at implementing steps in your application code to prevent "bad" data from ever getting into your database to begin with. Performing rollbacks from within...

Another thing to think about is this: Access has a default login of 'Admin' with no pwd. Try that combination for the security in your linked server and try...