In the very unlikely event that someone else has the same problem I thought I would post my solution.

Turns out when I changed my server from dynamic ports to static...

And I vote...

Yes, and thanks for all of your help. I finally tracked it down about the time you posted your last post.

The way I have it is that if...

pixye.sb (3/29/2011)

---

I map 'sa' and 'pinco', which are both sql server logins, with the same remote login 'si'.

If instead of Sql Native Client I use Ole Db Provider for Sql...

Name: SQL03.domain.company.com

Type: REG_SZ

Data: DBMSSOCN,sql03.us.aegon.com,1433

The other key also...

One of my server guys pointed out that the SQL03 instance is on port 1433. Could that be causing the behavior I'm seeing? I've never put a named...

Windows Server 2003 R2

SQL03\SQL03

Thanks again

Kenneth

I don't do much with clustering but 2 possiblities,

1) Is pinco a SQL login or an AD one? If its an AD login that may be part of your...

Perry Whittle (3/28/2011)

---

Kenneth

what does the following return when executed against the instance

SELECT SERVERPROPERTY('ComputerNamePhysicalNetBIOS') AS ComputerName,

CASE (SELECT SERVERPROPERTY('ISCLUSTERED'))

WHEN 1 THEN 'VirtualName = ' + CAST(SERVERPROPERTY('MachineName') AS NVARCHAR(25))

WHEN 0 THEN 'Not Clustered'

END...

Business Intelligence Development Studio (what its called under SQL Server). Otherwise known as Visual Studio.

paul.knibbs (3/17/2011)

---

And see mine was an Atari 800 with 800 BYTES of memory. And that was impressive for the time. And I was jealous of my friend who...

Jeff Moden (3/15/2011)

---

Heh... my first desktop computer had 8K and I had some serious bragging rights because I had twice the memory everyone else...

As GSquared said use raise error.

CREATE TABLE table1 (column1 int)

GO

CREATE TRIGGER [dbo].[TriggTest]

ON [dbo].[Table1]

FOR INSERT

AS

BEGIN

IF EXISTS ( SELECT * FROM INSERTED WHERE COLumn1 > 100)

BEGIN

ROLLBACK TRAN

RAISERROR...

Well our server is nothing all that exciting based on this list but its 72GB. Of course its used by maybe 10-20 users and the memory is there entirely...

Based on the XP its an extended stored procedure which would be listed in SSMS under ServerName->Databases->SystemDatabases->master->programmability->Extended Stored Procedures->

Of course if its just named that way and is a regular...