August 13, 2015 at 7:07 am
Brandie Tarvin (8/13/2015)
Luis Cazares (8/12/2015)
jasona.work (8/12/2015)
So, my laptop offered me the Win10 upgrade. I figured I'd sign up for it (laptop was recently reloaded to Win7 Pro) and worst case I can dump it...So far, I'm neither excited nor disappointed, considering I've only been using it now for about 30 minutes...
Need to get the rest of my normal stuff on it (MS Office, SSMS, etc) tomorrow...
I updated my laptop from 8.1 to 10 and it was definitively an improvement. I'm not sure if I would say the same about updating from 7.
Yeah, I'm holding off for another couple of weeks. Here's one of the reasons why: Windows 10 Privacy Concerns[/url]
And here's another article from Slate.com.
I gave up on my privacy some years ago. 🙁
That said, I'm not sure the privacy concerns are much greater with W10 compared to 8/8.1
August 13, 2015 at 7:24 am
TomThomson (8/12/2015)
Sean Lange (8/12/2015)
They took the old RPG code and used a tool to convert it to java which is what the front end is "written" in today. All of the primary and foreign keys are logical only.Moving from rpg to java by machine conversion sounds to me like a neat recipe for performance deterioration and unexpected problems, so maybe it's even sicker than before.
They release hundreds of patches weekly. :w00t:
select * from sys.foreign_keys
(0 row(s) affected)
select * from sys.key_constraints
(0 row(s) affected)
select count(*) from sys.tables
(3816 row(s) affected)
What are you using for an RDBMS? SQL Server would say 1 row(s) affected (for the single row containing the count). :hehe:
Obvioulsy a little copy/paste on my end. 😉
Then add to it a case sensitive collation and this has the smell of a very long and painful process to transition our business to this.
Like you (I think it's like you, anyway) I believe that the default collation for just about any database should be case insensitive (and accent sensitive). But there are some pretty big guns who take a different view (Hugo, for example). So we probably shouldn't blame Jan Baan back in 1978 (before there was any commercially available RDBMS) for following some earlier big guns and deciding his application's data would be case-sensitive.[/quote]
Yes the case sensitivity is going to take me some time to get used to. Honestly I can't imagine why it is good approach that tables named Customer and customer are two different tables. The whole things lends itself to errors and massive confusion. Of course the case sensitivity thing is rather silly in that system. Every table name and every column name are exactly 6 UPPER case letters.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
August 13, 2015 at 7:42 am
...Of course the case sensitivity thing is rather silly in that system. Every table name and every column name are exactly 6 UPPER case letters.
That's why they are all 6 upper case letters, for the case sensitivity.
I have a 3rd party system that is in a Binary collation so case sensitive and completely annoying because it doesn't need to be.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
August 13, 2015 at 7:47 am
Jack Corbett (8/13/2015)
...Of course the case sensitivity thing is rather silly in that system. Every table name and every column name are exactly 6 UPPER case letters.
That's why they are all 6 upper case letters, for the case sensitivity.
I have a 3rd party system that is in a Binary collation so case sensitive and completely annoying because it doesn't need to be.
Yeah this one too is a Binary collation. This just makes me want to take out my eyeballs and peel them. :w00t:
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
August 13, 2015 at 7:49 am
Lynn Pettis (8/12/2015)
< Rant >I don't know about others but I am really tired of people thinking that using vulgarity is appropriate in a professional environment and this is a professional environment and it bothers me more and more as I get older. Enough of the WT*.
< /Rant>
Lynn, regardless of how you feel about it, after Monday and Tuesday, we're still gonna have WTF. 😀
Sorry. Just couldn't resist. 😎
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
August 13, 2015 at 8:09 am
Alvin Ramard (8/13/2015)
Lynn Pettis (8/12/2015)
< Rant >I don't know about others but I am really tired of people thinking that using vulgarity is appropriate in a professional environment and this is a professional environment and it bothers me more and more as I get older. Enough of the WT*.
< /Rant>
Lynn, regardless of how you feel about it, after Monday and Tuesday, we're still gonna have WTF. 😀
Sorry. Just couldn't resist. 😎
I'll wait for the SS. :hehe:
August 13, 2015 at 8:16 am
Sean Lange (8/13/2015)
Every table name and every column name are exactly 6 UPPER case letters.
I'm working with one of those. Fortunately it's not case sensitive, but the tables are named as if they were.
Seriously, the limit for a table name is 128 characters iirc, why does the table have to be named TSKGRPMBRS?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 13, 2015 at 8:22 am
GilaMonster (8/13/2015)
Sean Lange (8/13/2015)
Every table name and every column name are exactly 6 UPPER case letters.I'm working with one of those. Fortunately it's not case sensitive, but the tables are named as if they were.
Seriously, the limit for a table name is 128 characters iirc, why does the table have to be named TSKGRPMBRS?
I was going to say, because DOS only allows 8.3 naming, then I counted the characters...
August 13, 2015 at 8:26 am
jasona.work (8/13/2015)
GilaMonster (8/13/2015)
Sean Lange (8/13/2015)
Every table name and every column name are exactly 6 UPPER case letters.I'm working with one of those. Fortunately it's not case sensitive, but the tables are named as if they were.
Seriously, the limit for a table name is 128 characters iirc, why does the table have to be named TSKGRPMBRS?
I was going to say, because DOS only allows 8.3 naming, then I counted the characters...
Someone might believe that having that kind of names will keep the data secure as no one will ever know what does the table store.
August 13, 2015 at 8:26 am
GilaMonster (8/13/2015)
Sean Lange (8/13/2015)
Every table name and every column name are exactly 6 UPPER case letters.I'm working with one of those. Fortunately it's not case sensitive, but the tables are named as if they were.
Seriously, the limit for a table name is 128 characters iirc, why does the table have to be named TSKGRPMBRS?
Have you added the schema, the database, and the server name to that string to check the length? Maybe someone's thinking 4 dot notation means they have to keep the table names short because the schema / db / server names are so long?
August 13, 2015 at 8:32 am
Brandie Tarvin (8/13/2015)
GilaMonster (8/13/2015)
Sean Lange (8/13/2015)
Every table name and every column name are exactly 6 UPPER case letters.I'm working with one of those. Fortunately it's not case sensitive, but the tables are named as if they were.
Seriously, the limit for a table name is 128 characters iirc, why does the table have to be named TSKGRPMBRS?
Have you added the schema, the database, and the server name to that string to check the length? Maybe someone's thinking 4 dot notation means they have to keep the table names short because the schema / db / server names are so long?
Database name - 7 characters. Schema is dbo
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 13, 2015 at 8:36 am
GilaMonster (8/13/2015)
Brandie Tarvin (8/13/2015)
GilaMonster (8/13/2015)
Sean Lange (8/13/2015)
Every table name and every column name are exactly 6 UPPER case letters.I'm working with one of those. Fortunately it's not case sensitive, but the tables are named as if they were.
Seriously, the limit for a table name is 128 characters iirc, why does the table have to be named TSKGRPMBRS?
Have you added the schema, the database, and the server name to that string to check the length? Maybe someone's thinking 4 dot notation means they have to keep the table names short because the schema / db / server names are so long?
Database name - 7 characters. Schema is dbo
Well there's no accounting for people who hate vowels.
August 13, 2015 at 8:37 am
Sean Lange (8/13/2015)
Every table name and every column name are exactly 6 UPPER case letters.
I feel your pain. Baan's tables were named using a multi-part naming convention that made it a bit silly to try and remember. Example:
t$ttdsls040400
t$ttdsls041400
t$ = Prefix necessary for all tables and columns.
t = Prefix that does nothing except add another "t" to the table name.
td = Package the table is a part of. TD, logically, means Triton Distribution.
sls = Module the table is a part of. SLS means Sales.
040 = Which table it is. Naturally, 040 is Sales Orders and 041 is Sales Orders Lines. Not Sales Order Lines, but Sales Orders Lines.
400 = The company number. You can have multiple companies set up in one database, each with their own set of tables. The company number is the suffix for everything.
The columns where not quite as bad, but almost:
t$orno
t$pono
t$txta
t$txtb
t$ = Prefix necessary for all tables and columns.
next 4 = Field name. Clearly, orno = Order Number, pono = Position Number, txta = pointer to the text table for the this text entry. Note I didn't say foreign key, because where were none.
The text table was: t$tttxt001400.
Obviously, the package "tt" is Triton Text, the module "txt" is Text and the table was 001. There was no 002.
And yes, the whole thing was case sensitive in both object names and values.
See why it gave me nightmares?
August 13, 2015 at 8:38 am
Jack Corbett (8/13/2015)
...Of course the case sensitivity thing is rather silly in that system. Every table name and every column name are exactly 6 UPPER case letters.
That's why they are all 6 upper case letters, for the case sensitivity.
I have a 3rd party system that is in a Binary collation so case sensitive and completely annoying because it doesn't need to be.
PeopleSoft uses the Latin1_BIN collation. I must be the weird one in this group, I prefer case sensitive collations.
August 13, 2015 at 8:54 am
I hate case sensitive collations. The vast majority of the time in working with data, I don't care that "acme" and "ACME" are different characters on disk. They're the same for most practical purposes.
I'm sure there are domains where case sensitivity matters, but I've not really had any in business.
Viewing 15 posts - 50,146 through 50,160 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply