August 4, 2017 at 9:04 am
You'd think he'd know more since it appears he has been working with SQL Server for at least 9 years. Should have picked up something hanging around here that long.
August 4, 2017 at 9:25 am
Lynn Pettis - Friday, August 4, 2017 9:04 AMYou'd think he'd know more since it appears he has been working with SQL Server for at least 9 years. Should have picked up something hanging around here that long.
Considering, earlier, a user that's been here for over 4 years asked how to pass variables/parameters to an SP, I'd call that wishful thinking. ^_^
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
August 4, 2017 at 9:33 am
Thom A - Friday, August 4, 2017 9:25 AMLynn Pettis - Friday, August 4, 2017 9:04 AMYou'd think he'd know more since it appears he has been working with SQL Server for at least 9 years. Should have picked up something hanging around here that long.Considering, earlier, a user that's been here for over 4 years asked how to pass variables/parameters to an SP, I'd call that wishful thinking. ^_^
The dates my stored procedure needs are in a table that's unrelated to my stored procedure.....
August 4, 2017 at 9:34 am
Thom A - Friday, August 4, 2017 9:25 AMLynn Pettis - Friday, August 4, 2017 9:04 AMYou'd think he'd know more since it appears he has been working with SQL Server for at least 9 years. Should have picked up something hanging around here that long.Considering, earlier, a user that's been here for over 4 years asked how to pass variables/parameters to an SP, I'd call that wishful thinking. ^_^
And then there's the Canine from Cymru... not that I've seen much of that one recently
Thomas Rushton
blog: https://thelonedba.wordpress.com
August 4, 2017 at 10:23 am
ThomasRushton - Friday, August 4, 2017 9:34 AMThom A - Friday, August 4, 2017 9:25 AMLynn Pettis - Friday, August 4, 2017 9:04 AMYou'd think he'd know more since it appears he has been working with SQL Server for at least 9 years. Should have picked up something hanging around here that long.Considering, earlier, a user that's been here for over 4 years asked how to pass variables/parameters to an SP, I'd call that wishful thinking. ^_^
And then there's the Canine from Cymru... not that I've seen much of that one recently
And that jasona.work guy, you'd think he'd know how to use a "partition by" in a LAG statement by now...
:hehe:
August 4, 2017 at 10:57 am
Brandie Tarvin - Friday, August 4, 2017 4:35 AM...My whole day is going to be like this now. I just know it.
Hope it's gotten better since then. if it makes you feel any better (probably won't) there was a period of about a year and a half where I was storing backups on a Drobo NAS device that would flake out a couple times a month and completely corrupt one of my backup directories. Fortunately that NAS was decommissioned and replaced. Hopefully your problem is a one time thing. 🙂
August 4, 2017 at 11:02 am
Chris Harshman - Friday, August 4, 2017 10:57 AMBrandie Tarvin - Friday, August 4, 2017 4:35 AM...My whole day is going to be like this now. I just know it.Hope it's gotten better since then. if it makes you feel any better (probably won't) there was a period of about a year and a half where I was storing backups on a Drobo NAS device that would flake out a couple times a month and completely corrupt one of my backup directories. Fortunately that NAS was decommissioned and replaced. Hopefully your problem is a one time thing. 🙂
Not quite. The saga continues through several reassignments of the ticket...
August 4, 2017 at 11:08 am
ThomasRushton - Friday, August 4, 2017 9:34 AMThom A - Friday, August 4, 2017 9:25 AMLynn Pettis - Friday, August 4, 2017 9:04 AMYou'd think he'd know more since it appears he has been working with SQL Server for at least 9 years. Should have picked up something hanging around here that long.Considering, earlier, a user that's been here for over 4 years asked how to pass variables/parameters to an SP, I'd call that wishful thinking. ^_^
And then there's the Canine from Cymru... not that I've seen much of that one recently
Heh - When I read Lynn's comment, I thought of Silver Spoons as well. He/she/they/etc has been conspicuously silent lately.
August 4, 2017 at 11:09 am
ZZartin - Friday, August 4, 2017 9:33 AMThom A - Friday, August 4, 2017 9:25 AMLynn Pettis - Friday, August 4, 2017 9:04 AMYou'd think he'd know more since it appears he has been working with SQL Server for at least 9 years. Should have picked up something hanging around here that long.Considering, earlier, a user that's been here for over 4 years asked how to pass variables/parameters to an SP, I'd call that wishful thinking. ^_^
The dates my stored procedure needs are in a table that's unrelated to my stored procedure.....
Yeah, but the table is in a database that's on a server I don't have access to, so how do I pass them?
Edit: Oh yeah, I didn't mention that the server is on a different domain. 😉
August 4, 2017 at 12:06 pm
OOOOOOHHHHH, this is so brilliant. To keep our NAS share from growing, someone made the decision to make it Read Only. <bah dum-dum>
Then they created a new NAS share to replace the old one. Only no one ever thought to tell us this. In the meantime, the tech assigned the ticket was insisting the share was Read / Write and even showed me a screen shot of one security group having Full Control permissions to prove it. Because a permissions screenshot absolutely proves whether or not the share is writeable.
<headdesk>
Well, at least I have the new share name now and can access it with our backup jobs. The way it was going, I thought we'd have to wait until next week to get this resolved.
August 4, 2017 at 12:17 pm
Brandie Tarvin - Friday, August 4, 2017 12:06 PMOOOOOOHHHHH, this is so brilliant. To keep our NAS share from growing, someone made the decision to make it Read Only. <bah dum-dum>Then they created a new NAS share to replace the old one. Only no one ever thought to tell us this. In the meantime, the tech assigned the ticket was insisting the share was Read / Write and even showed me a screen shot of one security group having Full Control permissions to prove it. Because a permissions screenshot absolutely proves whether or not the share is writeable.
<headdesk>
Well, at least I have the new share name now and can access it with our backup jobs. The way it was going, I thought we'd have to wait until next week to get this resolved.
Ugh, I've had to (not recently, thankfully,) had to deal with situations where people would claim having "Full Control" on a share equated to "Full Control" on the filesystem...
Or vice-versa...
Kind of makes one wish MS would simplify share permissions to "no access / access" and then the file-system permissions control how much someone can do in the share...
Which, you can do by just ignoring the "read only" share permission entirely.
August 4, 2017 at 12:32 pm
On the upside... My boss sometimes likes to ask for the impossible. Not that he phrases it that way. Usually he's like "Can we do XYZ instead?" So he did today and I said I'd do some research, then started thinking this task might truly be impossible.
Then instead of using Google, I decided really quick to run a sideways kind of test against the issue. And what do you know, it worked! So the day is ending on a positive note at least. The impossible task is possible. Just ... finicky.
August 4, 2017 at 12:52 pm
Brandie Tarvin - Tuesday, August 1, 2017 10:02 AMYou know, I didn't think about disabling the users... I should consider that for the next time.
Nah, that's too hard. Do it the easy way:
USE [DatabaseToWorkIn];
GO
ALTER DATABASE [DatabaseToWorkIn] SET SINGLE_USER WITH ROLLBACK IMMEDIATE; -- kicks everyone else out but you
GO
do your stuff....
ALTER DATABASE [Database ToWorkIn] SET MULTI_USER; -- let the losers back in
GO
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
August 7, 2017 at 4:19 am
WayneS - Friday, August 4, 2017 12:52 PMBrandie Tarvin - Tuesday, August 1, 2017 10:02 AMYou know, I didn't think about disabling the users... I should consider that for the next time.Nah, that's too hard. Do it the easy way:
USE [DatabaseToWorkIn];
GO
ALTER DATABASE [DatabaseToWorkIn] SET SINGLE_USER WITH ROLLBACK IMMEDIATE; -- kicks everyone else out but you
GO
do your stuff....
ALTER DATABASE [Database ToWorkIn] SET MULTI_USER; -- let the losers back in
GO
Not that simple. This is multi-step jobs that is taking forever (once a month) because of this. Plus there are auto-connect app accounts that log into the system, which reconnect faster than you'd think. All it takes is one user or one auto-connect account to re-establish connection in the millisecond before the job kicks off its next process and the job is hung due to Single User.
I've been down that path. It wasn't pretty and took us most of the day to figure out why the job wasn't completing.
August 7, 2017 at 9:59 am
THIS looks interesting. Too bad the internet is forever.
Viewing 15 posts - 59,566 through 59,580 (of 66,738 total)
You must be logged in to reply to this topic. Login to reply