Some of the code here may help:

http://www.sqlservercentral.com/articles/SQL+Server+2008/66554/

As you have an aggregate function on OrderDate it does not make much sense to have it in the GROUP BY clause.

Try:

GROUP BY I.ProductID, I.Description, I.UnitsInStock, I.UnitPrice, I.Expires--, O.OrderDate

Edit: Using...

As you have not raised an error or returned within the CATCH block I think the code will continue to execute.

(Edit: This will depend on what XACT_ABORT is set to.)

Try...

netguykb (2/2/2010)

---

NO IDEA How to do this. Here is what I have so far and I know this is not right considering the where clause is only allowing me to...

If you do not have access to the application code, you could look at using a trigger to clean the data as it was being saved.

You may also find this thread useful:

http://www.sqlservercentral.com/Forums/Topic754864-169-1.aspx

With inner joins where the filter is applied seems to make no difference. The optimizer generally sorts...

You may want to redesign your schema.

With your current schema, something like the following may work:

SELECT dCats.[NAME]

,refTable.[Id]

,'Default' AS CatType

FROM tbl_categoriesRefTable AS refTable

JOIN tbl_defaultCategories AS dCats

ON dCats.defaultCategoryId = refTable.defaultCategoryId

AND dCats.universityId =...

ALTER TABLE dbo.docfol

ADD CONSTRAINT FK_folderid_folder

FOREIGN KEY folderid

REFERENCES dbo.folder(folderid)

GO

ALTER TABLE dbo.docfol

ADD CONSTRAINT FK_docid_document

FOREIGN KEY docid

REFERENCES dbo.document(docid)

GO

Umm.... Works for me.

Copy the code exactly - spaces are important.

Also, there is no keyword DESC in my code.

Or maybe some dynamic SQL:

DECLARE @sql varchar(MAX)

SET @sql = ''

SELECT @sql = @sql

+ 'SELECT ''' + table_schema + ''', '''

+ table_name + ''', '''

+ column_name+ ''', COUNT(' + column_name...

As you have a strong SQL background, I think the best way to start with .Net is learn ADO.net 3.5.

If you know ADO.net well you should be able to get...

A merge join (lookup in BOL) can only use one index on each table. The join and filter conditions are:

col_detail.[timestamp] -- first to get om.[timestamp] >= @dt_temp

col_detail.DealID - used to...

jocampo (11/6/2009)

---

I believe your Index creation code is the same I'm proposing, right? Three separate non clustered indexes for each of the columns participating on the join condition ... am...

I cannot look at the queryplan at the moment but:

1. In SQL2008, using MERGE is safer than UPDATE FROM as it avoids non-deterministic problems

by throwing an exception if a one...