Viewing 15 posts - 35,341 through 35,355 (of 59,102 total)
chaudharyabhijit (1/17/2011)
Thank you for the suggestion. I would love to do what you asked me but unfortunately these tables are from a really obsolete software and there is no...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 7:31 am
keymoo (1/18/2011)
Jeff Moden
Just to follow up on that... a good ol' fashioned cross-tab can make life real easy and "prettier".
SELECT Symbol,
SUM(CASE...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2011 at 7:29 am
Bryan McGuire (1/17/2011)
I have been given a task to create a pivot table from a table of data supplied via a 3rd party.
The table is structured like this...
CREATE TABLE [dbo].[EntityRiskGroupKeyItem](
[Name]...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 11:21 pm
sqlbaby2 (1/17/2011)
I already found the solutions ...thanks
In that case, would you mind sharing them? Two way street here... 😉
And... you should still read the article I pointed you to....
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 11:06 pm
omd (1/17/2011)
I have a table that has a specific column holding dates & also a time e.g. '1/14/2011 16:25:32 PM'.
All I am trying to do is use a basic delete...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 11:02 pm
tacy.highland (1/17/2011)
There are two tables involved. One is the BookingActivity table which will be updated. The Update statement will also look at the Clients table to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 11:00 pm
JayK (1/17/2011)
Found this article which looks good to me:http://www.sqlteam.com/article/implementing-a-dynamic-where-clause
Using COALESCE certainly looks a lot neater.....
You need to be a wee bit careful with COALESCE because it will change datatypes based...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 10:49 pm
CELKO (1/17/2011)
Each module of code should have one entry and one exit point. Each...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 10:37 pm
sqlchanakya (1/17/2011)
So can we take a conclusion that we will have page splits at non clustered level even its a sequentially ordered?
No. Not necessarily but you certainly could if...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 10:23 pm
sqlbaby2 (1/17/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 10:08 pm
imohamed (12/3/2010)
Eg: Table "T1" has an integer field "A" which is either 0...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 10:05 pm
Just a couple of notes I'd like to add... first, we've just seen what happens when date and time are stored in separate columns for things like this. And...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 9:57 pm
The DM you're using will not help you find page splits. sys.dm_db_index_physical_stats will show you the affect that page and extent splits have had in the form of fragmentation...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 9:46 pm
You bet. Thank you for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 9:41 pm
picant (1/17/2011)
Tanks that's something I was looking for. Looks quite complex. It'll take me some time to understand how it works. Thanks again.
Nope... not complex at all. The first...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2011 at 9:39 pm
Viewing 15 posts - 35,341 through 35,355 (of 59,102 total)