Alert type not available

I've installed a new instance of SQL Server 2000 and applied SP3a.
I want to create a new SQL Server performance condition alert from the
Enterprise Manager, but this type of alert is not available. Only the type
SQL Server event alert is available. How can I make the performance condition
alerts available?
Wilbert,
Are your performance counters missing also in perfmon? If so, this
article should fix your problem.
PRB: SQL Performance Monitor Counters Missing
http://support.microsoft.com/?id=227662
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Wilbert wrote:
> I've installed a new instance of SQL Server 2000 and applied SP3a.
> I want to create a new SQL Server performance condition alert from the
> Enterprise Manager, but this type of alert is not available. Only the type
> SQL Server event alert is available. How can I make the performance condition
> alerts available?
|||Hello Mark,
The problem seems to be another instance of SQL on the same machine that is
used for Veritas. In this instance, the performance counters are available.
Is there a way to get the counters available for the second instance aswell?
Regards, Wilbert
"Mark Allison" wrote:

> Wilbert,
> Are your performance counters missing also in perfmon? If so, this
> article should fix your problem.
> PRB: SQL Performance Monitor Counters Missing
> http://support.microsoft.com/?id=227662
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Wilbert wrote:
>

Alert not triggering

I've configured an alert for the TLog that when the server generates error
9002 (out of log space) to kick off a job that will backup the TLog to clear
it. I am testing the alert and I receive the error message, but the it will
not activate the alert. I've ensured that it is enabled and that the job
works, but for some reason the alert is not working. Can anyone help?
Andrew
Does the error show up in the `Windows event log?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Big Ern" <BigErn@.discussions.microsoft.com> wrote in message
news:0BD5E05C-F708-43D7-ADC1-6CCC75F61D26@.microsoft.com...
> I've configured an alert for the TLog that when the server generates error
> 9002 (out of log space) to kick off a job that will backup the TLog to clear
> it. I am testing the alert and I receive the error message, but the it will
> not activate the alert. I've ensured that it is enabled and that the job
> works, but for some reason the alert is not working. Can anyone help?
> Andrew
|||Yes the error appears in both the SQL and Windows event logs.
"Tibor Karaszi" wrote:

> Does the error show up in the `Windows event log?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Big Ern" <BigErn@.discussions.microsoft.com> wrote in message
> news:0BD5E05C-F708-43D7-ADC1-6CCC75F61D26@.microsoft.com...
>
|||The last think I can think of is that agent isn't started. If that isn't the case and you can't find
anything obvious in Eventlog, I'm out of ideas, I'm afraid...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Big Ern" <BigErn@.discussions.microsoft.com> wrote in message
news:7AA07BA5-5744-4DC1-BF8F-310C1C700A49@.microsoft.com...[vbcol=seagreen]
> Yes the error appears in both the SQL and Windows event logs.
> "Tibor Karaszi" wrote:
sql

Alert

Hi,
I have a question regarding alerts in SQL Server.
From what I`ve read an alert tracks a certain logged information and if the
info matches the alert definition then the alert fires up.
My question is, for instance, I want to define a Perfmon alert that will
trigger a message in the windows application log when something happens.
Is it possible to configure a SQL Server alert that will catch the string
defined in the Perfmon Alert, from the Windows application log...and if yes,
how can I configure the SQL Server alert.
e.g. I define a perfmon alert that says "Hello" when the disk space on C:
drive falls under 100Mb, is it possible to define a job that triggers when in
the windows application log a certain Information/Warrning/Error contains in
its definition the "Hello" string?
Thx
Razvan Dragomir,
MCSA / MCSA: Messaging, Exchange & Windows System Administrator
I meant to say "alert" not "job"...sorry for the mistake
Razvan Dragomir,
MCSA/MCSA:Messaging Exchange & Windows System Administrator
"Razvan Dragomir" wrote:

> Hi,
> I have a question regarding alerts in SQL Server.
> From what I`ve read an alert tracks a certain logged information and if the
> info matches the alert definition then the alert fires up.
> My question is, for instance, I want to define a Perfmon alert that will
> trigger a message in the windows application log when something happens.
> Is it possible to configure a SQL Server alert that will catch the string
> defined in the Perfmon Alert, from the Windows application log...and if yes,
> how can I configure the SQL Server alert.
> e.g. I define a perfmon alert that says "Hello" when the disk space on C:
> drive falls under 100Mb, is it possible to define a job that triggers when in
> the windows application log a certain Information/Warrning/Error contains in
> its definition the "Hello" string?
>
> Thx
> --
> Razvan Dragomir,
> MCSA / MCSA: Messaging, Exchange & Windows System Administrator
>

