JesseBizInt (3/22/2016)

---

Thanks for the reply. It's a shame stuff can't be more standardized, at least, from the managers perspective of what each level of DBA should know. ...

I agree with your thoughts here....

Thing is, all organisations can have completely different business requirements, so setting a basic "what you should know by X" is difficult for anyone to do as it's such a...

JesseBizInt (3/22/2016)

---

I call myself an accidental dev because I ended up falling into a business intelligence role mainly through passion and not through any in-depth technical knowledge. Yes, I...

Beatrix Kiddo (3/22/2016)

---

tindog (3/22/2016)

I can't say I have ever met someone my age who has said "You know what I'd *love* to do? Work with databases." From what I've seen,...

I'm 23, and "fell into" the SQL world by pure accident 6 years ago. I've got a lot of "techy" friends who I've watched go through University and develop unrealistic...

What happens when these people actually get the job? Is it not horrendously embarrassing for everyone involved when they turn up and can't perform simple tasks? Are they not concerned...

pietlinden (3/20/2016)

---

Jeff,

Just wondering what you would say to an applicant that admitted up front that he may be underqualified, but asked you to help him figure out what he needed...

Right click the group (under 'Row Groups'), on 'General' add 'Group Expressions' and add one for each field, selecting the necessary field from your dataset each time.

Then just add the...

Check out some of the stored procedure's in MSDB, e.g 'msdb.dbo.sp_get_sqlagent_properties', this should point you in the right direction.

Are all 3 agents running?

Try scripting out and recreating the subscription.

I would first try reinitialising it, perhaps scripting it out and recreating it - something's got all out of whack somewhere down the line. Is there anything relevant in the...

Are you using a UNC path?

sys.user (2/25/2016)

---

Luis Cazares (2/25/2016)

---

Dodgier according to who?

If your problem is that you have too many columns in the GROUP BY clause, you could use a different approach.

I used a CTE...

sys.user (2/25/2016)

---

tindog (2/25/2016)

---

What do you mean by 'looks dodgier'? Does it not return the correct data?

What's the issue with the first query in your recent post? Also, the second query...