Tag Info

New answers tagged

2

That's a lot of NTEXT columns. You should know NTEXT is deprecated and you should consider refactoring to the newer datatypes, eg NVARCHAR(MAX). Regarding your specific problem, depending on what version and edition ( eg select @@version ) of SQL Server you are using, you could consider partitioning. Here's a simple demo of this might work for you and my ...


7

Your query is no faster with the index because SQL Server has determined that it would be more efficient to do a Clustered Index Scan, than use the IX_ActCost_ScenarioID that you have defined and perform a Key Lookup to retrieve the extra data needed. As you've only defined the index on ScenarioID, with no INCLUDE columns, each extra column you wish to ...


-1

You should look into several things: 1) Check the query plan, see if SQL Server is using the index. 2) How many records do you have in this table? If it's just a few million or even a few hundred million, then this query should be fast, if it's using the index. 3) Script out the index IX_ActCost_ScenarioID for CREATE and post its code here. See if ...


0

Please try: (edited 2014-12-18: replaced Left with INNER join): SELECT `pages_users`.`page_id` , COUNT(`pu2`.`page_id`) AS `count` FROM `pages_users` INNER JOIN `pages_users` AS `pu2` ON `pu2`.`user_id` = `pages_users`.`user_id` AND `pu2`.`page_id` = *PAGE_ID* WHERE `pages_users`.`page_id` != *PAGE_ID* GROUP BY ...


0

Let me do a small summary here: The Average Disk Queue Length is about read and write operations on your hard disk. The goal is to minimize these operations, you want the data to be read from memory since it's way faster and efficient. The recommended value for RAM on an SQL Server is minimum 50% of your databse size. And of course you should reserve at ...


3

Don't go to DTA. It can have severe performance impacts in production and can really do more harm than good (I learned that lesson the hard way when I started out as a DBA). The first step is to find out what exactly is causing your performance issues. Is it a CPU issue? Memory? Improper indexes? Also, how do you know you are experiencing a performance ...


0

Don't do it. First eliminate the obvious - it's not bad drive on the SAN, there isn't filegrowth happening, indexes aren't fragemented badly... etc. This is a last gasp effort from a desperate man... you're not that guy :) Edit (append): Fair enough comment: Elaborate :) As DBA I mistrust running processes on an already labouring server that are ...


1

am continuously getting the alerts for OS paging High. Memory is basically two types the physical random access memory (RAM) and virtual memory. A process has to be first mapped to Virtual memory and then to physical memory. All programs use RAM, but when there isn't enough RAM for the program you're trying to run, Windows temporarily moves information ...


0

Try to turn off Query Cache, which might cause extra lock.



Top 50 recent answers are included