Alert

Hi,
I have a question regarding alerts in SQL Server.
From what I`ve read an alert tracks a certain logged information and if the
info matches the alert definition then the alert fires up.
My question is, for instance, I want to define a Perfmon alert that will
trigger a message in the windows application log when something happens.
Is it possible to configure a SQL Server alert that will catch the string
defined in the Perfmon Alert, from the Windows application log...and if yes,
how can I configure the SQL Server alert.
e.g. I define a perfmon alert that says "Hello" when the disk space on C:
drive falls under 100Mb, is it possible to define a job that triggers when i
n
the windows application log a certain Information/Warrning/Error contains in
its definition the "Hello" string?
Thx
--
Razvan Dragomir,
MCSA / MCSA: Messaging, Exchange & Windows System AdministratorI meant to say "alert" not "job"...sorry for the mistake
Razvan Dragomir,
MCSA/MCSA:Messaging Exchange & Windows System Administrator
"Razvan Dragomir" wrote:

> Hi,
> I have a question regarding alerts in SQL Server.
> From what I`ve read an alert tracks a certain logged information and if th
e
> info matches the alert definition then the alert fires up.
> My question is, for instance, I want to define a Perfmon alert that will
> trigger a message in the windows application log when something happens.
> Is it possible to configure a SQL Server alert that will catch the stri
ng
> defined in the Perfmon Alert, from the Windows application log...and if ye
s,
> how can I configure the SQL Server alert.
> e.g. I define a perfmon alert that says "Hello" when the disk space on C
:
> drive falls under 100Mb, is it possible to define a job that triggers when
in
> the windows application log a certain Information/Warrning/Error contains
in
> its definition the "Hello" string?
>
> Thx
> --
> Razvan Dragomir,
> MCSA / MCSA: Messaging, Exchange & Windows System Administrator
>

Ajax Toggle Within a Gridview

Ive got a table of items which holds the privacy settings for each user. The items can either be the value 1 = Yes ,or 0 = No. Is it possible to bind these two options to a checkbox? I tryed to simply bind it to the checkboxes "checked" property, But it errored. Does anyone know how to bind an int feild to a checkbox? cos in the long run I want to add ajax toggle items to the checkboxes, but i was also wondering why that errored, but i think its cos i did my binding wrong. thanks si!

I've had this problem in the past. When using a boundfield checkbox, the type conversion fails converting from bool to int, if I remember right. If you change it to a template field, it should work though. I think this has to do with the implementation of checkboxfield.

|||

ill give it a go and get back to you! *fingers crossed* thanks si!

Agent Scheduling Confusion....

