| Author |
Topic |
|
JSchuster
Starting Member
2 Posts |
 Posted - 2002-01-28 : 11:56:54
|
| I'm currently an Oracle DBA who is branching out into SQL Server, and I'd like to get a jump-start by taking a class in SQL Server. The environment that I will be taking over includes both SQL Server 2000 and 7.0 DBs. If I take a 5-day course in 2000, will I be able to adequately admin the 7.0 machines, or are they sufficiently different that I'll have to learn both independently? Thanks. |
|
|
andre
Constraint Violating Yak Guru
259 Posts |
Posted - 2002-01-28 : 12:08:11
|
| The differences between SQL 2000 and 7 aren't nearly as huge as the differences between 6.5 and 7. If you know 2000, you won't have a problem with 7. 2000 does have some features 7 doesn't have though:1) Table variables. These aren't in 7, so you'll need to use temp tables2) Support for XML isn't as extensive3) You cannot store a text field in a table in 7 like you can in 2000 |
 |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-01-28 : 13:48:33
|
| Continuing on the differences:Differences in ReplicationEasier Clustering Indexed ViewsDistributed Partitioned ViewsMultiple Instance SupportThere are many other things. You can read:http://www.microsoft.com/SQL/evaluation/overview/whatsnew.aspfor the differences.That being said, I think they are sufficiently the same that you will be able to administer either with SQL 2000 knowledge, as long as you are aware of the differences.However, Make sure the class starts from a point of 'no prior knowledge'. I know some classes like to assume you know 7.0, and focus on the new features of 2000.my 2 cents-Chad |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-01-29 : 02:26:44
|
| >> If I take a 5-day course in 2000, will I be able to adequately admin the 7.0 machines.Probably not - nor the 2000 machines.You will need to look at the systems, find out what they are doing and predict what effect any of your actions will have on them.Considering the number of installation configurations and types of system that can be built there is no hope of covering it in a course.The best you can hope for is to learn enough to not do too much damage while you learn how to control the systems and to recover when you do crash them.==========================================Cursors are useful if you don't know sql.Beer is not cold and it isn't fizzy. |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2002-01-29 : 08:53:18
|
User defined functions and column permissions. In 7 there were no column level permissions but in 2k there are. Just thought I'd toss those in too. All in all they are very close to each other. I would say its kinda like the differences between Windows 98 and Windows ME (If you know 1 then you know the other, but they are different in some respects)But as NR said SQL Server will take a bit longer to learn than a 5 day course even though you do already know Oracle...  DanielSQL Server DBA |
|
|
|
JSchuster
Starting Member
2 Posts |
Posted - 2002-01-29 : 11:22:31
|
Yeah, I guess I deserved that. So, I should be able to take the 2000 class, read a few books, play with a test box, and learn enough not to terminally break both systems. Thanks all.Jeremyquote:
But as NR said SQL Server will take a bit longer to learn than a 5 day course even though you do already know Oracle... DanielSQL Server DBA
|
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2002-01-29 : 12:40:12
|
I would get copies of inside sql server for both v7 and v2000 and read them from cover to cover.Pay more attention to v2000 probably.Particularly look at data and index structures, query plans, procedure cache.Look at all the dbcc commands and think about what they do and how they might interact with anything you are running on your systems.Look at transaction isolation levels - dirty reads will enable you to query a live system with a good chance of not killing connections. Something a lot of DBAs "forget".Look at backup strategies and how to restore a system - this will give a good idea about how the transaction log is used.Look at the articles on this site and others and look at the questions asked - most mistakes have already been made and you will get an idea of theareas that cause problems.Build a system yourself, restore a live database to it - look at what happens to user logons (see this site if you can't figure out how to re-establish them). Use query analyser to update records in transactions without terminating them and look at master..syslocks to find out what is locked. Run queries in another window to verify your knowledge of lock compatiblity.Do a load of backups and restores - including tr logs and incrementals.Play around with permissions.Create some scheduled jobs, let them run and look at the system tables in msdb.Go to your live systems and spend some time looking at the locks held by spids, transaction lengths and the commands being executed - just getting an idea of what happens on a system and how things act can be invaluable. Make sure you set the transaction isolation level to read uncommitted.Play around with the profiler to see what is being executed by a connection.If you do all that (given that you already know about relational databases) then you will probably get more benifit than from a course.And learn to drink more beer - one of the areas in which Oracle people are deficient compared to proper database DBAs  .==========================================Cursors are useful if you don't know sql.Beer is not cold and it isn't fizzy.Edited by - nr on 01/29/2002 12:44:24 |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-01-29 : 12:58:06
|
quote:
In 7 there were no column level permissions but in 2k there are.
How come they existed in 6.5? I was able to set column level permissions on a couple of 6.5 tables. Never tried it in 7.0 though, but I can't believe they took them away then put them back. |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2002-01-29 : 13:05:57
|
quote:
quote:
In 7 there were no column level permissions but in 2k there are.
How come they existed in 6.5? I was able to set column level permissions on a couple of 6.5 tables. Never tried it in 7.0 though, but I can't believe they took them away then put them back.
Thats a good question. Actually in EM you cannot drill down on a tables permissions to see column level permissions (Unless this is only an Enterprise edition feature). However, in SQL 2k you can drill down on the table permissions to get to the column level.DanielSQL Server DBA |
|
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-01-29 : 13:46:17
|
quote:
In 7 there were no column level permissions but in 2k there are.
I'm pretty sure you could still do it in SQL7 using T-SQL... Probably looks something like this(unfortunately don't have a SQL7 box to test on):GRANT SELECT ON mytable(mycol) TO myuser |
|
|
|
|
Will a 2000 DBA course also apply to 7.0?