Search always was a bit odd on this site.

Just tried search on "windows surface" - no results -I wasn't surprised but I had expected someone to mention it....

There is no default sort order, so SELECT * FROM Table is not guaranteed to give the same sequence you put the records into the table.

The column you added cannot...

herladygeekedness (9/13/2012)

But what you are saying is that potentially changes in the source servers could cause this in my package? I have to assume that indexing of the hosted...

If you haven't changed the package, then Something must have changed on the SQL Server.

My starting point would be to ask 'TheirRealDBAness' if there are any new indexes, or triggers...

1) Are you running the stored proc in a transaction, as you mentioned you want to be able to rollback. If you do SQL Server will be very slow...

A number of points here.

If your web application runs all its SQL activity in a single transaction, then recycling the worker process should not cause any problems.

However if...

I'm not sure if this is the best way, given you have a fairly small fixed data set, but it's an excuse for a dynamic pivot.

First get all the column...

replace the untouchable 'BA#' first, then do the main replace, then put the 'BA#' back

SELECT REPLACE(REPLACE(REPLACE(@STRING, 'BA#', '***'), 'A#', 'C#'), '***', 'BA#')

L' Eomot Inversé (9/6/2012)

---

Tom Brown (9/6/2012)

---

Anyone from the UK remember BT Phone Day - back in the 1990s sometime, the UK phone company changed all number prefixes to add...

Lynn Pettis (9/6/2012)

---

Tom Brown (9/6/2012)

---

Anyone from the UK remember BT Phone Day - back in the 1990s sometime, the UK phone company changed all number prefixes to add a...

Anyone from the UK remember BT Phone Day - back in the 1990s sometime, the UK phone company changed all number prefixes to add a 1 - so 071 became...

OutGeeked

http://qa.sqlservercentral.com/Forums/FindPost1354183.aspx

(Thanks Lynn didn't know they're deprecating my favorite script)

Ssssshhhhhhhhhhhhhhhhhhhhhhhhhhhh!

you might wake me up

Orphaned users are easy to fix:

-- show users not mapped to a login

EXEC sp_change_users_login 'Report'

-- map database user OrphanedUser to Login OrphanedUser

EXEC sp_change_users_login @Action='Update_One', @UserNamePattern='OrphanedUser' , @LoginName='OrphanedUser'

Using one of Jeff Moden's splitter functions

DECLARE @pString VARCHAR(MAX) = 'BUILTIN\ADMINISTRATORS: [System Admin]YES;[Security Admin];[Server Admin];[setup Admin];[Process Admin];[Disk Admin]YES;[Database Creator];'

DECLARE @pDELIMITER CHAR(1) = ';'

;WITH SPLITS AS (

SELECT ItemNumber = ROW_NUMBER() OVER...