I'm a little confused.
I've been working on setting up one snapshot publication for one DB, and one
"one-way" transactional publication for another DB (both on the same
server).
My three "client" subscribers are running MSDE 2000 SP3, and they are
subscribing to these to Publishers.
As I have been in the process of setting these up, I'm having difficulty
understanding how all the "scheduling" works.
I mean there's a schedule for the "snapshot" agent. a schedule for the
"transactional" agent, a schedule for the "distribution" agent, a schedule
for the "subscriber" agent, ... and so on.
For my scenario, I need to know how to configure all the schedulers
(publisher and subscribers) so that when the "client" subscriber is
connected to the network, it automatically checks to see if there is an
updated snapshot, and see if there are any "transactional" transactions
published at the publisher. I want the publisher to publish the "snapshot"
every day at 3:00 AM, and I want the "transactional" publication to always
be "up-to-date".
Any ideas on where to get the most useful information about all the
"scheduling", or should I buy a book on replication
I've become pretty much adept at the actual setting up of all the security,
folders, etc. I'm just real unsure about the scheduling of the different
agents...
Thanks
-- Will G.
When you want the subscriber to determine when to connect to the publisher
and download updates you should be using a pull subscription.
Either that or use a push subscription and schedule your distribution agent
to run every 1 minute and have it fail continually until the subscriber
connects. The first option is the better way to go.
You can schedule your pull agent to run continuously. You might want to
configure your subscription to be managed by Windows Synchronization Manager
for a greater range of options on when to pull your subscription, for
instance it can pull your subscription on logon, when the network connection
is live, etc.
If you schedule your snapshot to run every morning at 3:00 it will only be
generated the first time, and subsequent times when a subscription needs
reinitialization, ie you made a schema change or the subscription expired.
You are still probably confused. Post back with any remaining or new
questions you might have, and someone should pick them up and answer them.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Will Gillen" <gille001@.nsuok.edu> wrote in message
news:ODw6zwevEHA.3080@.TK2MSFTNGP12.phx.gbl...
> I'm a little confused.
> I've been working on setting up one snapshot publication for one DB, and
one
> "one-way" transactional publication for another DB (both on the same
> server).
> My three "client" subscribers are running MSDE 2000 SP3, and they are
> subscribing to these to Publishers.
> As I have been in the process of setting these up, I'm having difficulty
> understanding how all the "scheduling" works.
> I mean there's a schedule for the "snapshot" agent. a schedule for the
> "transactional" agent, a schedule for the "distribution" agent, a schedule
> for the "subscriber" agent, ... and so on.
> For my scenario, I need to know how to configure all the schedulers
> (publisher and subscribers) so that when the "client" subscriber is
> connected to the network, it automatically checks to see if there is an
> updated snapshot, and see if there are any "transactional" transactions
> published at the publisher. I want the publisher to publish the
"snapshot"
> every day at 3:00 AM, and I want the "transactional" publication to always
> be "up-to-date".
> Any ideas on where to get the most useful information about all the
> "scheduling", or should I buy a book on replication
> I've become pretty much adept at the actual setting up of all the
security,
> folders, etc. I'm just real unsure about the scheduling of the different
> agents...
> Thanks
> -- Will G.
>
>

again and again... query analyzer and wrong SQL statement plan... + outer join?

