Question about scheduled job

You are the administrator of SQL Server 2000 computer. You create a job that
performs several maintenance tasks on the server’s databases. You want the
job to run whenever the server’s processor utilization falls below 5 percent.
You create a new schedule for the job and specify the start whenever the CPU(
s) become idle option. After several days, you notice that the job has never
executed although the server’s processor utilization has fallen below 5
percent several times.
What should you do?
A. Modify SQL Server Agent properties and specify a smaller idle time.
B. Modify SQL server agent properties and specify a larger idle time.
C. Write a stored procedure that executes the job whenever the @.@. IDLE
system variable is less than 5.
D. Write a stored procedure that executes the job whenever the @.@. IDLE
system variable is greater
than 1.
The processor utilization option works in conjunction with the
settings for the idle time or number of seconds the cpu remains below
the utilization percent specified. If you fall below the utilization
and the job never fires, it's generally due to the number of seconds
you have specified for the idle time never being hit so you'd want to
try lowering the number of seconds that the processor utilization
needs to be at the specified percentage. Once you hit the specified
number of seconds, the CPU is considered idle.
-Sue
On Wed, 8 Sep 2004 07:33:03 -0700, "Eric"
<Eric@.discussions.microsoft.com> wrote:

>You are the administrator of SQL Server 2000 computer. You create a job that
>performs several maintenance tasks on the servers databases. You want the
>job to run whenever the servers processor utilization falls below 5 percent.
>You create a new schedule for the job and specify the start whenever the CPU(
>s) become idle option. After several days, you notice that the job has never
>executed although the servers processor utilization has fallen below 5
>percent several times.
>What should you do?
>A. Modify SQL Server Agent properties and specify a smaller idle time.
>B. Modify SQL server agent properties and specify a larger idle time.
>C. Write a stored procedure that executes the job whenever the @.@. IDLE
>system variable is less than 5.
>D. Write a stored procedure that executes the job whenever the @.@. IDLE
>system variable is greater
>than 1.

Question about replication

You are the administrator of a SQL Server 2000 computer at your company's
warehouse. All product orders are shipped from this warehouse. Orders are
received at 30 sales offices. Each sales office offers a range of products
specific to its region.
Each sales office contains one SQL Server 2000 computer. These servers
connect to the warehouse through dial- up connections as needed, typically
once a day. Each sales office needs data pertaining only to its region. You
need to replicate inventory data from the server at the warehouse to the
servers at the sales offices. You want to minimize the amount of time needed
to replicate the data. Which three actions should you take? (Each correct
answer represents part of the solution. Choose three.)
A. Create one publication for each Subscriber.
B. Create one publication for all Subscribers.
C. Enable horizontal filtering.
D.Enable vertical filtering.
E. Use pull subscriptions.
F. Use push subscriptions.
pls. help.
I would create one pub for all subscribers, do horizontal filtering ( so
only the data a subscriber needs would be sent.), and go with pull
subscriptions ( because the work would be done at the subscriber, not at the
publisher)..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:069B5539-A863-446C-9D04-C6879CA20E5B@.microsoft.com...
> You are the administrator of a SQL Server 2000 computer at your company's
> warehouse. All product orders are shipped from this warehouse. Orders are
> received at 30 sales offices. Each sales office offers a range of products
> specific to its region.
> Each sales office contains one SQL Server 2000 computer. These servers
> connect to the warehouse through dial- up connections as needed, typically
> once a day. Each sales office needs data pertaining only to its region.
You
> need to replicate inventory data from the server at the warehouse to the
> servers at the sales offices. You want to minimize the amount of time
needed
> to replicate the data. Which three actions should you take? (Each correct
> answer represents part of the solution. Choose three.)
> A. Create one publication for each Subscriber.
> B. Create one publication for all Subscribers.
> C. Enable horizontal filtering.
> D.Enable vertical filtering.
> E. Use pull subscriptions.
> F. Use push subscriptions.
> pls. help.

question about database design

