Viewing 15 posts - 26,116 through 26,130 (of 59,099 total)
In that case, my answer would be to examine a similar system and make a determination from that. That is, of course, if that similar system has some form...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 4:49 pm
PearlJammer1 (8/22/2013)
It looks like the ones that had the high count have had either small increment growth settings or...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 4:28 pm
CGSJohnson (8/23/2013)
Is the dearth of responses an indication that we are all just working on mundane projects?! Or is it too early?!
Nope... I can't speak for others but it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 4:20 pm
I actually can't talk about some of the projects that I've worked on recently or am working on because of NDAs and personal ethics concerning perceived company secrets whether they're...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 4:08 pm
Shifting gears a bit, no matter which way you solve this problem, the server and the I/O system are going to suffer quite a bit. Even the "pipe" is...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 2:50 pm
Both tables are going to be scanned at least once. I haven't tried it for efficiency but I thought I'd let some of the inbuilt tools in SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 2:35 pm
Hold the phone... you have a [font="Arial Black"]1TB[/font] database for a [font="Arial Black"]NEW [/font]application?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 1:45 pm
To summarize a CROSS APPLY, it's a correlated subquery much like you might find in a subquery within a SELECT list except that it's capable of returning more than one...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 1:42 pm
Someone could explain this better than I but, at a 100,000ft view, when you put all of these queries in a single transaction, the data isn't actually written as you...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 1:36 pm
Smash125 (8/24/2013)
SELECT ContactID,
AVG(TotalDue) AS [Avergare Total Due]
FROM Sales.SalesOrderHeader
GROUP BY ContactID
ORDER BY 1 ASC
what i want to i want prefix dollar symbol in the [Avergare...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 1:26 pm
Open the Explorer window in SSMS by pressing the {f8} key. Then right click on the server/instance and select "Properties". In the properties window, select "Connection" and see...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 1:03 pm
L' Eomot Inversé (8/24/2013)
I have one quibble: terminology; even an old relic like me knows that "best bower" and "small bower" have been superseded by "starboard bower"...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 12:00 pm
LordHz (3/14/2013)
Not putting that back in the original table (mines not employee), I'm just maintaining the mapping in your hierarchy table. My thought is to make your stored procedure more...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 11:57 am
Hi Jamie,
Despite the low number of stars on this article, I think the concept of this article is actually very good but the methods used in the code bit you....
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2013 at 11:05 am
Craig-315134 (8/23/2013)
This is a part of what I'm talking about. Too many people think that the only way in or out of a database is through the UI...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 23, 2013 at 4:09 pm
Viewing 15 posts - 26,116 through 26,130 (of 59,099 total)