Viewing 15 posts - 32,341 through 32,355 (of 59,099 total)
We've only had 2008 boxes at work for a couple of weeks now and haven't explored all of the new joys of SQL Server 2008... that includes filtered indexes. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 10:27 pm
SpringTownDBA (10/8/2011)
I like the isnull datediff. Very elegant.two questions:
Would that work in a filtered index?
"SARGable"?
Thanks.
I don't know if it would work in a filtered index because, oddly enough,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 10:16 pm
One other thing (because I see some good folks who GET the idea that "one test is worth a thousand expert opinions" and I want to make life easier for...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 10:13 pm
I certainly could be wrong (seen stranger stuff) but your tests may have a flaw, dmoutray... you're not clearing cache between tests and that may make it look like your...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 9:42 pm
The following code runs in about 1/5th of the time of the previous code. All I did was separate out the CTE's into invidual pieces of code that populated...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 6:58 pm
Almost forgot... you can get the code for the DelimitedSplit8K function from the "Resources" section of the following article...
http://www.sqlservercentral.com/articles/Tally+Table/72993/
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 4:41 pm
AndrewSQLDBA (10/7/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 4:39 pm
Iulian -207023 (10/8/2011)
Do you have at hand a sample code on how to create the CLR function for splitting a string into rows / fields? I am not...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 3:26 pm
Sapen (10/8/2011)
I have few databases in my production SQL Server. I am using SQL Server 2008 Standard Edition SP1 X64 bit. The size of all the databases together is 335GB....
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 3:22 pm
Don't include such a thing in a trigger... if the email system goes down, it'll take that part of SQL Server with it.
Instead, setup a job to interogate your logs...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 3:08 pm
I've not used SQL Server Express but I'm pretty sure it will all for the use of VARCHAR(MAX) which will give you capabilities up to 2 billion characters (1 billion...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 3:05 pm
Lexa (10/8/2011)
We're implementing a set of new features for our app and require dynamic creation of tables. My concern is that there will be lots of new data and...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 2:59 pm
You probably won't be able to do this through maintenance plans. That's good because I believe that most folks recommend not actually using maintenance plans for various reasons.
My recommendation...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 2:55 pm
Lynn Pettis (10/7/2011)
If the testers are not changing anything in the database, just running the application...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 2:47 pm
dmoutray (10/8/2011)
Outstanding! Now, this is the kind of insight that I was after! 🙂
There's more. There's a saying that's actually a paraphrase of a longer version written by...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 8, 2011 at 2:41 pm
Viewing 15 posts - 32,341 through 32,355 (of 59,099 total)