March 15, 2015 at 4:11 pm
Steve Jones - SSC Editor (3/14/2015)
It was great to meet you, Gianluca, and sorry we didn't get to talk more. I'll have to get down to Italy at some point.And yes, you are a giant in a few ways. 2m and quite intelligent.
We're waiting for you! We've already had international speakers at our SQLSaturdays and attendees had no issues at all with English sessions. It was a big concern for us (Italian people are not exactly renowned for their fluency in foreign languages...) but we got pleasantly surprised by our attendees and their feedback.
I think that at some point we'll have to switch to 100% English sessions, otherwise we will never be able to attract attendees and speakers from foreign countries. It has be said that attracting attendees from our own country has been challenging enough that nobody wants to scare them away with English sessions now. It's hard to find a balance and it probably comes down to what your primary goal is.
In all honesty, I can't think of a dumber thing than a room full of Italian attendees desperately trying to follow along with an Italian presenter speaking (poor) English. 😀
Regarding me being a giant, well... thanks :blush:
-- Gianluca Sartori
March 15, 2015 at 4:19 pm
rodjkidd (3/14/2015)
Gianluca,
Sadly as most people discovered the Excel is great if you fly in to London City, not great for any other London airport! Next time let me know you plans, if I'm in East Anglia still, Stansted isn't that bad a drive for me.
Cheers,
Rodders...
That would be great, thank you!
Maybe choosing less crazy travel schedules will help just as much 🙂
However I'm under the impression that the next SQLBits won't be in London. I heard some of the organizers say that London got the event crazily big and they're thinking of sizing it a bit smaller for the next few years and move it north. Did I misunderstand?
-- Gianluca Sartori
March 15, 2015 at 4:23 pm
In other news, I submitted 3 sessions for the PASS Summit. It's the first time for me, but nobody promised to be gentle. 🙂
I'll tell you how the rejection letter looks like.
-- Gianluca Sartori
March 15, 2015 at 4:53 pm
Well it has been the tradition to move it around the country. Been to London three times in the 14. And different parts of London each time. So no I wouldn expect it to be in London next year.
Size? Well after the previous London one they halved the number of attendees. Not sure they can do that again. SQL Bits has got too well known now. My guess would be around 1200 mark maybe a few more. But then they have to find venues big enough. The problem is the keynote, apperently.
But wherever it ends up, if it's mainland UK then arranging pickups can be done from airports 🙂
Rodders
March 16, 2015 at 5:03 am
spaghettidba (3/15/2015)
Steve Jones - SSC Editor (3/14/2015)
It was great to meet you, Gianluca, and sorry we didn't get to talk more. I'll have to get down to Italy at some point.And yes, you are a giant in a few ways. 2m and quite intelligent.
We're waiting for you! We've already had international speakers at our SQLSaturdays and attendees had no issues at all with English sessions. It was a big concern for us (Italian people are not exactly renowned for their fluency in foreign languages...) but we got pleasantly surprised by our attendees and their feedback.
I think that at some point we'll have to switch to 100% English sessions, otherwise we will never be able to attract attendees and speakers from foreign countries. It has be said that attracting attendees from our own country has been challenging enough that nobody wants to scare them away with English sessions now. It's hard to find a balance and it probably comes down to what your primary goal is.
In all honesty, I can't think of a dumber thing than a room full of Italian attendees desperately trying to follow along with an Italian presenter speaking (poor) English. 😀
Regarding me being a giant, well... thanks :blush:
Have you considered asking translaters to sit in the classes and translate for the Italian-speaking portion of the class?
March 16, 2015 at 5:30 am
So I'm reading my Database Weekly this morning and find a link to Brent Ozar's SQL Rally commentary[/url]. Funny, I thinks as I read. I didn't know DBAs were dinosaurs.
Then something he said struck me in an odd way. AHHA! I says to myself. There's the opening that women are more likely to take then men.
Maybe I'm wrong, but I always see men in the workplace only wanting to solve the problems they find interesting themselves rather than positioning themselves to solve the problems the company needs solving. What do you think? (I've linked my blog with my thoughts on the issue.)
March 16, 2015 at 5:48 am
Brandie Tarvin (3/16/2015)
So I'm reading my Database Weekly this morning and find a link to Brent Ozar's SQL Rally commentary[/url]. Funny, I thinks as I read. I didn't know DBAs were dinosaurs.Then something he said struck me in an odd way. AHHA! I says to myself. There's the opening that women are more likely to take then men.
Maybe I'm wrong, but I always see men in the workplace only wanting to solve the problems they find interesting themselves rather than positioning themselves to solve the problems the company needs solving. What do you think? (I've linked my blog with my thoughts on the issue.)
Very true.
I love solving SSIS performance problems, so most of the time at projects I take a look at that, even if performance is acceptable.
"I don't care if it runs in 20 seconds, I can make it run in 10 seconds!"
(and the package runs only once a day...)
One of my many, many flaws 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 16, 2015 at 6:09 am
Brandie Tarvin (3/16/2015)
So I'm reading my Database Weekly this morning and find a link to Brent Ozar's SQL Rally commentary[/url]. Funny, I thinks as I read. I didn't know DBAs were dinosaurs.Then something he said struck me in an odd way. AHHA! I says to myself. There's the opening that women are more likely to take then men.
Maybe I'm wrong, but I always see men in the workplace only wanting to solve the problems they find interesting themselves rather than positioning themselves to solve the problems the company needs solving. What do you think? (I've linked my blog with my thoughts on the issue.)
Yes, I enjoy solving problems I find interesting, but I think that's probably an altruism (or close to it) for nearly everyone. Usually, the ones that I find interesting are the complicated ones that the company needs to be solved. I will certainly work on the ones that need solving whether they're interesting or not, but I enjoy the interesting ones simply because they're interesting.
I can only speak for myself, not for all men. I don't know about the differences in how men and women solve problems.
March 16, 2015 at 6:13 am
Ed Wagner (3/16/2015)
Brandie Tarvin (3/16/2015)
So I'm reading my Database Weekly this morning and find a link to Brent Ozar's SQL Rally commentary[/url]. Funny, I thinks as I read. I didn't know DBAs were dinosaurs.Then something he said struck me in an odd way. AHHA! I says to myself. There's the opening that women are more likely to take then men.
Maybe I'm wrong, but I always see men in the workplace only wanting to solve the problems they find interesting themselves rather than positioning themselves to solve the problems the company needs solving. What do you think? (I've linked my blog with my thoughts on the issue.)
Yes, I enjoy solving problems I find interesting, but I think that's probably an altruism (or close to it) for nearly everyone. Usually, the ones that I find interesting are the complicated ones that the company needs to be solved. I will certainly work on the ones that need solving whether they're interesting or not, but I enjoy the interesting ones simply because they're interesting.
I can only speak for myself, not for all men. I don't know about the differences in how men and women solve problems.
Well, I guess my question is... Do you just assume you know what those problems are? Do you have to be told? Or do you proactively ask?
March 16, 2015 at 6:27 am
Koen Verbeeck (3/16/2015)
Brandie Tarvin (3/16/2015)
So I'm reading my Database Weekly this morning and find a link to Brent Ozar's SQL Rally commentary[/url]. Funny, I thinks as I read. I didn't know DBAs were dinosaurs.Then something he said struck me in an odd way. AHHA! I says to myself. There's the opening that women are more likely to take then men.
Maybe I'm wrong, but I always see men in the workplace only wanting to solve the problems they find interesting themselves rather than positioning themselves to solve the problems the company needs solving. What do you think? (I've linked my blog with my thoughts on the issue.)
Very true.
I love solving SSIS performance problems, so most of the time at projects I take a look at that, even if performance is acceptable.
"I don't care if it runs in 20 seconds, I can make it run in 10 seconds!"
(and the package runs only once a day...)
One of my many, many flaws 😀
+1 and for me that includes any query I look at. I think it is in the blood.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
March 16, 2015 at 6:34 am
Brandie Tarvin (3/16/2015)
Ed Wagner (3/16/2015)
Brandie Tarvin (3/16/2015)
So I'm reading my Database Weekly this morning and find a link to Brent Ozar's SQL Rally commentary[/url]. Funny, I thinks as I read. I didn't know DBAs were dinosaurs.Then something he said struck me in an odd way. AHHA! I says to myself. There's the opening that women are more likely to take then men.
Maybe I'm wrong, but I always see men in the workplace only wanting to solve the problems they find interesting themselves rather than positioning themselves to solve the problems the company needs solving. What do you think? (I've linked my blog with my thoughts on the issue.)
Yes, I enjoy solving problems I find interesting, but I think that's probably an altruism (or close to it) for nearly everyone. Usually, the ones that I find interesting are the complicated ones that the company needs to be solved. I will certainly work on the ones that need solving whether they're interesting or not, but I enjoy the interesting ones simply because they're interesting.
I can only speak for myself, not for all men. I don't know about the differences in how men and women solve problems.
Well, I guess my question is... Do you just assume you know what those problems are? Do you have to be told? Or do you proactively ask?
In the area of performance, I go looking for them. Do I think I know what all of them are? Absolutely not, and I certainly hope I never become so arrogant to think I can find them all. I find some on my own and some are brought to me by others.
I also ask others and have mixed results. Some people don't ever want to admit to having any problems, while others appreciate help and want to learn from the tuning experience. I find the same thing to be true for design.
How about you?
March 16, 2015 at 7:09 am
Ed Wagner (3/16/2015)
Brandie Tarvin (3/16/2015)
Ed Wagner (3/16/2015)
Brandie Tarvin (3/16/2015)
So I'm reading my Database Weekly this morning and find a link to Brent Ozar's SQL Rally commentary[/url]. Funny, I thinks as I read. I didn't know DBAs were dinosaurs.Then something he said struck me in an odd way. AHHA! I says to myself. There's the opening that women are more likely to take then men.
Maybe I'm wrong, but I always see men in the workplace only wanting to solve the problems they find interesting themselves rather than positioning themselves to solve the problems the company needs solving. What do you think? (I've linked my blog with my thoughts on the issue.)
Yes, I enjoy solving problems I find interesting, but I think that's probably an altruism (or close to it) for nearly everyone. Usually, the ones that I find interesting are the complicated ones that the company needs to be solved. I will certainly work on the ones that need solving whether they're interesting or not, but I enjoy the interesting ones simply because they're interesting.
I can only speak for myself, not for all men. I don't know about the differences in how men and women solve problems.
Well, I guess my question is... Do you just assume you know what those problems are? Do you have to be told? Or do you proactively ask?
In the area of performance, I go looking for them. Do I think I know what all of them are? Absolutely not, and I certainly hope I never become so arrogant to think I can find them all. I find some on my own and some are brought to me by others.
I also ask others and have mixed results. Some people don't ever want to admit to having any problems, while others appreciate help and want to learn from the tuning experience. I find the same thing to be true for design.
How about you?
Well, see. I'm not just talking about performance here. I'm talking about everything.
Actually, I do go to the boss at least once every two months and say "What's at the top of our agenda? What do you need help with or what should I be working on, because if you don't say otherwise, I'm tackling X project this week."
And the project could be anything from moving jobs from one server to another, to creating a new backup / recovery plan, to hitting all those low priority data fix projects that have been on our list. Or it could be calling up corporate to schedule a conference call about our server move, or the domain controller reboot project, etc.
So I am geniunely curious. How do all of my fellow Threadzians decide what is a priority? I'm not talking "Servers are down, building's on fire" kind of issues. I'm talking day to day operations. To paraphrase what I got from Brent's post "What is the boss's number one priority today?".
Do you assume you know? Do you have to be told? Do you proactively ask? (And yes, I do, but not as often as I should, probably).
March 16, 2015 at 7:51 am
Brandie Tarvin (3/16/2015)
Ed Wagner (3/16/2015)
Brandie Tarvin (3/16/2015)
Ed Wagner (3/16/2015)
Brandie Tarvin (3/16/2015)
So I'm reading my Database Weekly this morning and find a link to Brent Ozar's SQL Rally commentary[/url]. Funny, I thinks as I read. I didn't know DBAs were dinosaurs.Then something he said struck me in an odd way. AHHA! I says to myself. There's the opening that women are more likely to take then men.
Maybe I'm wrong, but I always see men in the workplace only wanting to solve the problems they find interesting themselves rather than positioning themselves to solve the problems the company needs solving. What do you think? (I've linked my blog with my thoughts on the issue.)
Yes, I enjoy solving problems I find interesting, but I think that's probably an altruism (or close to it) for nearly everyone. Usually, the ones that I find interesting are the complicated ones that the company needs to be solved. I will certainly work on the ones that need solving whether they're interesting or not, but I enjoy the interesting ones simply because they're interesting.
I can only speak for myself, not for all men. I don't know about the differences in how men and women solve problems.
Well, I guess my question is... Do you just assume you know what those problems are? Do you have to be told? Or do you proactively ask?
In the area of performance, I go looking for them. Do I think I know what all of them are? Absolutely not, and I certainly hope I never become so arrogant to think I can find them all. I find some on my own and some are brought to me by others.
I also ask others and have mixed results. Some people don't ever want to admit to having any problems, while others appreciate help and want to learn from the tuning experience. I find the same thing to be true for design.
How about you?
Well, see. I'm not just talking about performance here. I'm talking about everything.
Actually, I do go to the boss at least once every two months and say "What's at the top of our agenda? What do you need help with or what should I be working on, because if you don't say otherwise, I'm tackling X project this week."
And the project could be anything from moving jobs from one server to another, to creating a new backup / recovery plan, to hitting all those low priority data fix projects that have been on our list. Or it could be calling up corporate to schedule a conference call about our server move, or the domain controller reboot project, etc.
So I am geniunely curious. How do all of my fellow Threadzians decide what is a priority? I'm not talking "Servers are down, building's on fire" kind of issues. I'm talking day to day operations. To paraphrase what I got from Brent's post "What is the boss's number one priority today?".
Do you assume you know? Do you have to be told? Do you proactively ask? (And yes, I do, but not as often as I should, probably).
I discuss it with my boss on a regular basis. Or I did until this job. This job there are issues that spring up frequently that I'm supposed to drop everything for. I let my boss tell me when those arise. Otherwise I try to work on the projects that I've been told are important. I've never worked someplace with a large enough team and a stable enough environment that I had the leisure to pick and choose what to do.
When I have to prioritize it is
1) Keep things running
2) Ensure customers consider it "usable"
3) new development
4) Speed improvements with largest effect for customer experience or resolving potential bottlenecks first
5) Going through the above 'cause I must have missed something
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
March 17, 2015 at 1:06 pm
Can someone help with a crystal ball or interrogation system for this thread?
http://www.sqlservercentral.com/Forums/Topic1668185-391-1.aspx
March 17, 2015 at 1:18 pm
Brandie Tarvin (3/16/2015)
Ed Wagner (3/16/2015)
Brandie Tarvin (3/16/2015)
Ed Wagner (3/16/2015)
Brandie Tarvin (3/16/2015)
So I'm reading my Database Weekly this morning and find a link to Brent Ozar's SQL Rally commentary[/url]. Funny, I thinks as I read. I didn't know DBAs were dinosaurs.Then something he said struck me in an odd way. AHHA! I says to myself. There's the opening that women are more likely to take then men.
Maybe I'm wrong, but I always see men in the workplace only wanting to solve the problems they find interesting themselves rather than positioning themselves to solve the problems the company needs solving. What do you think? (I've linked my blog with my thoughts on the issue.)
Yes, I enjoy solving problems I find interesting, but I think that's probably an altruism (or close to it) for nearly everyone. Usually, the ones that I find interesting are the complicated ones that the company needs to be solved. I will certainly work on the ones that need solving whether they're interesting or not, but I enjoy the interesting ones simply because they're interesting.
I can only speak for myself, not for all men. I don't know about the differences in how men and women solve problems.
Well, I guess my question is... Do you just assume you know what those problems are? Do you have to be told? Or do you proactively ask?
In the area of performance, I go looking for them. Do I think I know what all of them are? Absolutely not, and I certainly hope I never become so arrogant to think I can find them all. I find some on my own and some are brought to me by others.
I also ask others and have mixed results. Some people don't ever want to admit to having any problems, while others appreciate help and want to learn from the tuning experience. I find the same thing to be true for design.
How about you?
Well, see. I'm not just talking about performance here. I'm talking about everything.
Actually, I do go to the boss at least once every two months and say "What's at the top of our agenda? What do you need help with or what should I be working on, because if you don't say otherwise, I'm tackling X project this week."
And the project could be anything from moving jobs from one server to another, to creating a new backup / recovery plan, to hitting all those low priority data fix projects that have been on our list. Or it could be calling up corporate to schedule a conference call about our server move, or the domain controller reboot project, etc.
So I am geniunely curious. How do all of my fellow Threadzians decide what is a priority? I'm not talking "Servers are down, building's on fire" kind of issues. I'm talking day to day operations. To paraphrase what I got from Brent's post "What is the boss's number one priority today?".
Do you assume you know? Do you have to be told? Do you proactively ask? (And yes, I do, but not as often as I should, probably).
I found that talking to the customer support people, to customer staff with ops manager or it manager or junior it type jobs, and to our people who were planning new customer installations that we had contracts for was good for deciding what today's (or this week's, or longer short term) priorities needed to be. Talking to customer people higher up the tree, to our regional sales directors, to the CEO (when we had one who actually did that job) and to suppliers was good for medium term and long term priorities. But obviously if a salesman was trying to commit us to something not feasible preventing that was top priority, and if acustomer system was down getting it back up again was also top priority (no matter why it was down). When I was a bit younger and had fewer responsibilities and a narrower range of activity I used to get priorities from discussions with my boss, discussions with sales and tech support people, and from feedback to my proposals for new projects. When I was still younger and narrowly focussed I would talk about priorities frequently with my boss and less frequently with his. When I was younger still my priorities for short term stuff were (a) what the head of department wanted me to do and (b) having my next lecture prepared to the point where the students might actually learn something and for long long term stuff what I though my research project needed, and before that I was really green and hadn't really a clue about priorities.
In the late nineties I had three years working for a compny at which their appeared to be no priorities - just chaos. I tried to sort out some priorities, but discovered that resource allocation wasalways a matte of office politics so priorities, if there were any, would be utterly irrelevant. It was not fun.
Tom
Viewing 15 posts - 47,806 through 47,820 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply