Viewing 15 posts - 33,106 through 33,120 (of 59,102 total)
btull89 (7/27/2011)
Thanks for all of the feedback! It was helpful.
I'll add to all of this. Use thoughtful comments and section headers. IT makes life a whole lot easier...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 27, 2011 at 2:30 pm
Ninja's_RGR'us (7/27/2011)
http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1I just use the basic cpu, reads, writes, duration columns.
Those events are nice to use in their own rights :
Performance:Showplan XML Statistics Profile
SP:StmtCompleted
SQL:StmtCompleted
I also throw in ROWCOUNT... it...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 27, 2011 at 2:28 pm
ekant_alone (7/27/2011)
I am working on a huge XML file. I am trying to update a XML file. I am saving the broken parts into a variable of nvarchar(max) type Datatype....
--Jeff Moden
Change is inevitable... Change for the better is not.
July 27, 2011 at 2:23 pm
Ian86Myers (7/26/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2011 at 10:49 pm
chadphillips807 (7/26/2011)
So I have been tasked with creating a table where the Primary Key is a 10 digit number and is randomly generated with each insert. NEWID() and NEWSEQUENTIALID() are...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2011 at 10:43 pm
I guess I'm out of tricks, then. I can't troubleshoot any further from here. My apologies.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2011 at 10:37 pm
@SQLFRNDZ (7/26/2011)
CREATE FUNCTION dbo.Split(@String varchar(8000), @Delimiter char(1))returns @temptable TABLE (items varchar(8000))
as ...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2011 at 10:16 pm
This is a simple "pivot" problem... except I don't care for using PIVOT because it's slower than classic "Cross Tab" code and I don't care for its structure. 😉
Let's peel...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2011 at 9:39 pm
My recommendation would be to study Oracle on your own a bit before making such a move. There's a huge paradigm shift between PL/SQL and T-SQL. At least...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2011 at 8:49 pm
DATEDIFF doesn't work the way most people think. It works on the borders of days (ie: midnight). For example, even though the following dates are only 3 milliseconds...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2011 at 8:36 pm
You bet, Marcelo. Thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2011 at 9:39 am
Use methods similar to those found in the following article...
http://www.sqlservercentral.com/articles/Crosstab/65048/
Instead of using SUM or COUNT on the DATETME and character based columns, use MAX, instead.
If you'd like a coded answer...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2011 at 6:43 pm
Chelo (7/25/2011)
I'm working with a database that contains a table with IDs to create Relationships and Reciprocal records in the database. The table with the IDs for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2011 at 6:30 pm
If you insist on an estimation, there's a section in Books Online called "estimating table size" in the index. Personally, I think that's a huge PITA although you could...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2011 at 5:53 pm
john.arnott (7/25/2011)
Question:
What's the answer?Answer choices:
It depends.
It doesn't depend.
What's the question?
I think there's a tpyo in here so I can only guess.
There...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2011 at 5:15 pm
Viewing 15 posts - 33,106 through 33,120 (of 59,102 total)