uninstall SQL: path

Showing posts with label path. Show all posts

Monday, March 19, 2012

Cascading path problem

Hello,
The following SQL code produces the famous multiple cascading paths problem.
How should I design the tables to have the below functionality, but keep the
cascading paths? A Doc doesn't necessarily have to be related to a Folder,
but must be related to a Cust.
Changing ON UPDATE to NO ACTION would solve it partly, but it just doesn't
feel right.
Thanks for any help!
cheers,
Jonah
CREATE TABLE Cust (
usr_name varchar(20) NOT NULL,
usr_pwd varchar(40) NOT NULL,
customer_name nvarchar(50) NOT NULL,
created_date datetime default getdate() NOT NULL,
change_date datetime default getdate() NOT NULL,
deactivate_date datetime default getdate() NULL
) ON [PRIMARY]
GO
ALTER TABLE Cust ADD CONSTRAINT
PK_Cust PRIMARY KEY CLUSTERED
(
usr_name
) ON [PRIMARY]
GO
CREATE TABLE Folders (
folder_id int NOT NULL ,
folder_name nvarchar(20) NOT NULL ,
folder_description nvarchar(150) NULL ,
usr_name varchar(20) NOT NULL
) ON [PRIMARY]
GO
ALTER TABLE Folders ADD CONSTRAINT
PK_Folders PRIMARY KEY CLUSTERED
(
folder_id
) ON [PRIMARY]
GO
ALTER TABLE Folders ADD CONSTRAINT
FK_Folders_Cust FOREIGN KEY
(
usr_name
) REFERENCES Cust
(
usr_name
) ON UPDATE CASCADE
GO
CREATE TABLE Docs (
doc_id int NOT NULL,
header nvarchar(255) not null,
created_date datetime default getdate() NOT NULL,
updated_date datetime default getdate() NOT NULL,
usr_name varchar(20) NOT NULL
) ON [PRIMARY]
GO
ALTER TABLE Docs ADD CONSTRAINT
PK_Docs PRIMARY KEY CLUSTERED
(
doc_id
) ON [PRIMARY]
GO
ALTER TABLE Docs ADD CONSTRAINT
FK_Cust_Docs FOREIGN KEY
(
usr_name
) REFERENCES Cust
(
usr_name
) ON UPDATE CASCADE
ON DELETE NO ACTION
GO
CREATE TABLE DocsInFolders
(
doc_id int NOT NULL,
folder_id int NOT NULL
) ON [PRIMARY]
GO
ALTER TABLE DocsInFolders ADD CONSTRAINT
PK_DocsInFolders PRIMARY KEY CLUSTERED
(
doc_id,
folder_id
) ON [PRIMARY]
GO
ALTER TABLE DocsInFolders ADD CONSTRAINT
FK_DocsInFolders_Folders FOREIGN KEY
(
folder_id
) REFERENCES Folders
(
folder_id
) ON UPDATE CASCADE
ON DELETE CASCADE
GO
ALTER TABLE DocsInFolders ADD CONSTRAINT
FK_DocsInFolders_Docs FOREIGN KEY
(
doc_id
) REFERENCES Docs
(
doc_id
) ON UPDATE CASCADE
ON DELETE CASCADE
GOYou say 'A Doc *doesn't necessarily have to be* related to a Folder,
but *must be* related to a Cust.'
Keep cascading on FK_DocsInFolders_Docs, but manage the Cust<--Docs
relationship in procedures. You make it sound as if the importance of the
Cust<--Docs relationship supercedes the importance of the Folders<--Docs
relationship.
Vital relationships should not be cascading.
ML|||Correct. The Cust<--Docs relationship is more importance, but that's why I
have only ON UPDATE CASCADE (to make possible usr_name changes up to date)
and not ON DELETE because I don't want Custs having Docs deleted by mistake.
An SP takes care of that.
So what you are saying is that I should change the ON CHANGE to NO ACTION as
well?
/Jonah
"ML" <ML@.discussions.microsoft.com> skrev i meddelandet
news:601F4976-E669-4865-9D92-FBAF9A16CA8F@.microsoft.com...
> You say 'A Doc *doesn't necessarily have to be* related to a Folder,
> but *must be* related to a Cust.'
> Keep cascading on FK_DocsInFolders_Docs, but manage the Cust<--Docs
> relationship in procedures. You make it sound as if the importance of the
> Cust<--Docs relationship supercedes the importance of the Folders<--Docs
> relationship.
> Vital relationships should not be cascading.
>
> ML|||If usr_name can be changed then using it as a primary key (and/or referencin
g
it from a foreign key table) is really bad practice. Either disallow usr_nam
e
changes or use a better kandidate key.
I wouldn't allow cascades for this one.
ML|||OK. So if I disallow cascades for usr_name, you would consider the design to
be correct?
/Jonah
"ML" <ML@.discussions.microsoft.com> skrev i meddelandet
news:90F300A3-7104-4924-A594-E28AC05D645D@.microsoft.com...
> If usr_name can be changed then using it as a primary key (and/or
> referencing
> it from a foreign key table) is really bad practice. Either disallow
> usr_name
> changes or use a better kandidate key.
> I wouldn't allow cascades for this one.
>
> ML|||As far as I can see, the design is fine. I would, however, do something abou
t
the Folders and Docs entities. Right now you allow a single document to exis
t
in more than one folder, which can lead to problems. The same goes for
folders - you should focus on preventing circular references.
Oh, and if any given document cannot exist in more than one folder, then the
DocsInFolders table is obsolete. You could simply add a nullable folder_id
foreign key to the Docs table (nullable since you've mentioned that a
document need not exist in any folder).
I hope you started on paper. :) And in case you haven't, maybe you'll do it
next time.
ML|||My design question applied to the cascading paths, not the business rules
themselves. One Doc may actually exist in several Folders.
- One Cust may have zero or more Folders
- One Cust may have zero or more Docs not connected to a Folder
- One Folder may have zero or more Docs related
Thus, my question was only related to if there's a better way of designing
the relations and tables to avoid circular references, which now occurs.
FYI, I didn't start on paper. I use Visio.
Thank you,
Jonah
"ML" <ML@.discussions.microsoft.com> skrev i meddelandet
news:F981A87A-893F-4940-9EBD-566C385CF1CB@.microsoft.com...
> As far as I can see, the design is fine. I would, however, do something
> about
> the Folders and Docs entities. Right now you allow a single document to
> exist
> in more than one folder, which can lead to problems. The same goes for
> folders - you should focus on preventing circular references.
> Oh, and if any given document cannot exist in more than one folder, then
> the
> DocsInFolders table is obsolete. You could simply add a nullable folder_id
> foreign key to the Docs table (nullable since you've mentioned that a
> document need not exist in any folder).
> I hope you started on paper. :) And in case you haven't, maybe you'll do
> it
> next time.
>
> ML|||No pun intended.
You are right - there is a better way to avoid circular references. You
might find more answers studying trees and hierarchies. Consider this model:
ItemInstance : ItemID : BelongsToInstance : ItemType
ItemInstance is unique.
ItemID can be either cust_id, folder_id or doc_id.
BelongsToInstance is a foreign key referencing ItemInstance.
ItemType designates whether ItemID is customer, folder or document.
Valid relationships are:
1) Customer/Folder/Document
2) Customer/Document
3) Folder/Folder (<-- not sure about this one, but seems logical, however:
parent folder_id must should be equal to child folder_id).
A customer can only exist as a root element (BelongsToInstance is null).
A Document can only exist as a leaf element (its ItemInstance is never
referenced in a BelongsToInstance).
The above constraints could be reinforced through the use of indexed views.
ItemInstance and BelongsToInstance prevent circular references while still
allowing all possible relationships between the three entities.
ML|||Thank you for your detailed answer.
I do have a copy of a trees and hierarchies book which I could take a closer
look into (Joe Celko's Trees and Hierarchies in SQL for Smarties). Maybe I
can find some more answers and examples there.
/Jonah
"ML" <ML@.discussions.microsoft.com> skrev i meddelandet
news:D5B9F5D8-4790-4088-BF18-14DE5119891D@.microsoft.com...
> No pun intended.
> You are right - there is a better way to avoid circular references. You
> might find more answers studying trees and hierarchies. Consider this
> model:
> ItemInstance : ItemID : BelongsToInstance : ItemType
> ItemInstance is unique.
> ItemID can be either cust_id, folder_id or doc_id.
> BelongsToInstance is a foreign key referencing ItemInstance.
> ItemType designates whether ItemID is customer, folder or document.
> Valid relationships are:
> 1) Customer/Folder/Document
> 2) Customer/Document
> 3) Folder/Folder (<-- not sure about this one, but seems logical, however:
> parent folder_id must should be equal to child folder_id).
> A customer can only exist as a root element (BelongsToInstance is null).
> A Document can only exist as a leaf element (its ItemInstance is never
> referenced in a BelongsToInstance).
> The above constraints could be reinforced through the use of indexed
> views.
> ItemInstance and BelongsToInstance prevent circular references while still
> allowing all possible relationships between the three entities.
>
> ML|||What about using a nested sets model for the hierarchy? I am not a big
fanof misxed node trees, but this case is pretty easy:
1) If it is the root node, it is a Customer
2) If it is a leaf node, it is a document
3) other it is a folder
CREATE TABLE DocumentHierarchy
(customer_id INTEGER NOT NULL
REFERENCES Customers
ON UPDATE CASCADE
ON DELETE CASCADE,
folder_id INTEGER -- null means no folder
REFERENCES Folders (folder_id)
ON UPDATE CASCADE
ON DELETE CASCADE,
document_id INTEGER -- null means no document
REFERENCES Documents(doc_id)
ON UPDATE CASCADE
ON DELETE CASCADE,
lft INTEGER NOT NULL CHECK (lft >0),
rgt INTEGER NOT NULL CHECK (rgt >lft),
PRIMARY KEY (customer_id, lft, rgt));
untested. You can also get a copy of TREES & HIERARCHIES IN SQL for
more ideas.

