Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««1234»»

Today's Humor.. Expand / Collapse
Author
Message
Posted Thursday, July 31, 2014 9:10 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, December 18, 2014 10:51 AM
Points: 1,510, Visits: 8,470
Grant Fritchey (7/31/2014)
Sarah Wagner (7/31/2014)
I hired in to a software company and sad to say we were one of those vendors. Gladly we are not anymore as I rewrote all of our recommendations to clients documentation. A little education goes a long way.


Thank you!

One down 678,342 to go...


Grant, I think you left out a few.




Alvin Ramard
Memphis PASS Chapter

All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.
Post #1598325
Posted Thursday, July 31, 2014 9:32 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 2:39 PM
Points: 18,064, Visits: 16,108
Sarah Wagner (7/31/2014)
I hired in to a software company and sad to say we were one of those vendors. Gladly we are not anymore as I rewrote all of our recommendations to clients documentation. A little education goes a long way.



You're taking some of our fun away

Seriously though, I think the education only works if it is coming from within the organization. I'm sure most of us have had similar experiences trying to educate vendors from outside their walls. They want none of it.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Post #1598334
Posted Thursday, July 31, 2014 9:35 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 1:35 PM
Points: 4,618, Visits: 4,076
SQLRNNR (7/31/2014)
Sarah Wagner (7/31/2014)
I hired in to a software company and sad to say we were one of those vendors. Gladly we are not anymore as I rewrote all of our recommendations to clients documentation. A little education goes a long way.



You're taking some of our fun away

Seriously though, I think the education only works if it is coming from within the organization. I'm sure most of us have had similar experiences trying to educate vendors from outside their walls. They want none of it.

That's because they already know everything. It's their product. They don't want a bunch of "users" of their product telling them how to make it work better.



Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions
Post #1598335
Posted Thursday, July 31, 2014 12:32 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 10:20 AM
Points: 261, Visits: 469
I have to deal with a vendor who has the following advice in their Tuning and Scaling guide:
Setting Recovery Model to Simple has the lowest amount of overhead over Full and Bulk-logged, which is crucial to the performance requirements needed for the (vendor redacted) databases.


I debated about asking them for any whitepapers, or test results to back this assertion up. But apparently I am not allowed to talk to our vendors, anyway.
Post #1598437
Posted Thursday, July 31, 2014 12:50 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 1:33 PM
Points: 2,533, Visits: 7,116
GilaMonster (7/31/2014)
Alvin Ramard (7/30/2014)

WAIT!!!! What kind of database MUST be repaired regularly????



MS Access ones.

That actually is correct advice, for an MS Access database (as in Access tables) used by multiple people. They generally need a 'compact and repair' on a very regular basis. Only MS Access though


At least up to and including Access 2000, this was the standard practice. The risk was that the database would grow passed the 2Gb limit resulting in an unusable heap of ......
Historical note: The operation created a new database, copied the data from the original one, purged it and renamed the new one.
Somehow it looks like the old MS Access is still the impression some have of any Microsoft Database products.
Post #1598443
Posted Thursday, July 31, 2014 3:02 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 1:58 PM
Points: 3,113, Visits: 11,542
As a general rule, vendors have very little knowledge of DBA best practices, so they just toss out some misinterpreted stuff that some junior developer found on some web site which may or may not apply to the current version of SQL Server. I have seen so many bad practices advocated by vendors that I expect it.

The last vendor I had to deal with had an application that required the use of a specific SA password to connect to the database on a specifically named (non-default) instance. Having an application use a hard coded SA password is really bad security, but it's just some medical application, so no big deal.

At least they didn't tell me to set the databases to simple recovery or not do backups.

Another vendor application (for a building security system) required the use of a blank SA password so I guess it can always get worse.

Post #1598503
Posted Thursday, July 31, 2014 3:11 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, December 18, 2014 10:51 AM
Points: 1,510, Visits: 8,470

SCARY!!!!!!




Alvin Ramard
Memphis PASS Chapter

All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.
Post #1598509
Posted Thursday, July 31, 2014 3:16 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 1:33 PM
Points: 2,533, Visits: 7,116
Michael Valentine Jones (7/31/2014)
As a general rule, vendors have very little knowledge of DBA best practices, so they just toss out some misinterpreted stuff that some junior developer found on some web site which may or may not apply to the current version of SQL Server. I have seen so many bad practices advocated by vendors that I expect it.

The last vendor I had to deal with had an application that required the use of a specific SA password to connect to the database on a specifically named (non-default) instance. Having an application use a hard coded SA password is really bad security, but it's just some medical application, so no big deal.

At least they didn't tell me to set the databases to simple recovery or not do backups.

Another vendor application (for a building security system) required the use of a blank SA password so I guess it can always get worse.



In my experience, this kind of applications have databases dating 15-20 years back when the structure was entirely different, sa was then the equivalent of being a member of sysadmin.
Medical or medieval, those do not pass any decent compliance audit.
Post #1598511
Posted Thursday, July 31, 2014 3:40 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 12:24 PM
Points: 1,391, Visits: 645
SQLRNNR (7/31/2014)
Sarah Wagner (7/31/2014)
I hired in to a software company and sad to say we were one of those vendors. Gladly we are not anymore as I rewrote all of our recommendations to clients documentation. A little education goes a long way.



You're taking some of our fun away

Seriously though, I think the education only works if it is coming from within the organization. I'm sure most of us have had similar experiences trying to educate vendors from outside their walls. They want none of it.


Abosolutely 100% easier from inside and still only about 50% success rate...
Post #1598518
Posted Thursday, July 31, 2014 4:13 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 9:22 AM
Points: 40,632, Visits: 37,094
Michael Valentine Jones (7/31/2014)

The last vendor I had to deal with had an application that required the use of a specific SA password to connect to the database on a specifically named (non-default) instance. Having an application use a hard coded SA password is really bad security, but it's just some medical application, so no big deal.

...

Another vendor application (for a building security system) required the use of a blank SA password so I guess it can always get worse.


That's when you rename the sa login to something which sounds useless, disable it and create a new login called 'sa' with just the permissions you want it to have.
Want sa? Sure, just gimme a couple minutes...



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1598525
« Prev Topic | Next Topic »

Add to briefcase «««1234»»

Permissions Expand / Collapse