October 17, 2016 at 7:50 am
Dirk Gently, I look forward to see how its different to the short lived BBC one from a few years ago.
Loved the two books.
So hands up who loves the idea of a production db being called Test_Autos on a server that was the test server...
Yes a production server details were also sent out...
But hey why bother porting over the data? Why don't we just point the app at the test server and continue to use test_autos...
:w00t:
Rodders...
October 17, 2016 at 7:54 am
rodjkidd (10/17/2016)
So hands up who loves the idea of a production db being called Test_Autos on a server that was the test server...Yes a production server details were also sent out...
But hey why bother porting over the data? Why don't we just point the app at the test server and continue to use test_autos...
:w00t:
Rodders...
I love the idea of ANY production database being called Test.
My second favorite is Error.
:hehe:
October 17, 2016 at 8:03 am
Phil Parkin (10/17/2016)
Spammers have upped their game recently. Some are starting to mention 'SQL' or 'database' in the subject line, the ****ers. What's the latest on migration to new forum software?
I was whacking spam all weekend and I know I'm not the only one that can. It still amazes me that single-URL spam continues to be the most frequent type of them all.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2016 at 8:04 am
Brandie Tarvin (10/17/2016)
rodjkidd (10/17/2016)
So hands up who loves the idea of a production db being called Test_Autos on a server that was the test server...Yes a production server details were also sent out...
But hey why bother porting over the data? Why don't we just point the app at the test server and continue to use test_autos...
:w00t:
Rodders...
I love the idea of ANY production database being called Test.
My second favorite is Error.
:hehe:
How about adding _new to the end of any database name, to designate the latest version? One of my favourites.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
October 17, 2016 at 8:06 am
Phil Parkin (10/17/2016)
Spammers have upped their game recently. Some are starting to mention 'SQL' or 'database' in the subject line, the ****ers. What's the latest on migration to new forum software?
Integration still going on. Some minor issues with jquery versions and integrating the new software into the site. There are some fairly deep embeds, but the work proceeds fairly smoothly.
Still weeks out.
October 17, 2016 at 8:10 am
Phil Parkin (10/17/2016)
Brandie Tarvin (10/17/2016)
rodjkidd (10/17/2016)
So hands up who loves the idea of a production db being called Test_Autos on a server that was the test server...Yes a production server details were also sent out...
But hey why bother porting over the data? Why don't we just point the app at the test server and continue to use test_autos...
:w00t:
Rodders...
I love the idea of ANY production database being called Test.
My second favorite is Error.
:hehe:
How about adding _new to the end of any database name, to designate the latest version? One of my favourites.
I don't know about this. If the production database is named Test_Autos, then are you sure you'll be able to keep it straight from the test databases on production? Oh yeah...the test database will be named Test_Autos_Test.
The real question comes in how to keep them straight between the production and test databases on production versus the test database on test. Unless, of course, there's a production database on test - that would be even worse.
October 17, 2016 at 8:15 am
Steve Jones - SSC Editor (10/17/2016)
Phil Parkin (10/17/2016)
Spammers have upped their game recently. Some are starting to mention 'SQL' or 'database' in the subject line, the ****ers. What's the latest on migration to new forum software?Integration still going on. Some minor issues with jquery versions and integrating the new software into the site. There are some fairly deep embeds, but the work proceeds fairly smoothly.
Still weeks out.
Thanks for the update, Steve.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
October 17, 2016 at 8:32 am
Brandie Tarvin (10/17/2016)
So who else is going to be watching Dirk Gently's Holistic Detective Agency when it comes out?
Past my bedtime. I would like to watch it sometime. Read the first book and liked it read the second not so much.
October 17, 2016 at 8:33 am
Ed Wagner (10/17/2016)
Phil Parkin (10/17/2016)
Brandie Tarvin (10/17/2016)
rodjkidd (10/17/2016)
So hands up who loves the idea of a production db being called Test_Autos on a server that was the test server...Yes a production server details were also sent out...
But hey why bother porting over the data? Why don't we just point the app at the test server and continue to use test_autos...
:w00t:
Rodders...
I love the idea of ANY production database being called Test.
My second favorite is Error.
:hehe:
How about adding _new to the end of any database name, to designate the latest version? One of my favourites.
I don't know about this. If the production database is named Test_Autos, then are you sure you'll be able to keep it straight from the test databases on production? Oh yeah...the test database will be named Test_Autos_Test.
The real question comes in how to keep them straight between the production and test databases on production versus the test database on test. Unless, of course, there's a production database on test - that would be even worse.
Okay, fine. If you're going to be that way about it, I'm just going to start naming all my production databases Dev_ or _Dev. That way EVERYONE will know the difference!
:w00t:
October 17, 2016 at 8:40 am
What does it say about a company when it takes over a week to get a "new" computer up and configured to replace an existing computer?
Just an individuals workstation, only a couple special applications. E-mail still isn't working, so the person in question has had to fall back on their old PC to be able to check work e-mails...
Not me, nor anyone where I work...
October 17, 2016 at 8:41 am
I just complained directly to the manager here and said are you seriously telling me you named a prod db Test_
And asked me to fix an issue on Prod directly first... (OK you called it the test server... When Prod has nothing on it - I looked later)
To the dev here I simply said I can't say what I want to say...
Everyone seemed to think I was panicking about deleting prod data, no... Just thinking a pity it wasn't a drop DB statement. Then they might learn.
I was amazed really. And very, very angry at their blasé approach.
No obviously you would the test db this;
No_Really_This_Is_The_Test_Autos
🙂
(well until it become the live data)
Rodders...
October 17, 2016 at 8:42 am
Brandie Tarvin (10/17/2016)
Ed Wagner (10/17/2016)
Phil Parkin (10/17/2016)
Brandie Tarvin (10/17/2016)
rodjkidd (10/17/2016)
So hands up who loves the idea of a production db being called Test_Autos on a server that was the test server...Yes a production server details were also sent out...
But hey why bother porting over the data? Why don't we just point the app at the test server and continue to use test_autos...
:w00t:
Rodders...
I love the idea of ANY production database being called Test.
My second favorite is Error.
:hehe:
How about adding _new to the end of any database name, to designate the latest version? One of my favourites.
I don't know about this. If the production database is named Test_Autos, then are you sure you'll be able to keep it straight from the test databases on production? Oh yeah...the test database will be named Test_Autos_Test.
The real question comes in how to keep them straight between the production and test databases on production versus the test database on test. Unless, of course, there's a production database on test - that would be even worse.
Okay, fine. If you're going to be that way about it, I'm just going to start naming all my production databases Dev_ or _Dev. That way EVERYONE will know the difference!
:w00t:
Bah, lightweight...
Your server should be named Prod_Development_Dev for a production server and Dev_Production_Prod for development.
QA should be QA_QA_QA
And all your databases should be named "data base for application"
:hehe:
October 17, 2016 at 9:53 am
jasona.work (10/17/2016)
What does it say about a company when it takes over a week to get a "new" computer up and configured to replace an existing computer?Just an individuals workstation, only a couple special applications. E-mail still isn't working, so the person in question has had to fall back on their old PC to be able to check work e-mails...
Not me, nor anyone where I work...
The technician must have had help filling out their resume to get the job?
Hope they never touch a production server. :w00t:
I can only imagine the frustration.
October 17, 2016 at 11:21 am
Greg Edwards-268690 (10/17/2016)
jasona.work (10/17/2016)
What does it say about a company when it takes over a week to get a "new" computer up and configured to replace an existing computer?Just an individuals workstation, only a couple special applications. E-mail still isn't working, so the person in question has had to fall back on their old PC to be able to check work e-mails...
Not me, nor anyone where I work...
The technician must have had help filling out their resume to get the job?
Hope they never touch a production server. :w00t:
I can only imagine the frustration.
Yeah, the company in question stands up every workstation "from scratch," every time. No two PCs are the same model, there's no standardized OS deployment, nothing. It's not entirely the tech's fault, as much as a managerial obtuseness...
October 17, 2016 at 11:28 am
jasona.work (10/17/2016)
obtuseness...
There is a word I do not come across very often. Have to remember to use it on occasion as it does describe various situations.
🙂
Viewing 15 posts - 56,281 through 56,295 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply