Luis Cazares (9/21/2015)

---

WayneS (9/21/2015)

---

Kristen-173977 (9/20/2015)

---

GilaMonster (9/19/2015)

---

protecting against SQL Injection is done, in most cases, by ensuring that it is parameterised, except for the rare scenario where the user input...

This really looks like a trigger. Check for db-level (DDL) triggers. If not, check for server-based triggers (that seems unlikely in this case, though). For example:

SELECT t.*

FROM...

SQL provides some help here.

You can use missing index views

sys.dm_db_missing_index*

and the index stats view:

sys.dm_db_index_usage_stats

to help determine what indexes to create.

First and absolutely foremost, you need to determine and implement the...

If you don't require an nvarchar search, you can use varchar and get 900 chars to search.

Since you're always searching at the start of the string, you could add a persisted computed column of ~900 bytes and search on that:

ALTER TABLE ourtable

ADD bigcolumn_search AS CAST(LEFT(bigcolumn, 450)...

Here's another method to try, just in case:

SELECT

ta.last_name,

ta.first_name,

tb.ID

FROM

TableA ta

INNER...

That code is dependent on the DATEFIRST setting, and I don't believe it's accurate anyway. Maybe this?:

--additional dates for testing/verification

INSERT INTO #weekdays (datevalue, numericvalue) VALUES

('20150101', 1000),

('20150102', 1001),

('20150103', 1001),

('20150104', 1001),

('20150105',...

The design is basic, but it seems workable for very straightforward messaging.

Just some possibilities, not necessarily better than what you have:

1) I agree with an identity column on the Message...

If instead of sync'ing up just once a day, or some other slow schedule, you want an up-to-the-second value, why not just get the value from the actual table itself...

I was just using CAST to show that it would avoid the implicit conversion, but it still didn't resolve the need to recompile. This is just a failure on...

Thanks for the follow up.

Interesting, and bizarre. We can prevent the implicit conversion using CAST. But we still have to recompile even to avoid a full query scan...

Kristen-173977 (9/16/2015)

---

We do both ways and I can't say I've ever known...

If you're going to allow that, easiest would be to then quote all the values:

Select 'Apple=''5'',Orange=''10,11,12'',Banana=''11''' UNION ALL

Then you can use the same technique with a delimiter of ''',' instead...

Maybe you could do something like this:

CREATE PROCEDURE dbo.GetSomeData (@rptType INT, @customerID INT)

AS

SET NOCOUNT ON

IF @rptType = 1

EXEC dbo.rpt_1 @customerID

ELSE IF @rptType = 2

...

My understand was that all operation codes needed shown, not just the two being checked.