Viewing 15 posts - 16 through 30 (of 85 total)
Hi Angela,
I have seen many posts of this kind on SSC so far. Usual suggestion is to solve the problem at the presentation level, not at the database level. I...
April 20, 2005 at 1:06 am
Hi subban,
clustered indexes are usually said to be usefull when selecting and ORDERed recordset or when filtering on the index prefix (leading portion of columns). What do you expect from...
March 29, 2005 at 11:38 pm
Or, you can re-use what has already been posted here:
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=99869
Regards,
Goce.
March 29, 2005 at 12:14 am
Hi Dilip,
I think that you should see the execution plan for the SP. Looking at the SQL statement, it seems to me that SQL Server will use nested loop, but...
March 28, 2005 at 12:40 am
Hi there,
about the benefits mentioned, I don't know how M$$QL treats this issue, but on ORACLE you can save some space if you order the columns as Frank wrote. For...
March 1, 2005 at 1:27 am
Hi Frank,
At the end of the "Truncating the Transaction Log" article of BOL it is explicitly stated: "Truncation does not reduce the size of a physical log file, it reduces...
February 17, 2005 at 1:23 am
Hi Joan,
Try this one:
SELECT TOP 1 DATALENGTH(ldtext), * FROM longtescription WHERE ldtext IS NOT NULL ORDER BY DATALENGTH(ldtext) DESC
The first column in the result set will contain the actual...
February 16, 2005 at 1:07 am
Hi Matt,
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=4&messageid=152361</a?
I think it is a similar problem.
Regards,
Goce.
February 9, 2005 at 2:01 am
Hi there,
I don't consider myself as one of the Farrell's true gurus :-), but I still cannot accept the fact that M$$SQL's query execution engine has an undiscovered bug that...
February 3, 2005 at 1:28 am
Hi,
the usual rule of thumb is to first solve the problem that is causing the most of the problems. So, start the SQL Monitor and observe the execution of SQL...
February 3, 2005 at 1:09 am
Hi,
write the table definition like this:
DECLARE @InterestIncome Table ( Period_Amount FLOAT, Regular_Calendar_Key INT, Scenario_Key INT, Hierarchy_Key INT, Service_Type_Key INT, Category_Key INT, Concept_Key INT, Event_Key INT, Fiscal_Calendar_Key INT, PRIMARY KEY ( ...
February 2, 2005 at 1:05 am
Hi Felipe,
I came up with this procedure.
create procedure families_report as create table #tmp( id int not null, rank int not null, ...
January 28, 2005 at 3:05 am
Hi Felipe,
If you limit the result set to a fixed number of columns (according to examples, this will be 3), I think that there is a solution to the problem....
January 27, 2005 at 2:58 am
Hi all,
I still think that you cannot (or a least should not) avoid altering those SPs, because a data type change is not an issue that can pass without major...
January 27, 2005 at 12:45 am
Viewing 15 posts - 16 through 30 (of 85 total)