I have a table, named car. It normally have 10000 records and will growth in
the furture.
Administrator can delete the car record through an web based administrator
platform
And we not like delete the car record physically.
My question is that, what is the best method to keep the database
performance.
1. add additional field, which called is_deleted, in the car table, and mark
it as 'T' if the record is deleted, and 'F' when the record is active.
2. create new table, which have the same as schema as car table, and named
deleted_car, when administrator delete a car record, the program will remove
a record from car table and insert it into the deleted_car table.
Thanks~I prefer the first one as there is no need for additional table
Madhivanan|||> My question is that, what is the best method to keep the database
> performance.
Make sure that you have properly designed database.
Make sure that you have properly defined indexes on the tables.
"Utada P.W. SIU" <wing0508@.hotmail.com> wrote in message
news:ujpjMOXHFHA.560@.TK2MSFTNGP12.phx.gbl...
> I have a table, named car. It normally have 10000 records and will growth
in
> the furture.
> Administrator can delete the car record through an web based administrator
> platform
> And we not like delete the car record physically.
> My question is that, what is the best method to keep the database
> performance.
> 1. add additional field, which called is_deleted, in the car table, and
mark
> it as 'T' if the record is deleted, and 'F' when the record is active.
> 2. create new table, which have the same as schema as car table, and named
> deleted_car, when administrator delete a car record, the program will
remove
> a record from car table and insert it into the deleted_car table.
> Thanks~
> --
>|||Either method will work. For a table that small either method will work
well.
If the table starts to get into the hundreds of thousands of records you
will see a performance improvment (small) by using two tables. If you get
into the millions of records it will start to actuall make a difference...
This is assuming that you are using indexes correctly. If you are not, then
having 2 tables will have a large speed improvement even with the smaller
record sets.
"Utada P.W. SIU" <wing0508@.hotmail.com> wrote in message
news:ujpjMOXHFHA.560@.TK2MSFTNGP12.phx.gbl...
>I have a table, named car. It normally have 10000 records and will growth
>in
> the furture.
> Administrator can delete the car record through an web based administrator
> platform
> And we not like delete the car record physically.
> My question is that, what is the best method to keep the database
> performance.
> 1. add additional field, which called is_deleted, in the car table, and
> mark
> it as 'T' if the record is deleted, and 'F' when the record is active.
> 2. create new table, which have the same as schema as car table, and named
> deleted_car, when administrator delete a car record, the program will
> remove
> a record from car table and insert it into the deleted_car table.
> Thanks~
> --
>|||The second option might cause you some maintenance headaches down the
road... If you update your application you have to make sure you apply
updates to both sets of tables, your application will need to be modified to
work with the changes in both sets of tables, etc. What if someone
accidentally "deletes" a record and has to bring it back/make it active
again? What if, somehow, a single item gets copied to both tables?
For 10,000 -- or even 100,000 -- records I don't think it would be worth the
hassle to split it up.
Thx
Mike C
"Utada P.W. SIU" <wing0508@.hotmail.com> wrote in message
news:ujpjMOXHFHA.560@.TK2MSFTNGP12.phx.gbl...
>I have a table, named car. It normally have 10000 records and will growth
>in
> the furture.
> Administrator can delete the car record through an web based administrator
> platform
> And we not like delete the car record physically.
> My question is that, what is the best method to keep the database
> performance.
> 1. add additional field, which called is_deleted, in the car table, and
> mark
> it as 'T' if the record is deleted, and 'F' when the record is active.
> 2. create new table, which have the same as schema as car table, and named
> deleted_car, when administrator delete a car record, the program will
> remove
> a record from car table and insert it into the deleted_car table.
> Thanks~
> --
>|||right~~|||hehe~~
right...|||thanks~
^.^|||thanks~
you made my mind clear again~|||>> 1. add additional field [sic], which called is_deleted, in the car
table, and mark it as 'T' if the record [sic] is deleted, and 'F' when
the record [sic] is active. <<
Rows are not records; columns are not fields; an RDBMS is not a
sequential file system. The basic idea is right, but make this
attribute a general status code that can take other values or make it a
timestamp so you know when the event occurred.