Viewing 15 posts - 376 through 390 (of 391 total)
run SP_who2 and see what process is blocking?
August 24, 2010 at 1:30 am
Thanks, interesting way of looking at the problem.
Also you could change the WHERE clause to
WHERE N <= DATALENGTH(CountryName) instead of using the SUBSTRING comparison.
The example...
August 3, 2010 at 1:54 am
Dont mean to put a downer on the conversation, but I was looking at a code generated query today which was running very slowly - subquery upon subquery upon subquery...
March 10, 2010 at 3:19 am
You'll need to respond about whether there are indexes available..
Also try running it with just the empid join, then modify it for just the name string join and see how...
February 24, 2010 at 12:20 am
Cast the empnum's as INT and remove the 0000 concatenation / string comparison.
Remove the CHARINDEX function and try "a.account LIKE '%' + @query + '%' "
February 22, 2010 at 9:35 pm
Just an FYI for anyone who gets the editorial via email... the book "Protecting SQL Server Data" is advertised for sale from amazon below the editorial, but you download...
January 26, 2010 at 3:48 pm
Can you check the actual execution plan? Maybe limit the subselect to top 10 results first. It's probably cascading the delete to other tables etc..
Also find out how...
January 20, 2010 at 6:46 pm
WITH cte(warehouse, product,req_quantity, batch_number,RowNumber) AS
(
SELECT a1.warehouse, a1.product, a1.req_quantity, a2.batch_number,
ROW_NUMBER() OVER(PARTITION BY a1.warehouse, a1.product ORDER BY fifo_date ASC) AS 'RowNumber'
FROM #wms_requirements a1
INNER JOIN #wms_batch_queue a2 ON a1.warehouse = a2.warehouse...
January 19, 2010 at 6:25 am
"The key, the whole key, and nothing but the key, so help me Codd."
Sorry but I cannot agree with this editorial. Im not a senior dba or developer or...
January 18, 2010 at 11:43 pm
It's almost a complete cultural shift in the way support is handled these days. "Service" is no longer king and cost-cutting / price takes precedence. Think of the...
January 14, 2010 at 12:51 am
I selected "nothing" however I've had issues in the past with the default "max server memory" setting being set at 2147483647 MB on 64 bit systems. Setting the max...
January 7, 2010 at 11:44 pm
For SQL 2005 sp3
For SQL 2005 sp2
SQL 2000 Reporting services
October 13, 2009 at 6:09 pm
How did you resolve this?
I have a very similar issue using the EXECUTE AS statement with sysadmin rights and getting the same error message.
July 22, 2009 at 7:55 pm
Viewing 15 posts - 376 through 390 (of 391 total)