Wednesday, March 7, 2012

Career Path

Hi. Sorry if this is a little off topic. I was wondering if someone could provide a little advice please.

currently work in a software development team leader role working in mainly

VB.NET and SQL Server 2000 technologies. Recently I’ve become more interested

in data analysis and decision support systems etc and am thinking in the future

I’d like to specialise in this area.

I was wondering if anyone has any advice

on courses and accreditations that would help me to get into this field. I

don’t have any previous experience of analysis services or similar tools but

have several years of SQL experience including writing applications, reports

and as an administrator. Many thanks in advance.

This DM Review article on BI career considerations may be relevant:

http://www.dmreview.com/article_sub.cfm?articleId=1060142

Career Considerations in the Field of Business Intelligence

Article published in DM Review Magazine
August 2006 Issue

By Nan Weitzman and Jonathan Wu

Never has there been a better time to have a career in business intelligence (BI) than the present. The discipline of making decisions based on relevant, timely and accurate information is now a standard business practice. The technology that we enjoy today supports this discipline while competitive, economic and regulatory factors are forcing individuals to embrace it. As the amount of data continues to accumulate at a rapid pace, organizing it in a meaningful manner is critical to realizing and sustaining any value.

...

|||That's great, I will take a look. Thanks for your help.

Career move for DBAs

