Viewing 15 posts - 3,226 through 3,240 (of 5,843 total)
as2higpark (8/1/2011)
We finally moved the DB...
August 2, 2011 at 8:27 am
"cheap" and "high performance" just don't go together. I would bet your hardware is not up to the task you are asking either. If other database platforms offer...
August 2, 2011 at 8:03 am
1) I would shut down sql server and other processes on the box and run chkdisk.exe (you can use -? to get options) to find possibly bad sectors on the...
August 2, 2011 at 7:58 am
1) Ninja hit it, and I doubt we need query plans to verify it. Your original code was set up to use nvarchar datatypes or joins and now you...
July 28, 2011 at 5:53 am
Are you trying to load to the free SQL Express edition? That has a 2GB file limit in SQL 2005/2008 and 10GB limit in 2008R2.
July 28, 2011 at 5:50 am
There is a very precise reason why your max used memory only gets to 1700MB or so. a) it is a 32 bit system, which under default configurations can...
July 27, 2011 at 5:50 am
1) consider moving your reporting off to another server. Log shipping is great for this if you only need say yesterday's data 'freshness'. Large-scale reporting against production databases...
July 26, 2011 at 7:07 am
Stop using maintenance plans. They have lots of issues, especially when it comes to indexes/statistics mx. Get the awesome, free and fully documented stuff from ola.hallengren.com
July 26, 2011 at 7:03 am
ksvr99 (7/25/2011)
can you please tell me which connection manger (OLEDB or ADO.NET ...)do we need to use to...
July 26, 2011 at 7:02 am
Read the book(s) and any blogs/articles written by Allan Hirt.
July 26, 2011 at 7:00 am
I second the recommendation for using sp_whoisactive. See sqlblog.com for latest version and a 30-day blog series on how to effectively use the awesome free tool.
July 21, 2011 at 9:20 am
You simply must make improvements to your schema/data to allow you to remove the ISNULL(A, B) = something. Not only is it a CPU burn, it also voids index...
July 21, 2011 at 9:19 am
1) and (@filter = 0 or mas_id in (
That is a horrible construct for the optimizer. split this big mess into two separate pieces of code,...
July 21, 2011 at 9:15 am
>> One row can't be written on two pages. Keeping this in mind 8K was choosen as 4K would be too short and every row would have to be <...
July 21, 2011 at 9:10 am
Typically this wait indicates that the calling app is not consuming the rows as quickly as SQL Server wants to spool them out. Poorly written app, network bottleneck, overloaded...
July 20, 2011 at 7:20 am
Viewing 15 posts - 3,226 through 3,240 (of 5,843 total)