if object_id( 'Testing123' ) is not null
drop table dbo.Testing123;
go
create table Testing123 ( ordinal int identity(1,1) primary key clustered, data varchar(max) )
go
insert into Testing123 ( data )
select o1.name + ' - ' + o2.name
from sys.objects o1
cross join sys.objects o2
go
--Now we'll look at the count of rows, and the pages that belong to the table.
select count(*) from dbo.Testing123;
go
dbcc ind('Test', 'Testing123', -1);
go
--We get a count of 504 rows and the following pages:
/*
(3025 row(s) affected)
-----------
3025
(1 row(s) affected)
PageFID PagePID IAMFID IAMPID ObjectID IndexID PartitionNumber PartitionID iam_chain_type PageType IndexLevel NextPageFID NextPagePID PrevPageFID PrevPagePID
------- ----------- ------ ----------- ----------- ----------- --------------- -------------------- -------------------- -------- ---------- ----------- ----------- ----------- -----------
1 154 NULL NULL 21575115 1 1 72057594038845440 In-row data 10 NULL 0 0 0 0
1 153 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 156 0 0
1 155 1 154 21575115 1 1 72057594038845440 In-row data 2 1 0 0 0 0
1 156 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 157 1 153
1 157 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 158 1 156
1 158 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 159 1 157
1 159 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 168 1 158
1 168 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 169 1 159
1 169 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 176 1 168
1 176 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 177 1 169
1 177 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 178 1 176
1 178 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 179 1 177
1 179 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 180 1 178
1 180 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 181 1 179
1 181 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 182 1 180
1 182 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 183 1 181
1 183 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 184 1 182
1 184 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 185 1 183
1 185 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 186 1 184
1 186 1 154 21575115 1 1 72057594038845440 In-row data 1 0 0 0 1 185
(20 row(s) affected)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
*/
--Next, start a transaction and truncate the table. Verify that DBCC IND shows no pages belonging to the table and the count is 0. Then, look at the locks.
begin tran
truncate table dbo.Testing123;
insert into Testing123 ( data )
select o1.name
from sys.objects o1
select count(*) from dbo.Testing123;
dbcc ind('Test', 'Testing123', -1);
dbcc extentinfo('Test', 'Testing123', -1);
select resource_type, resource_description, request_mode
from sys.dm_tran_locks
where resource_type in ('EXTENT', 'PAGE')
and resource_database_id = db_id('Test');
--You should see 2 rows from DBCC IND, and 55 rows from count(*). But the locks info should return something like:
/*
(55 row(s) affected)
-----------
55
(1 row(s) affected)
PageFID PagePID IAMFID IAMPID ObjectID IndexID PartitionNumber PartitionID iam_chain_type PageType IndexLevel NextPageFID NextPagePID PrevPageFID PrevPagePID
------- ----------- ------ ----------- ----------- ----------- --------------- -------------------- -------------------- -------- ---------- ----------- ----------- ----------- -----------
1 155 NULL NULL 149575571 1 1 72057594038976512 In-row data 10 NULL 0 0 0 0
1 154 1 155 149575571 1 1 72057594038976512 In-row data 1 0 0 0 0 0
(2 row(s) affected)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
file_id page_id pg_alloc ext_size object_id index_id partition_number partition_id iam_chain_type pfs_bytes
----------- ----------- ----------- ----------- ----------- ----------- ---------------- -------------------- -------------------- ------------------
1 154 1 1 149575571 1 1 72057594038976512 In-row data 0x6000000000000000
(1 row(s) affected)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
resource_type resource_description request_mode
------------------------------------------------------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------------------------------
PAGE 1:155 X
PAGE 1:153 X
PAGE 1:182 X
PAGE 1:183 X
PAGE 1:180 X
PAGE 1:181 X
PAGE 1:178 X
PAGE 1:179 X
PAGE 1:176 X
PAGE 1:177 X
EXTENT 1:176 X
EXTENT 1:216 X
EXTENT 1:208 X
(13 row(s) affected)
*/
--So the extent and page locks include all the pages that we saw in the DBCC IND output. (Remember, an extent is 8 contiguous pages, starting at the one that describes the extent.)
--Only after you ROLLBACK the transaction will the locks be released, and you should see all the rows and pages back in the table again.
rollback tran;
go
select count(*) from dbo.Testing123;
dbcc ind('Test', 'Testing123', -1);
go
/*
-----------
3025
(1 row(s) affected)
PageFID PagePID IAMFID IAMPID ObjectID IndexID PartitionNumber PartitionID iam_chain_type PageType IndexLevel NextPageFID NextPagePID PrevPageFID PrevPagePID
------- ----------- ------ ----------- ----------- ----------- --------------- -------------------- -------------------- -------- ---------- ----------- ----------- ----------- -----------
1 154 NULL NULL 21575115 1 1 72057594038845440 In-row data 10 NULL 0 0 0 0
1 153 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 156 0 0
1 155 1 154 21575115 1 1 72057594038845440 In-row data 2 1 0 0 0 0
1 156 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 157 1 153
1 157 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 158 1 156
1 158 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 159 1 157
1 159 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 168 1 158
1 168 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 169 1 159
1 169 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 176 1 168
1 176 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 177 1 169
1 177 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 178 1 176
1 178 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 179 1 177
1 179 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 180 1 178
1 180 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 181 1 179
1 181 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 182 1 180
1 182 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 183 1 181
1 183 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 184 1 182
1 184 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 185 1 183
1 185 1 154 21575115 1 1 72057594038845440 In-row data 1 0 1 186 1 184
1 186 1 154 21575115 1 1 72057594038845440 In-row data 1 0 0 0 1 185
(20 row(s) affected)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
*/
A GUIDE TO ADVENTURE, A GUIDEBOOK FOR LIFE
Project Leave No Trace is an educational program designed to provide information, materials, and support for youth leaders interested in the ethics and skills fundamental to "Leave No Trace" outdoor recreation.
The roots of Project Leave No Trace lie in one Wilderness Ranger’s desire to be proactive about reducing impact to Washington’s Wilderness areas. Her ideas brought the commitment of numerous people who worked together to design a program that met the goals and needs of all the partners. Since its inception, Project Leave No Trace has grown and evolved, continually improving its effectiveness and content.
The program is designed to multiply its effect by training adult leaders who then teach their youth groups and share the program with other leaders who will do the same. The program is laid out in three parts:
- The manual "A Leader's Guide to Teaching and Learning Leave No Trace"
- An introductory workshop for leaders
- The Leave No Trace Certification Event
Sponsors and supporters of Project Leave No Trace:
- National Outdoor Leadership School
- Mt. Baker Snoqualmie National Forest
- North Cascades National Park
- The Mountaineers
- Girl Scouts - Totem Council
- Chief Seattle Council - Boy Scouts of America
- Mt. Baker Council - Boy Scouts of America
- Backcountry Horsemen of Washington
- Boeing
- Microsoft
- Cascade Designs, Inc.
Preface
The Book of Mormon is full of facts, ranging from eternal truths to mundane details. This collection charts many of those facts in clear and convenient graphs and visuals.
This collection of visual aids aims to serve multiple purposes. Students and teachers will find here helpful guides for personal study, as well as images for classroom use.
The idea for this book began to take shape almost two decades ago. One of my responsibilities on the board for Macmillan’s Encyclopedia of Mormonism was to gather or create the maps, charts, and photographs that accompany its thirteen hundred articles. Personal experiences in working with several people in collecting and selecting those graphic images and, similarly, in using such visuals in many contexts confirmed for me of the value of charts in communicating important gospel precepts and interesting information.
In 1996, I turned attention specifically to Book of Mormon visuals. Morgan A. Ashton, serving as a BYU intern under my supervision, worked to locate as many previously circulated Book of Mormon charts, graphs, and maps as possible. From his findings, certain recurring themes were identified and composite charts were created. In addition, many new charts were conceived. All of these schematics were then refined and shaped on the computer by my son, Gregory Welch, who devoted the summers of 1997 and 1998 to the initial graphic development of this project.
A preliminary packet containing samples of about half of these charts was distributed by the Foundation for Ancient Research and Mormon Studies in 1997. Feedback and additions from many people have improved this publication, and they are acknowledged with much appreciation.
In order to enhance understandability, a brief narrative explanation is added to each chart. Because each chart is by nature an incomplete abstraction of much more complicated data, these brief explanatory notes quickly orient the viewer to the contents and purposes of each chart. A fuller discussion of each topic can be found in the bibliographic sources given. Amy K. Bingham, Don L. Brugger, and Eden N. Rasmussen have superbly shared much of the load in generating those comments, checking sources, and preparing the electronic version of these charts.
This collection is by no means complete. Many more charts could easily be added, and other excellent schematics can be found in other publications. Readers may want to make new charts on their own, as well as add further details to the charts created so far.
I am deeply grateful to all who have helped transform the initial vision of this project into a concrete reality. We hope that these visuals will open new vistas of insight for Book of Mormon students everywhere.
John W. Welch
Provo, Utah
Do you have an LDS-related question?
LDSfaq can help you find the answers to your questions:
- Answers to over 400 LDS-related questions
- Concise answers provided in few paragraphs
- All answers supported with references
- Related questions linked to one another
- Easy to use search function
About LDSFAQ and BYU Studies
BYU Studies sponsors LDSfaq. BYU Studies is an academic LDS journal that has produced high quality, peer-reviewed, scholary LDS research since 1959.
Pronounced
[
ree
-
uh
l-
tahym
,
reel
-
]
–noun
Fishing
.
| of or pertaining to the period in which a fisherman must leave to go fishing. |
–adjective
Computers
.
| of or pertaining to applications in which the computer must respond as rapidly as required by the user or necessitated by the process being controlled. |