Had some questions with regards to a career path for DBAs.
1) Do DBAs within Operations report to a Database Manager ? Is that the
right title ? If not, curious to know who else do DBAs report to in an
organisation ?
2) How do DBAs keep their jobs challenging on a day to day basis ? How does
the manager keep the DBAs happy besides the money factor ? The DBAs job is
keeping systems up and running and securing the data and being available to
support the organisation. Doing that day in and day out will eventually get
to you and want to make sure theres exciting work
3) What can DBAs do to move up in their career ?Hi
1. If you have more than a few DBA's, they should be in their own group,
having their own line manager. We have over 3000 database servers (from the
big 3 vendors), and there are multiple teams on duty at any one time.
2. Job rotation within the teams, continuous training. Maybe a bit of a desk
swap with a development DBA if he is capable.
3. Database Engineering (the guys who architect and design the standards,
tools and database product setups, based on your runtime OS platforms and
requirements) is the logical place for them to go after production DBA, and
possibly, up to Lead DB Engineer. Any other track is a paper pushing (sorry
management) track and then the DBA throws his technical knowledge away.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Anonymous" <anonymous@.hotmail.com> wrote in message
news:uOIdBuy8FHA.476@.TK2MSFTNGP15.phx.gbl...
> Had some questions with regards to a career path for DBAs.
> 1) Do DBAs within Operations report to a Database Manager ? Is that the
> right title ? If not, curious to know who else do DBAs report to in an
> organisation ?
> 2) How do DBAs keep their jobs challenging on a day to day basis ? How
> does the manager keep the DBAs happy besides the money factor ? The DBAs
> job is keeping systems up and running and securing the data and being
> available to support the organisation. Doing that day in and day out will
> eventually get to you and want to make sure theres exciting work
> 3) What can DBAs do to move up in their career ?
>|||3000 DB Servers Mike ? WoW.. Is this all the db servers within your company
? Does the same DBA team look after development, test,Staging,etc in
addition to production ? Or are there different teams for those
environments, such as OLTP vs Data Warehouse vs BackOffice Applications,etc
?
Who runs data changes on a day to day basis ? Assuming some changes are not
part of the tools and need to be executed using QA.. Do DBAs do that or do
you have some data change analysts doing that ?
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:OIYh6X28FHA.1148@.tk2msftngp13.phx.gbl...
> Hi
> 1. If you have more than a few DBA's, they should be in their own group,
> having their own line manager. We have over 3000 database servers (from
> the big 3 vendors), and there are multiple teams on duty at any one time.
> 2. Job rotation within the teams, continuous training. Maybe a bit of a
> desk swap with a development DBA if he is capable.
> 3. Database Engineering (the guys who architect and design the standards,
> tools and database product setups, based on your runtime OS platforms and
> requirements) is the logical place for them to go after production DBA,
> and possibly, up to Lead DB Engineer. Any other track is a paper pushing
> (sorry management) track and then the DBA throws his technical knowledge
> away.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Anonymous" <anonymous@.hotmail.com> wrote in message
> news:uOIdBuy8FHA.476@.TK2MSFTNGP15.phx.gbl...
>> Had some questions with regards to a career path for DBAs.
>> 1) Do DBAs within Operations report to a Database Manager ? Is that the
>> right title ? If not, curious to know who else do DBAs report to in an
>> organisation ?
>> 2) How do DBAs keep their jobs challenging on a day to day basis ? How
>> does the manager keep the DBAs happy besides the money factor ? The DBAs
>> job is keeping systems up and running and securing the data and being
>> available to support the organisation. Doing that day in and day out will
>> eventually get to you and want to make sure theres exciting work
>> 3) What can DBAs do to move up in their career ?
>|||Hi
All changes have to be in the form of scripts, with documentation, that can
be run by the DBA's. OSQL for SQL Server. No script, no update to the
servers. No change control ticket, no change. No backout procedure, no
change.
They look after all the DB servers, be they Dev, Test, Prod or Disaster
Recovery.
The platforms are standard, each install is identical to the next, and the
rules are the rules. Projects can not have something that was not engineered
by Engineering and approved by Security.
Nobody but the DBA team have sa privileges. If the application needs it, it
does not go onto the servers. dbo needs approval from security.
24x7x365, follow the sun, in 4 locations around the world.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Anonymous" <anonymous@.hotmail.com> wrote in message
news:exJoFe48FHA.1032@.TK2MSFTNGP11.phx.gbl...
> 3000 DB Servers Mike ? WoW.. Is this all the db servers within your
> company ? Does the same DBA team look after development, test,Staging,etc
> in addition to production ? Or are there different teams for those
> environments, such as OLTP vs Data Warehouse vs BackOffice
> Applications,etc ?
> Who runs data changes on a day to day basis ? Assuming some changes are
> not part of the tools and need to be executed using QA.. Do DBAs do that
> or do you have some data change analysts doing that ?
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:OIYh6X28FHA.1148@.tk2msftngp13.phx.gbl...
>> Hi
>> 1. If you have more than a few DBA's, they should be in their own group,
>> having their own line manager. We have over 3000 database servers (from
>> the big 3 vendors), and there are multiple teams on duty at any one time.
>> 2. Job rotation within the teams, continuous training. Maybe a bit of a
>> desk swap with a development DBA if he is capable.
>> 3. Database Engineering (the guys who architect and design the standards,
>> tools and database product setups, based on your runtime OS platforms and
>> requirements) is the logical place for them to go after production DBA,
>> and possibly, up to Lead DB Engineer. Any other track is a paper pushing
>> (sorry management) track and then the DBA throws his technical knowledge
>> away.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "Anonymous" <anonymous@.hotmail.com> wrote in message
>> news:uOIdBuy8FHA.476@.TK2MSFTNGP15.phx.gbl...
>> Had some questions with regards to a career path for DBAs.
>> 1) Do DBAs within Operations report to a Database Manager ? Is that the
>> right title ? If not, curious to know who else do DBAs report to in an
>> organisation ?
>> 2) How do DBAs keep their jobs challenging on a day to day basis ? How
>> does the manager keep the DBAs happy besides the money factor ? The DBAs
>> job is keeping systems up and running and securing the data and being
>> available to support the organisation. Doing that day in and day out
>> will eventually get to you and want to make sure theres exciting work
>> 3) What can DBAs do to move up in their career ?
>>
>|||Mike,
I had a few more questions and would like to get in touch with you directly
. How can I do so?
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:O4QkSC58FHA.2264@.tk2msftngp13.phx.gbl...
> Hi
> All changes have to be in the form of scripts, with documentation, that
> can be run by the DBA's. OSQL for SQL Server. No script, no update to the
> servers. No change control ticket, no change. No backout procedure, no
> change.
> They look after all the DB servers, be they Dev, Test, Prod or Disaster
> Recovery.
> The platforms are standard, each install is identical to the next, and the
> rules are the rules. Projects can not have something that was not
> engineered by Engineering and approved by Security.
> Nobody but the DBA team have sa privileges. If the application needs it,
> it does not go onto the servers. dbo needs approval from security.
> 24x7x365, follow the sun, in 4 locations around the world.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Anonymous" <anonymous@.hotmail.com> wrote in message
> news:exJoFe48FHA.1032@.TK2MSFTNGP11.phx.gbl...
>> 3000 DB Servers Mike ? WoW.. Is this all the db servers within your
>> company ? Does the same DBA team look after development, test,Staging,etc
>> in addition to production ? Or are there different teams for those
>> environments, such as OLTP vs Data Warehouse vs BackOffice
>> Applications,etc ?
>> Who runs data changes on a day to day basis ? Assuming some changes are
>> not part of the tools and need to be executed using QA.. Do DBAs do that
>> or do you have some data change analysts doing that ?
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:OIYh6X28FHA.1148@.tk2msftngp13.phx.gbl...
>> Hi
>> 1. If you have more than a few DBA's, they should be in their own group,
>> having their own line manager. We have over 3000 database servers (from
>> the big 3 vendors), and there are multiple teams on duty at any one
>> time.
>> 2. Job rotation within the teams, continuous training. Maybe a bit of a
>> desk swap with a development DBA if he is capable.
>> 3. Database Engineering (the guys who architect and design the
>> standards, tools and database product setups, based on your runtime OS
>> platforms and requirements) is the logical place for them to go after
>> production DBA, and possibly, up to Lead DB Engineer. Any other track is
>> a paper pushing (sorry management) track and then the DBA throws his
>> technical knowledge away.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "Anonymous" <anonymous@.hotmail.com> wrote in message
>> news:uOIdBuy8FHA.476@.TK2MSFTNGP15.phx.gbl...
>> Had some questions with regards to a career path for DBAs.
>> 1) Do DBAs within Operations report to a Database Manager ? Is that the
>> right title ? If not, curious to know who else do DBAs report to in an
>> organisation ?
>> 2) How do DBAs keep their jobs challenging on a day to day basis ? How
>> does the manager keep the DBAs happy besides the money factor ? The
>> DBAs job is keeping systems up and running and securing the data and
>> being available to support the organisation. Doing that day in and day
>> out will eventually get to you and want to make sure theres exciting
>> work
>> 3) What can DBAs do to move up in their career ?
>>
>>
>|||Hi
Look at my posting address and my IM address below.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Anonymous" <anonymous@.hotmail.com> wrote in message
news:eWPWmZ58FHA.3952@.TK2MSFTNGP12.phx.gbl...
> Mike,
> I had a few more questions and would like to get in touch with you
> directly . How can I do so?
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:O4QkSC58FHA.2264@.tk2msftngp13.phx.gbl...
>> Hi
>> All changes have to be in the form of scripts, with documentation, that
>> can be run by the DBA's. OSQL for SQL Server. No script, no update to the
>> servers. No change control ticket, no change. No backout procedure, no
>> change.
>> They look after all the DB servers, be they Dev, Test, Prod or Disaster
>> Recovery.
>> The platforms are standard, each install is identical to the next, and
>> the rules are the rules. Projects can not have something that was not
>> engineered by Engineering and approved by Security.
>> Nobody but the DBA team have sa privileges. If the application needs it,
>> it does not go onto the servers. dbo needs approval from security.
>> 24x7x365, follow the sun, in 4 locations around the world.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "Anonymous" <anonymous@.hotmail.com> wrote in message
>> news:exJoFe48FHA.1032@.TK2MSFTNGP11.phx.gbl...
>> 3000 DB Servers Mike ? WoW.. Is this all the db servers within your
>> company ? Does the same DBA team look after development,
>> test,Staging,etc in addition to production ? Or are there different
>> teams for those environments, such as OLTP vs Data Warehouse vs
>> BackOffice Applications,etc ?
>> Who runs data changes on a day to day basis ? Assuming some changes are
>> not part of the tools and need to be executed using QA.. Do DBAs do that
>> or do you have some data change analysts doing that ?
>> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
>> news:OIYh6X28FHA.1148@.tk2msftngp13.phx.gbl...
>> Hi
>> 1. If you have more than a few DBA's, they should be in their own
>> group, having their own line manager. We have over 3000 database
>> servers (from the big 3 vendors), and there are multiple teams on duty
>> at any one time.
>> 2. Job rotation within the teams, continuous training. Maybe a bit of a
>> desk swap with a development DBA if he is capable.
>> 3. Database Engineering (the guys who architect and design the
>> standards, tools and database product setups, based on your runtime OS
>> platforms and requirements) is the logical place for them to go after
>> production DBA, and possibly, up to Lead DB Engineer. Any other track
>> is a paper pushing (sorry management) track and then the DBA throws his
>> technical knowledge away.
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "Anonymous" <anonymous@.hotmail.com> wrote in message
>> news:uOIdBuy8FHA.476@.TK2MSFTNGP15.phx.gbl...
>> Had some questions with regards to a career path for DBAs.
>> 1) Do DBAs within Operations report to a Database Manager ? Is that
>> the right title ? If not, curious to know who else do DBAs report to
>> in an organisation ?
>> 2) How do DBAs keep their jobs challenging on a day to day basis ? How
>> does the manager keep the DBAs happy besides the money factor ? The
>> DBAs job is keeping systems up and running and securing the data and
>> being available to support the organisation. Doing that day in and day
>> out will eventually get to you and want to make sure theres exciting
>> work
>> 3) What can DBAs do to move up in their career ?
>>
>>
>>
>|||On Sun, 27 Nov 2005 00:21:00 -0800, "Anonymous"
<anonymous@.hotmail.com> wrote:
>2) How do DBAs keep their jobs challenging on a day to day basis ?
Always more backup procedures to create, performance to tune. But
look for something new to do as a background task. New
certifications, if nothing else.
> How does
>the manager keep the DBAs happy besides the money factor ?
The book on this says keep techies happy by offering them new tech,
keeping skills up to date, and like that.
>The DBAs job is
>keeping systems up and running and securing the data and being available to
>support the organisation. Doing that day in and day out will eventually get
>to you and want to make sure theres exciting work
I'm always more on the development side anyway, but just profiling the
data, the better to manage performance, is always something I like to
spend time on. What are the most common names in your database? How
does that correspond to address? Who are the top 10 customers in your
major product areas? Usually there are meaningful reports on these
kinds of things done by marketing in your organization, but that's
sort of top-down, and as a DBA you can sometimes suggest some
bottom-up views that are interesting - possibly getting you involved
with marketing, or special projects, and the like.
That is, if it doesn't violate policy or protocol for you to run those
kinds of queries as a DBA. It probably should, yet nobody ever seems
to yell at me when I show up with some curious report I just ran for
no reason. But if I wasn't easily amused by such things, I suppose I
wouldn't like being a DBA, or data architect, or whatever it is I'm
supposed to be these days.
Josh

Monday, March 19, 2012

Cascading path problem

Wednesday, March 7, 2012

Career Path

Career Considerations in the Field of Business Intelligence

Career move for DBAs

Career move for DBAs

Career move for DBAs

uninstall SQL

Blog Archive

About Me