I think the key difference is if we are securing them, we know they are encrypted. If you use the same password everywhere can you guarantee that everybody else hashes them?
PeterStephenson
@PeterStephenson
Best posts made by PeterStephenson
Latest posts made by PeterStephenson
-
RE: Password storage system
-
RE: Password storage system
Basically a secure system to store all the different passwords we have (not for sites as such, but for our systems)
-
Password storage system
I was hoping that i'd be able to get a good reccomendation on a product here :D
I'm looking for a password storage system that stores all passwords encrypted in some description, is usuable by multiple users and preferably has some access control capability and is easy to backup.
I do realise that I want the world here ;)
Thanks in advance for any help
Peter
-
RE: Another spam WTF
@emurphy said:
*Important*
Please update your records on or before 48 hours, a failure to update your records will result in a temporal hold on your funds.Anyone know what a Temporal hold on your funds is?
It sounds cool though :P
-
Left outer join...
Came into work today and checked out some code written by a collegue, SQL query with a few joins... I think he missed a few PerMEaTaTIons...
Left outer join <snip>
LEFT OUTER JOIN <snip>
left outer join <snip>
Left Outer JOin <snip>
left OUter jOin <snip>
Left Outer Join <snip> -
RE: .NET Query issue
@Oscar L said:
@PeterStephenson said:
(trying to dodge a "if the server breaks run sp_recreateTheOtherSps" WTF here guys ;) )
Post the better solution when you find it, please. My servers are colocated, and it's a long drive just to slap a machine around. Seriously, check the nocount flag on that procedure and all the dependent procedures, too.
finally managed to reliably fix this by forcing the Sproc to recompile every time it is run (add with recompile after params b4 the "as")
Only thing i found that made any difference!
-
RE: .NET Query issue
ok we "solved" the issue ;)
After several midnight chanting sessions we believe we finally exorcised the demon ><
Seriously all we did is drop the SP, comment out soem fields, re create- it worked
we readded the fields 1 by 1 until they were all back and it still works fine! no changes to the ACTUAL code of the SP(and i had previously tried a drop and recreate)
We have no idea why this did it! Anyone?
-
RE: .NET Query issue
@Alex Papadimoulis said:
You need to be more specific. Short of that, some general guidelines:
- run a profiler trace to see the difference in queries
- see if the problem is parameter sniffing (google it)
- look at the connection string differences
Will try your suggestions next time im at the machine
Ok a few more details, sorry for being vague earlier I was rushing to get out the door ;)
I developed a stored procedure in Query Analyser, and was very careful to make sure it ran in an acceptable time (with the specific parameters being passed, sub second)I then call this stored procedure in my .net application- time out!
I dont think its a connection issue as there are other SP calls in the .net (same page, same connection)that run fine
Also I am definately using the same parameters as i have ran the actual query (exception handing will print the query to the browser if on a dev server)There are only 2 queries that time out. These queries have a parameter that specifies how it should look for a certain field, effectiely it can run one of 3 different (but very simple) queries into a table variable that is then used in the main part of the SP
This is a recurring issue, and it has in the past been solved by dropping, recreating and executing the SP again before using the web app, which leads me to believe its to do with being pushed out of the cache- but this makes no sense (to me at least) with the working in QA + not .NET app.... however this time, a drop + recreate hasnt fixed it.. and to be honest this "solution" is not acceptable ;) so im looking for a better way before I have to MTP this stuff ;)
(trying to dodge a "if the server breaks run sp_recreateTheOtherSps" WTF here guys ;) )
-
.NET Query issue
Anybody ever had a problem where a stored procedure will run in sub second in query analyser then time out in .NET at runtime?? (Exactly the same code)
and if so... anybody know how to fix it??