Viewing 15 posts - 4,111 through 4,125 (of 6,041 total)
I would consider SSEE for a 10 user line of business application that doesn't require GB of reference data or ad-hoc queries. However, it would have to be a business...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 27, 2015 at 7:41 am
Of course containing "date" values in VarChar columns is a bad idea from the start, and once it's done, it's no small change to undo, because there are applications and...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 26, 2015 at 9:19 am
sstanek 27058 (2/26/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 26, 2015 at 8:57 am
PHYData DBA (2/25/2015)
Eric M Russell (2/25/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 25, 2015 at 9:58 am
If I offended anyone here with my analogy, of a table having no primary key, to that of a feral child having no name, then I'm sorry. I think that...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 25, 2015 at 9:28 am
Great leaders are almost always great simplifiers, who can cut through argument, debate and doubt to offer a solution everybody can understand.
– Colin Powell
I believe this quote is particularly...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 25, 2015 at 9:14 am
ZZartin (2/19/2015)
Eric M Russell (2/19/2015)
In the original post, it was stated that table contains no primary key. Regardless of what the table contains (datatypes or internal value structure), all tables...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 25, 2015 at 8:34 am
MMartin1 (2/24/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 24, 2015 at 2:56 pm
FYI:
If you're struggling with users entering "date" values into a varchar column in required format, the following check constraint enforces insertion of values as YYYYMMDD.
create table foo
(
...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 24, 2015 at 6:16 am
It works for me when I first cast the string as date and then wrap a convert function around that.
PRINT convert(char(8),cast('Jul 11 2014' as date),112);
20140711
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 24, 2015 at 6:11 am
If no explicit constraint name is specified, then SQL Server will assign a random one at the time of object creation. It's best supply a constraint name so it's consistent...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 23, 2015 at 3:08 pm
Kutang Pan (2/23/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 23, 2015 at 9:06 am
mw112009 (2/23/2015)
Below is a SQL statement that shows what columns belong to a certain view. My next question is how can I get a third column that...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 23, 2015 at 8:26 am
PHYData DBA (2/23/2015)
bantrim (2/22/2015)
Eric M Russell (2/22/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 23, 2015 at 8:18 am
I don't let my young kids go off exploring entirely on their own; not the neighborhood or the internet. But I do find ways to gradually and thoughtfully introduce them...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
February 23, 2015 at 8:09 am
Viewing 15 posts - 4,111 through 4,125 (of 6,041 total)