Hi,
again we have some SQL statement performance problems...
I've 2 table with 140 000 records each.
I join the 2 tables and the result is also 140 000, but the query analyzer
estimate 1000 rows only.
Its a simple join with 5 equals in the join
select * from tableA inner join table B on A.ID1 = B.ID2.....
all the stats for my tables are ok.
its not a so big problem, but when I want to estimate before an execution
and when the result is far different, its a big surprise for me!
Also, we have aproblem with a query which use 1 inner join and 3 left outer
join.
Each outer join is a sub-query which contain a group by:
select *from A inner join B on A.ID = B.ID
left outer join (Select ID1, ID2 from C group by ID1, ID2) CC
on A.ID1 = CC.ID1 and A.ID2 = CC.ID2
...
(the 2 others outer join use the same syntax)
This query takes more then 10 minutes, but if I precalculate each sub-query
in a temporary table and if I use these tables instead-of the sub-queries,
the result appear in only 19seconds!!!!!
how can I tell SQL Server to use the same way without creating myself the
temporary tables?
there is any table hint option to force SQL Server to treat the sub queries
has "physical tables".
I know its not the first time you have this type of questions... so thanks
for your time (again)
Jerome.
create an Index for those 5 columns on each table.. But only those 5 columns
ll be used..
And let SQL estimate the proper Index for the execution
"Jj" <willgart@._A_hAotmail_A_.com> wrote in message
news:uX1Ih0htEHA.3604@.TK2MSFTNGP10.phx.gbl...
> Hi,
> again we have some SQL statement performance problems...
> I've 2 table with 140 000 records each.
> I join the 2 tables and the result is also 140 000, but the query analyzer
> estimate 1000 rows only.
> Its a simple join with 5 equals in the join
> select * from tableA inner join table B on A.ID1 = B.ID2.....
> all the stats for my tables are ok.
> its not a so big problem, but when I want to estimate before an execution
> and when the result is far different, its a big surprise for me!
> Also, we have aproblem with a query which use 1 inner join and 3 left
outer
> join.
> Each outer join is a sub-query which contain a group by:
> select *from A inner join B on A.ID = B.ID
> left outer join (Select ID1, ID2 from C group by ID1, ID2) CC
> on A.ID1 = CC.ID1 and A.ID2 = CC.ID2
> ...
> (the 2 others outer join use the same syntax)
> This query takes more then 10 minutes, but if I precalculate each
sub-query
> in a temporary table and if I use these tables instead-of the sub-queries,
> the result appear in only 19seconds!!!!!
> how can I tell SQL Server to use the same way without creating myself the
> temporary tables?
> there is any table hint option to force SQL Server to treat the sub
queries
> has "physical tables".
> I know its not the first time you have this type of questions... so thanks
> for your time (again)
> Jerome.
>

After Restore of a DB to another, it runs slower?

