Viewing 15 posts - 31,321 through 31,335 (of 59,101 total)
Good idea, Paul. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 27, 2012 at 6:54 am
Thanks, Chrissy. I always like to know these types of things so I can help better. I appreciate the time you spent on the reply.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 27, 2012 at 6:53 am
mithubhudolia (1/27/2012)
please reply me of my question only .Thanks
Sure. Answer to your question... just modify code in the following article to work with days instead of months.
http://www.sqlservercentral.com/articles/Crosstab/65048/
--Jeff Moden
Change is inevitable... Change for the better is not.
January 27, 2012 at 6:49 am
er.sivaganesh (1/27/2012)
can u plz help me
Yes. Post an example of the actual data you want split and tell us how you want it split.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 27, 2012 at 6:45 am
SQL Kiwi (1/26/2012)
Jeff Moden (1/26/2012)
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2012 at 11:59 pm
Thanks, Paul...
The deprecation that I remember was based on using table names instead of alias names for column callout in the SELECT list. Like this...
SELECT TableName.SomeColumnName
...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2012 at 11:47 pm
Forgot to ask... Jared is correct on this. This type of formatting is usually relegated to the frontend code and I'm as curious as he. Why did you...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2012 at 8:16 pm
Chrissy321 (1/26/2012)
Thanks! I wasn't aware of STUFF
You bet. We could have just as easily used SUBSTRING(expression,2,10) instead of STUFF for this but glad I could introduce you to a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2012 at 8:15 pm
Lynn Pettis (1/25/2012)
Jeff Moden (1/25/2012)
This should do it, Chrissy...
DECLARE @SomeExampleDate DATETIME;SELECT @SomeExampleDate = '01/01/2012';
SELECT STUFF(REPLACE('/'+CONVERT(CHAR(10),@SomeExampleDate,101),'/0','/'),1,1,'')
Don't you just hate it when a simple solution is staring you in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2012 at 8:10 pm
IIRC, the proxy account will only help folks when it comes to running a job. It won't help them with creating or editing a job.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2012 at 8:04 pm
I'll second all of that, Elliott. I'll also add that I prefer that most things are in the "dbo" schema.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2012 at 6:13 pm
Steve Jones - SSC Editor (1/25/2012)
True, you can use views of synonyms. That might work, although performance wouldn't be great.For dev/test, it's probably fine.
I've not experienced any noticiable slowdowns with...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2012 at 8:49 am
opc.three (1/26/2012)
Jeff Moden (1/25/2012)
babatmanpub (1/25/2012)
Just for those who would like to change $pshome : you can do it here :with regedit
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PSConfigurationProviders\Microsoft.PowerShell]
"ApplicationBase"="c:\\Windows\\System32\\WindowsPowerShell\\v1.0"
Nicely done.
Shifting gears a bit (and no implications...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2012 at 8:40 am
No... I don't believe there is.
However, if you use BULK INSERT instead of OPENROWSET, you can route all of the errors to an error file and import that, as well.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 10:25 pm
Sean Lange (1/25/2012)
raisleger (1/25/2012)
Any additional ideas?
CardType ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2012 at 10:16 pm
Viewing 15 posts - 31,321 through 31,335 (of 59,101 total)