Viewing 15 posts - 4,216 through 4,230 (of 6,041 total)
Now on to data types.
Currency: should it be decimal, numeric, money, int?
Date/Time: datetime, offset, varchar?
Names and descriptions: varchar or nvarchar?
Unique Identifiers: int, guid, timestamp, rowid, identity, sequence? :rolleyes:
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 23, 2015 at 10:06 am
I can live with mixed naming conventions, or even no convention, so long as the name given for each column makes sense and is consistent within the scope of that...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 23, 2015 at 9:04 am
GoofyGuy (1/22/2015)
In many businesses and governmental organisations, IT is the only part of the organisation which can provide enterprise- wide knowledge of...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 22, 2015 at 9:21 am
I can see now this thread is going to get a lot of comment. This is one niche application where I'd suggest Hadoop and HiveSQL.
As far as doing this...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 22, 2015 at 8:02 am
Comparing the IT department to a utility company may not be accurate for most organizations, but at least it's not as demeaning as comparing IT to a sausage factory. ...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 22, 2015 at 7:20 am
ramana3327 (1/21/2015)
Need to change some columns datatype from nvarchar to varchar.Just need to drop the indexes that are on that column.
Do we get any problems from changing nvarchar to varchar
Yes,...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 21, 2015 at 3:22 pm
Brian J. Parker (1/21/2015)
Eric M Russell (1/21/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 21, 2015 at 1:33 pm
Steve Jones - SSC Editor (1/21/2015)
Eric M Russell (1/21/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 21, 2015 at 10:58 am
I don't take offense if I'm called after work, so long as it's regarding something that's broke in production. The way I see it, if I done by due dilligence,...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 21, 2015 at 8:16 am
ProductID, ProductId, and product_id are all respectable options, so long as it's done consistently.
However, I would take issue with ID by itself, on every table. Anytime I see that,...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 21, 2015 at 7:16 am
The data model of a database is like the foundation of skyscraper. It defines the scope, constraints, and scalability of the database. Get it wrong, and your SQL and data...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 20, 2015 at 2:00 pm
alanspeckman (1/20/2015)
I need a quick way of showing...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 20, 2015 at 1:42 pm
Sean Lange (1/20/2015)
Eric M Russell (1/20/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 20, 2015 at 9:49 am
Steve Jones - SSC Editor (1/20/2015)
david.gugg (1/20/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 20, 2015 at 9:39 am
I've used product_id. I like typing code in all lowercase, both keywords and identifiers, which is ok so long as underscores are also used for clarity. Also, I don't have...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 20, 2015 at 9:33 am
Viewing 15 posts - 4,216 through 4,230 (of 6,041 total)