Hi,
I've created a DB,and then I restored it from the develop DB, so I can get
all the data into it, but all the qry's run slower on the production DB as
compared to the develop DB.
Any suggestions?
Thanks alot!
Deke
There can be lots of reasons but have you updated the stats after the
restore? If not run sp_updatestats.
Andrew J. Kelly SQL MVP
"Deke" <fakeemail@.nospam.net> wrote in message
news:enigPp8eEHA.4068@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I've created a DB,and then I restored it from the develop DB, so I can
get
> all the data into it, but all the qry's run slower on the production DB as
> compared to the develop DB.
> Any suggestions?
> Thanks alot!
> Deke
>
|||Hi Andrew,
Well I ran the sp_udatestats from the master db in query analyzer and it
showed a bunch of stuff being updated, but when I run the query it's still
slow (10 sec) where in the other develop db when I run the same query it's
instant.
Any other suggestions?
Thanks
Deke
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:e6jrk79eEHA.396@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> There can be lots of reasons but have you updated the stats after the
> restore? If not run sp_updatestats.
> --
> Andrew J. Kelly SQL MVP
>
> "Deke" <fakeemail@.nospam.net> wrote in message
> news:enigPp8eEHA.4068@.TK2MSFTNGP11.phx.gbl...
> get
as
>
|||Are the databases on the same server? If not could one server be better than
the other? Could network issues come into play due to the location of each
serer? Are you seeing the same results when you run SP from query analyzer?
"Deke" <fakeemail@.nospam.net> wrote in message
news:#WvNjO#eEHA.1724@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Hi Andrew,
> Well I ran the sp_udatestats from the master db in query analyzer and it
> showed a bunch of stuff being updated, but when I run the query it's still
> slow (10 sec) where in the other develop db when I run the same query it's
> instant.
> Any other suggestions?
> Thanks
> Deke
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:e6jrk79eEHA.396@.TK2MSFTNGP12.phx.gbl...
can[vbcol=seagreen]
DB
> as
>
|||Well running it in Master does nothing for the stats in the user db. Try:
USE YourDB
GO
sp_updatestats
It also takes a little while for the data to get in cache and the sp's etc
to all compile before it will be as fast as possible. Is the hardware
identical?
Andrew J. Kelly SQL MVP
"Deke" <fakeemail@.nospam.net> wrote in message
news:%23WvNjO%23eEHA.1724@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Hi Andrew,
> Well I ran the sp_udatestats from the master db in query analyzer and it
> showed a bunch of stuff being updated, but when I run the query it's still
> slow (10 sec) where in the other develop db when I run the same query it's
> instant.
> Any other suggestions?
> Thanks
> Deke
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:e6jrk79eEHA.396@.TK2MSFTNGP12.phx.gbl...
can[vbcol=seagreen]
DB
> as
>
|||Thanks Andrew,
The DB is on the same server, so it's not a hardware issue. Maybe during
the developemnt of the original query it fine tuned itself for the fastest
way, and then when copied it lost that info(?)
But doing what you posted in your last post did the job, thank you very
much!
It's fun learning something new everyday.
Deke
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:etEEx2%23eEHA.3476@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Well running it in Master does nothing for the stats in the user db. Try:
> USE YourDB
> GO
> sp_updatestats
> It also takes a little while for the data to get in cache and the sp's etc
> to all compile before it will be as fast as possible. Is the hardware
> identical?
>
> --
> Andrew J. Kelly SQL MVP
>
> "Deke" <fakeemail@.nospam.net> wrote in message
> news:%23WvNjO%23eEHA.1724@.TK2MSFTNGP10.phx.gbl...
it[vbcol=seagreen]
still[vbcol=seagreen]
it's
> can
> DB
>
|||Well each time a stored proc (or any query for that matter) is run (in each
db) it has to be compiled and a query plan is chosen. This compiled plan is
then stored in cache (memory only) so that when you run it again there is no
need to recompile again. The query plan is based on several things one of
which are the statistics for the table(s) involved. When you restore a DB
you should always update the stats to ensure they are current and useable.
When you copy a db and run a sp in the new db it has no knowledge of the old
one so it gets a new plan and if the stats are wrong it can choose a wrong
plan. When you update the stats it forces the plans to be recompiled again
and then they will use the new stats and hopefully choose the proper plan.
Andrew J. Kelly SQL MVP
"Deke" <fakeemail@.nospam.net> wrote in message
news:Ol8R49%23eEHA.2764@.TK2MSFTNGP11.phx.gbl...
> Thanks Andrew,
> The DB is on the same server, so it's not a hardware issue. Maybe
during[vbcol=seagreen]
> the developemnt of the original query it fine tuned itself for the fastest
> way, and then when copied it lost that info(?)
> But doing what you posted in your last post did the job, thank you very
> much!
> It's fun learning something new everyday.
> Deke
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:etEEx2%23eEHA.3476@.tk2msftngp13.phx.gbl...
Try:[vbcol=seagreen]
etc[vbcol=seagreen]
and[vbcol=seagreen]
> it
> still
> it's
the[vbcol=seagreen]
I[vbcol=seagreen]
production
>

Advice on upgrading 2000 to 2005 needed

