« first day (3268 days earlier)      last day (1593 days later) » 

5:14 AM
Morning
 
 
1 hour later…
6:21 AM
Morning
 
7:14 AM
Good Morning
 
7:35 AM
Morning
 
The question was specifically about performance, i.e. whether adding LIMIT 1 would make a WHERE column = value query any faster if column already has a UNIQUE constraint defined on it. The OP is well aware that the query would definitely return no more than one row anyway and LIMIT 1 is unnecessary in terms of results. The question is whether LIMIT 1 would help in that scenario in terms of performance. — Andriy M 8 mins ago
Seems like a useless answer at this point, but maybe the answerer genuinely misunderstood the question. Hopefully they'll respond in any way.
 
@AndriyM I often fail to understand his answers. Maybe he tries to answer the question in his first sentence "You do not need to use LIMIT 1 (to improve performance)"
 
7:53 AM
@TomV-TeamMonica Possible, though not very likely. There's no mentioning of performance in the entire post (in all of its three sentences).
What's also annoying is that the answer had been happily sitting at 0 but then it was bumped to the top page by Community and someone decided it was the reason to upvote it.
 
 
1 hour later…
9:23 AM
@TomV-TeamMonica ...and <<<him>>> too.
 
9:35 AM
user image
4
 
 
6 hours later…
3:23 PM
Anyone around?
 
3:34 PM
i r
 
Hi. I'm using mySql with C#.
Whenever I enter some Hebrew chars via :

```
INSERT INTO `Fueling`.`FuelingTransactions`
(`PhoneNumber`,
`CarNumber`,
`StationCity`,
`StationName`,
`Cost`,
`Liters`,
`VendorId`,
`PointsEarned`,
`PointName`,
`DateCreated`)
VALUES
('{transaction.PhoneNumber}',
'{transaction.CarNumber}',
'{transaction.StationCity}',
'{transaction.StationName}',
{transaction.Cost},
{transaction.Liters},
{transaction.FuelingVendorId},
{transaction.PointsEarned},
'{transaction.PointName}',
Am I missing something in the settings of the table ?
 
@RoyiNamir This is a collation issue - I'd suggest posting on the main site for more help
 
Also, not a mysql person but you might need nvarchar data type instead of varchar to support Hebrew. .NET strings natively handle unicode so as George suggests, pop a question onto the site
 
3:49 PM
theres no nvarchar
 
Oh well then, yet another thing I don't know about mysql
 
National char in mysql i think?
 
I have a feeling I know the answer, but if I have a stored SA password that lets me into the db in MS SQL 2008, is there a way to know what that SA password is?
 
@JohnP No - there's only a way to know if your stored pass is correct versus the one on the server
Oh
you mean stored in SSMS history?
[NATIONAL] VARCHAR(M) [CHARACTER SET charset_name] [COLLATE collation_name]
According to the documentayshun
 
@JohnP nope
 
3:52 PM
@billinkc utf8 is the equivalent on NCHAR and NVARCHAR, in MySQL.
 
@Marian Yeah, that's what I figured. From everything I've seen so far, there's no way to tell if the programmers were smart enough not to use the SA password for things. Guess I'll have to wade through the code to find the query logins. Was hoping to avoid that.
I mean, I have access to the database, but I have an update I need to do that requires the SA password.
I hate supporting external company purchases 3 years after anyone involved has left/moved on. :|
 
@JohnP it's stored as hashed text fortunately :)
@JohnP SA or any sysadmin user?
@JohnP get whoisactive to table (article by Kendra Little methinks) and run it in a job every minute for a few days..
and you'll see if users really use SA or some different user
 
@Marian hmm... just has USERID: with sa prefilled, but it's an editable field. We don't have the sa account login on the SQL01 machine, but we do on 02.
This (luckily) is on a cloned set of systems, working on a db upgrade for a client on a live set of servers.
 
uhm.. try creating a sysadmin sql user and see if you can use that
 
@Marian to quote Apollo 13 - "You sir, are a steely eyed missile man"
 
@Johnakahot2use Hey, I like ADA. And SNOBOL.
 
@JohnP you can migrate any user.. including the SA (use something like usp_logins by sql tiger) but it won't show the password :)
@JohnP I liked Pascal.. 25 years ago
 
@Marian The daemon that uploads information is going to go through an upgrade. The related tables need an upgrade, and the tool uses the SA login. I didn't think about adding a second sysadmin user.
@Marian I still like Pascal. I don't use it, but affection never dies. :p
 
yeah.. it's a pita especially when devs "need" SA!
I always refuse their request
and then they come back.. we need sysadmin!
boo
 
@JohnP Pascal, Lisp, Prolog, Forth ;)
 
4:16 PM
@Marian This is a never updated/upgraded product we bought from a 3rd party. They fired all the people related to it when they found them mining bitcoins using company resources. Enter me, 2 years after the fact as the "maintainer".
 
4:30 PM
So there was a team of them previously, and they couldn't maintain this product without mining themselves some bitcoins as a side endeavour... And now enter a new solo maintainer, no team, no joy of bitcoins... That's no fun at all.
 
@Marian Just use a login trigger :)
 
@George.Palacios or that :)
@AndriyM quite the fun they had
 
4:46 PM
CREATE  PROCEDURE MineBitcoins(...)
AS ...  ;
GO
 -- and profit ;)
 
Yes, GO is unavoidable
In their case it was anyway
 
@Marian Since this is a clone server, I created a recovery acct and reset SA password. We'll see if that bollixes anything on the upgrade sequence later.
Sheesh.
Meeting quote of the day - "Yeah, I asked for resources, I should have asked for competent resources!"
2
End of year production go/nogo meetings are always fun...
 
5:05 PM
Also, if you have an import process that handles a few hundred files a day, you'd think you'd have something that would age/archive/delete said files, no?
No.
 
5:21 PM
@Marian So...in the upload daemon code we found the SA password. Yay sloppy devs.
 
6:16 PM
Always fun to change password / stop a service/db and see what breaks, who complains ;)
 
 
4 hours later…
9:57 PM
Voted to close since op said in (now deleted) answer op was connected to the wrong server — Tom V - Team Monica 23 secs ago
 

« first day (3268 days earlier)      last day (1593 days later) »