Viewing 15 posts - 13,036 through 13,050 (of 15,379 total)
I too get the point about cardinality issues but the example really is more of a logic flaw than anything else. The example you provided has some serious issues that...
February 8, 2012 at 7:43 am
bharatgi (2/8/2012)
hi,how would i get the field values to automatically show the display format rather than the sql standard format?
Fields don't display stuff they simply store data. In this case...
February 8, 2012 at 7:28 am
CELKO (2/7/2012)
And we never, never use the UPDATE ..FROM.. syntax; it is not only proprietary, it does not work right.
I have used this plenty over the years and have never...
February 8, 2012 at 7:22 am
Uripedes Pants (6/14/2011)
Kansas City and Texarkana immediately come to mind as spanning States.
Actually the cities do NOT cross state lines. The metropolitan areas cross state lines but they have separate...
February 7, 2012 at 3:03 pm
And here is another one that Lowell wrote (same caveats about production ;-)):
CREATE PROCEDURE sp_UGLYSEARCH
/*
--Purpose: to search every string column in a databasefor a specific word
--returns sql statement as...
February 7, 2012 at 2:58 pm
Here is an old cursor based solution I wrote for just this sort of thing. Keep in mind this is NOT fast. Do NOT run this (or the previous one)...
February 7, 2012 at 2:57 pm
Hi and welcome to SSC. There seems to be something missing here. First Chrissy asked you to post ddl (create table statements) and sample data (insert statements) along with desired...
February 7, 2012 at 2:54 pm
bharatgi (2/7/2012)
based on your code i tried the following:
update [table1]set [ddate2] = convert(datetime,CAST([ddate] as datetime),112)
but it now outputs '2011-09-01 00:00:00'
If your new destination is actually a datetime, which i...
February 7, 2012 at 10:13 am
That's because you have data somewhere in there that can't be converted to a datetime.
February 7, 2012 at 10:01 am
Shaun Dayaram (2/7/2012)
For my own sanity, I need the following explained to me. It was an issue we picked up in a PROD environment.,
eg.
CREATE PROCEDURE dbo.my_proc
...
February 7, 2012 at 9:56 am
Not a lot of detail to go on here but your replace statement did exactly what you told it to do.
declare @Tag_Data varchar(200) = '2''10"'
select @Tag_Data = REPLACE(REPLACE(REPLACE(REPLACE(REPLACE(@TAG_DATA,'"','\quote\'),'@','\at\'),'^','\carat\'),'|','\pipe\'),'=','\equal\') + '^'
select...
February 7, 2012 at 9:46 am
I would recommend not using the local copy and always use the online copy anyway. There are frequent changes and updates to the documentation and your local copy will not...
February 7, 2012 at 9:40 am
What is the datatype of your new column? I suspect it is another nvarchar(255). Please use the proper datatypes. You have datetime information put it in a datetime column.
Look at...
February 7, 2012 at 9:33 am
Viewing 15 posts - 13,036 through 13,050 (of 15,379 total)