Hi,
I've read through the threads related to 2000-2005 upgrade I can find on
this newsgroup. From what I've gathered, seems there are the following three
ways to upgrade.
1. in place
2. install a new instance that runs 2005 on the same database server
3. Set up a different server and then install 2005 on it.
We're currently running SQL 2000 SP3 on windows 2003. Is it true that
installing SP4 on SQL 2000 is required before it can be brought up to 2005
for in place upgrade?
For the rest two, I'm not very clear which one is better.
If we do option 3, we need to make DNS changes for server IP/name move which
always doesn't happen right away in my environment. That would most likely
extend upgrade time. But the obvious benefit is in case something wrong
happens with the upgrade, I can have the original 2000 server to safely go
back to.
For option 2, would a new 2005 instance have any negative impact on the sql
2000 instance? Are them totally independent of each other? I need to know
for sure if the 2005 instance doesn't work, the 2000 still works fine.
I'd appreciate any insight or real world experience (better) regarding 2005
upgrade. Things don't always go the way as they are instructed in the doc.
Thanks,
Bing
Upgrade supported by SQL Server 2005 include SQL Server 7.0 SP$ and SQL 2000
SP3.
About a side-by-side installation of SQL Server 2005, i'm currently running
on my laptop (2Gb RAM...) two SQL Server 2000 instances and two SQL Server
2005 instances; since the installation i've never had a problem.
The only important consideration in this case is: do i have sufficient RAM
for both instances? Surely you'll need to configure appropriately Min memory
and Max memory for each instance.
More: currently i'm administering my SQL Server 2000 instances from SQL
Server Management Studio.
Gilberto Zampatti
"bing" wrote:

> Hi,
> I've read through the threads related to 2000-2005 upgrade I can find on
> this newsgroup. From what I've gathered, seems there are the following three
> ways to upgrade.
> 1. in place
> 2. install a new instance that runs 2005 on the same database server
> 3. Set up a different server and then install 2005 on it.
> We're currently running SQL 2000 SP3 on windows 2003. Is it true that
> installing SP4 on SQL 2000 is required before it can be brought up to 2005
> for in place upgrade?
> For the rest two, I'm not very clear which one is better.
> If we do option 3, we need to make DNS changes for server IP/name move which
> always doesn't happen right away in my environment. That would most likely
> extend upgrade time. But the obvious benefit is in case something wrong
> happens with the upgrade, I can have the original 2000 server to safely go
> back to.
> For option 2, would a new 2005 instance have any negative impact on the sql
> 2000 instance? Are them totally independent of each other? I need to know
> for sure if the 2005 instance doesn't work, the 2000 still works fine.
> I'd appreciate any insight or real world experience (better) regarding 2005
> upgrade. Things don't always go the way as they are instructed in the doc.
> Thanks,
> Bing
|||Thanks for the response. RAM allocation is a very good point. Our SQL
server 2000 server (Standard) which is running only one instance currently
has 2G RAM. If I install 2005 (Standard) on the save server, that will
compete with 2000 for RAM.
Bing
"Gilberto Zampatti" wrote:
[vbcol=seagreen]
> Upgrade supported by SQL Server 2005 include SQL Server 7.0 SP$ and SQL 2000
> SP3.
> About a side-by-side installation of SQL Server 2005, i'm currently running
> on my laptop (2Gb RAM...) two SQL Server 2000 instances and two SQL Server
> 2005 instances; since the installation i've never had a problem.
> The only important consideration in this case is: do i have sufficient RAM
> for both instances? Surely you'll need to configure appropriately Min memory
> and Max memory for each instance.
> More: currently i'm administering my SQL Server 2000 instances from SQL
> Server Management Studio.
> Gilberto Zampatti
> "bing" wrote:
|||On May 18, 9:49 am, bing <b...@.discussions.microsoft.com> wrote:
> Thanks for the response. RAM allocation is a very good point. Our SQL
> server 2000 server (Standard) which is running only one instance currently
> has 2G RAM. If I install 2005 (Standard) on the save server, that will
> compete with 2000 for RAM.
> Bing
>
> "Gilberto Zampatti" wrote:
>
>
>
>
>
>
> - Show quoted text -
Here is my experience in a nutshell - as much as I remember anyway. I
just did a 2000 to 2005 upgrade for 8 production databases varying
from a few hundred megs to 50 gigs.This approach with a new server
allowed us to test and to hold cutting over until we were 100% sure
everything was working. There are may ways to do this, but this how I
did it....
We built and configured a new 2005 server first. Here is the overview
of the check list:
1. Build new server with network engineers.
2. Discuss best place to keep logfiles, databases, backups etc. Do
appropriate sizing etc.
3. Decide what new services to use and get them configured and
running. EX: We are not using analysis service.
4. Configure database mail.
5. Configure alerts and get backups going for system databases etc.
6. do a backup and restore from 2000 to 2005 and get the db backup and
log maintenence jobs going. I did weekly stats update and alter index
reorganize.
7. Created all windows, sql logins on the new box - we are mixed mode.
8. This allowed us to test the apps on the new server and permissions
etc. The schema's can be troublesome. I dropped all users after
restoring and then reapplied the permissions.
9.Here was my actual cutover checklist of things the SSIS package did
a. take down apps/or web server during cutover
b.backup 2000 databases to unc path
c.resotore databases to new 2005 box from unc path.
d.drop permissions (logins, schemas, roles, users)
e. re-assign permissions as required.
f.rebuild indexes
g.set database compatibility level (90) for 2005
h.re-point all applications to new SQL instance
i.run backup and maintenence jobs to make sure all working.
j.test and run other SSIS jobs
k.detach old 2005 databases but leave on the server for awhile in case
of issues.
Kristina
|||"Kristina" wrote:

