Grant Fritchey (10/27/2015)

---

Great Summit so far. I've been able to talk to Gail & Lynn and Rod. Saw Gianluca as I was running between events. Any Threadsters I'm missing, track...

Struggle

Would this produce the correct behavior?

CREATE TABLE EDI_data_proc_log(

ID int IDENTITY(1,1),

comment VARCHAR(3000),

time_recorded DATETIME DEFAULT GETDATE(),

run_by varchar(100),

duration int );

GO

CREATE TRIGGER TI_EDI_data_proc_log ON EDI_data_proc_log

INSTEAD OF INSERT

AS

INSERT INTO EDI_data_proc_log(

...

Corrected version for...

The only columns mentioned have been Price, Rating and Location. If rating is a single value, I'll assume that location would be as well (You won't be looking for hotels...

Here's a different approach with 2 variants:

DECLARE @StartDate DATE = '01/01/15';

SELECT DATEADD( YY, DATEDIFF( YY, 0, @StartDate), '18991106'),

DATEADD( YY, DATEDIFF( YY, 0, @StartDate), -56),

...

Or maybe this: =Format(Fields!Total.Value,"C")

I'm not sure about this, but you could give it a try:

https://msdn.microsoft.com/en-us/library/3352e6f5(v=vs.90).aspx

Then you need to trust your queries. Try tweaking this to get what you need.

SELECT OBJECT_NAME( object_id), *

FROM sys.sql_modules

WHERE definition LIKE '%ColumnName%'

AND definition LIKE '%TableName%'

SELECT OBJECT_NAME( object_id), OBJECT_NAME( referenced_major_id)

FROM sys.sql_dependencies

Ok, trying to bring this to the original topic.

This is what I was thinking as an approach.

Select Top(10) HotelName, Price, CustomerRating

From dbo.VacationDestinations

where Price <= @price AND CustomerRating = @CustomerRating

Order...

An easy way to do it, is by using SQL Search: https://www.red-gate.com/products/sql-development/sql-search/

You could also query things on sys.sql_modules.

Jeff Moden (10/24/2015)

---

Careful now... Do you know what the maximum length of each parameter will be? Me neither. But I can tell you that the maximum length allowed...

Girls

I'm not sure if this is what you're looking for:

SELECT e.id,

e.NAME,

e.sdate,

e.edate,

CASE WHEN ROW_NUMBER() OVER(...

Considering that this fix is included since version 10.50.1797.0, you should have it.

Reference: https://support.microsoft.com/en-us/kb/2534352