Thanks, I just wanted to make sure I wasn't missing something obvious. That seems incredibly shortsighted. Even without licensing issues, we still have to run an entirely separate windows install...

Cool. Thanks guys. Sp4 it is.

Thanks again. Drew, your suggestion worked...I was collating when I set the variable inside the function but not inside the replace statement...once I moved it there, everything seems honky dory...

Thanks Drew - and Jeff if he reads this.

Only issue I'm running into now is that it's replacing characters that shouldn't be, i.e.

DECLARE @1 NVARCHAR(200),

@2 NVARCHAR(200)

SELECT @1 = 'athfawthfawf', @2...

Ratheesh.K.Nair (9/28/2011)

---

Derrick Smith (9/28/2011)

---

Just a note here, the active transaction may not be in tempdb. It's most likely in your app database and is just using tempdb and therefore wont...

Since you just mentioned the 15 row number...why are you indexing a 15 row table? Unless it's 300 columns wide or has ridiculous XML/varbinary(max)/image fields, reading 15 rows is incredibly...

That would likely be best handled by one index unless you have some really odd where clauses or selects:

CREATE NONCLUSTERED INDEX idxEVendors_Z1 ON #EVendors

(BuyerNumber, VendorNumber, WarehouseNumber)

INCLUDE (Whatever COLUMNS ARE...

gregory.anderson (9/28/2011)

---

Rob Schripsema (9/28/2011)

---

I'll venture that the 'OR' clause in the join statement is the issue here. You're looking for values that are either NULL (at one end of the...

You're right. If you have three very different queries (pulling off different columns completely), then you should usually have 3 separate covering indexes to support them.

As with all things though,...

You'll get a different error if the login has the wrong password/no permissions/etc. To verify this, you can check the log on the server it's trying to connect to. If...

Just a note here, the active transaction may not be in tempdb. It's most likely in your app database and is just using tempdb and therefore wont show up with...

Can you post the create table definitions for the Member_Time table?

It sounds like the member_time.date or member_time.time_out fields are not datetime fields and are probably varchar, and you have at...

Try changing it to this:

DECLARE @sql NVARCHAR(4000)

SET @sql = 'BACKUP DATABASE DB TO DISK = ''\UNCPath\DB.BAK''

WITH COPY_ONLY, NOFORMAT, NOINIT, SKIP, NOREWIND, NOUNLOAD, COMPRESSION, STATS = 10'

EXEC...

You'd have to switch it around:

--Run on prod server

set IDENTITY_INSERT [dbo].

ON

INSERT INTO [dbo].

([ReportID]

,[ReportName]

...

That best practice rule sounds like the case of having 1 instance on each node and being able to run both in case of a failover, i.e.

Two nodes

32gb each

Two instances

Each...