> On May 18, 9:49 am, bing <b...@.discussions.microsoft.com> wrote:
> Here is my experience in a nutshell - as much as I remember anyway. I
> just did a 2000 to 2005 upgrade for 8 production databases varying
> from a few hundred megs to 50 gigs.This approach with a new server
> allowed us to test and to hold cutting over until we were 100% sure
> everything was working. There are may ways to do this, but this how I
> did it....
> We built and configured a new 2005 server first. Here is the overview
> of the check list:
> 1. Build new server with network engineers.
> 2. Discuss best place to keep logfiles, databases, backups etc. Do
> appropriate sizing etc.
> 3. Decide what new services to use and get them configured and
> running. EX: We are not using analysis service.
> 4. Configure database mail.
> 5. Configure alerts and get backups going for system databases etc.
> 6. do a backup and restore from 2000 to 2005 and get the db backup and
> log maintenence jobs going. I did weekly stats update and alter index
> reorganize.
> 7. Created all windows, sql logins on the new box - we are mixed mode.
> 8. This allowed us to test the apps on the new server and permissions
> etc. The schema's can be troublesome. I dropped all users after
> restoring and then reapplied the permissions.
> 9.Here was my actual cutover checklist of things the SSIS package did
> a. take down apps/or web server during cutover
> b.backup 2000 databases to unc path
> c.resotore databases to new 2005 box from unc path.
> d.drop permissions (logins, schemas, roles, users)
> e. re-assign permissions as required.
> f.rebuild indexes
> g.set database compatibility level (90) for 2005
> h.re-point all applications to new SQL instance
> i.run backup and maintenence jobs to make sure all working.
> j.test and run other SSIS jobs
> k.detach old 2005 databases but leave on the server for awhile in case
> of issues.
> Kristina
>
Excellent! Thanks much. We're in a similar situation. For the last step
k, I think you meant 'detach old 2000 databases', right?
Bing
|||On May 18, 11:11 am, bing <b...@.discussions.microsoft.com> wrote:
> "Kristina" wrote:
>
>
>
>
>
>
>
>
>
> Excellent! Thanks much. We're in a similar situation. For the last step
> k, I think you meant 'detach old 2000 databases', right?
> Bing- Hide quoted text -
> - Show quoted text -
yes, I am a poor writer.....it wasn't really that bad to do the
upgrade. I got the wrox press SQL 2005 Administration book and it
helped tons...
Good LUCK!
|||"Kristina" wrote:

> On May 18, 11:11 am, bing <b...@.discussions.microsoft.com> wrote:
> yes, I am a poor writer.....it wasn't really that bad to do the
> upgrade. I got the wrox press SQL 2005 Administration book and it
> helped tons...
> Good LUCK!
>
Glad to hear it isn't that bad. Thanks again, Kristina.
Bing