How to trigger the update command of the SQLDataSource

Hi - I'm using .net2, and have a gridview, populated by a SQL Datasource (Edit, Insert, Delete, Select).

Like we all used to do with the datagrid, I've added text boxes into the footer, and a link button, which I'd like to use to fire the Update command.

How do I get the link button to trigger the update command?

Thanks, Mark

in you link button click event handler call

datasourceName.Update();

Hop this help

How to transfer data to another site and update data later on

I have a project that requires to send dataset that meet certain criteria
stored in SQL Server 7.0 in my office at L.A. to the parent company's SQL
Server 2000 at TX and then update parent's dataset that has been sent before
monthly for whatever changes that have been made over the time. Can somebody
teach me a way how to do it? As I don't know which record what data value has
been changed at our office over the time so as to update the dataset at TX's
SQL Server. It definitely will have changes. Also our SQL Server has limited
resource and the transmitted dataset will be about 400-500K records at the
first population.
Thank you in advance for your help.
Take a look at DTS if you want to try to automate the process.
If you would like to do it by hand, I would suggest that you use bcp to move
the data out to a flat file, WinZip the file and ship it. On the TX
system, bcp that new data into a staging table and then perform your
updates.
Note: Before performing your updates, you should probably back up the TX
database. That way if you really do something strange, you can quickly undo
it.
Rick Sawtell
MCT, MCSD, MCDBA
"Emily" <Emily@.discussions.microsoft.com> wrote in message
news:6CDB8949-4450-4F4E-9A07-F67950847298@.microsoft.com...
> I have a project that requires to send dataset that meet certain criteria
> stored in SQL Server 7.0 in my office at L.A. to the parent company's SQL
> Server 2000 at TX and then update parent's dataset that has been sent
before
> monthly for whatever changes that have been made over the time. Can
somebody
> teach me a way how to do it? As I don't know which record what data value
has
> been changed at our office over the time so as to update the dataset at
TX's
> SQL Server. It definitely will have changes. Also our SQL Server has
limited
> resource and the transmitted dataset will be about 400-500K records at the
> first population.
> Thank you in advance for your help.
|||Thanks for your help. But how can I tell which record has changes and
requires to do an update to the TX's database?
B.Regards,
Emily
"Rick Sawtell" wrote:

> Take a look at DTS if you want to try to automate the process.
> If you would like to do it by hand, I would suggest that you use bcp to move
> the data out to a flat file, WinZip the file and ship it. On the TX
> system, bcp that new data into a staging table and then perform your
> updates.
> Note: Before performing your updates, you should probably back up the TX
> database. That way if you really do something strange, you can quickly undo
> it.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Emily" <Emily@.discussions.microsoft.com> wrote in message
> news:6CDB8949-4450-4F4E-9A07-F67950847298@.microsoft.com...
> before
> somebody
> has
> TX's
> limited
>
>
|||Without looking at your table structures and how the data is handled, I
couldn't tell you.
How would you do it normally?
You could use a RowVersion datatype in the tables at both sites and then
compare them. For RowVersions that are different, you could perform your
updates on those rows.
HTH
Rick Sawtell
"Emily" <Emily@.discussions.microsoft.com> wrote in message
news:B40AE998-4ABF-4DC8-8954-4F0E938018C3@.microsoft.com...[vbcol=seagreen]
> Thanks for your help. But how can I tell which record has changes and
> requires to do an update to the TX's database?
> B.Regards,
> Emily
> "Rick Sawtell" wrote:
move[vbcol=seagreen]
TX[vbcol=seagreen]
undo[vbcol=seagreen]
criteria[vbcol=seagreen]
SQL[vbcol=seagreen]
value[vbcol=seagreen]
at[vbcol=seagreen]
the[vbcol=seagreen]
|||The recordset is pulled from different tables by joining the foreign keys
with the main table. None of them has a column with timestamp datatype( I
guess this is the datatype that you refer to as there is no RowVersion
datatype in SQL Server 7.0) .
Correct me if I'm wrong.
All tables that are used to get the recordset have a primary key in integer
datatype like an autonumber but not include in the recordset.
Does it mean we should add an additional column to trigger if there is any
change?
Thank you very much for your help.
Emily
"Rick Sawtell" wrote:

> Without looking at your table structures and how the data is handled, I
> couldn't tell you.
> How would you do it normally?
> You could use a RowVersion datatype in the tables at both sites and then
> compare them. For RowVersions that are different, you could perform your
> updates on those rows.
> HTH
> Rick Sawtell
>
> "Emily" <Emily@.discussions.microsoft.com> wrote in message
> news:B40AE998-4ABF-4DC8-8954-4F0E938018C3@.microsoft.com...
> move
> TX
> undo
> criteria
> SQL
> value
> at
> the
>
>

How to transfer data to another site and update data later on

I have a project that requires to send dataset that meet certain criteria
stored in SQL Server 7.0 in my office at L.A. to the parent company's SQL
Server 2000 at TX and then update parent's dataset that has been sent before
monthly for whatever changes that have been made over the time. Can somebody
teach me a way how to do it? As I don't know which record what data value has
been changed at our office over the time so as to update the dataset at TX's
SQL Server. It definitely will have changes. Also our SQL Server has limited
resource and the transmitted dataset will be about 400-500K records at the
first population.
Thank you in advance for your help.Take a look at DTS if you want to try to automate the process.
If you would like to do it by hand, I would suggest that you use bcp to move
the data out to a flat file, WinZip the file and ship it. On the TX
system, bcp that new data into a staging table and then perform your
updates.
Note: Before performing your updates, you should probably back up the TX
database. That way if you really do something strange, you can quickly undo
it.
Rick Sawtell
MCT, MCSD, MCDBA
"Emily" <Emily@.discussions.microsoft.com> wrote in message
news:6CDB8949-4450-4F4E-9A07-F67950847298@.microsoft.com...
> I have a project that requires to send dataset that meet certain criteria
> stored in SQL Server 7.0 in my office at L.A. to the parent company's SQL
> Server 2000 at TX and then update parent's dataset that has been sent
before
> monthly for whatever changes that have been made over the time. Can
somebody
> teach me a way how to do it? As I don't know which record what data value
has
> been changed at our office over the time so as to update the dataset at
TX's
> SQL Server. It definitely will have changes. Also our SQL Server has
limited
> resource and the transmitted dataset will be about 400-500K records at the
> first population.
> Thank you in advance for your help.|||Thanks for your help. But how can I tell which record has changes and
requires to do an update to the TX's database?
B.Regards,
Emily
"Rick Sawtell" wrote:
> Take a look at DTS if you want to try to automate the process.
> If you would like to do it by hand, I would suggest that you use bcp to move
> the data out to a flat file, WinZip the file and ship it. On the TX
> system, bcp that new data into a staging table and then perform your
> updates.
> Note: Before performing your updates, you should probably back up the TX
> database. That way if you really do something strange, you can quickly undo
> it.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Emily" <Emily@.discussions.microsoft.com> wrote in message
> news:6CDB8949-4450-4F4E-9A07-F67950847298@.microsoft.com...
> > I have a project that requires to send dataset that meet certain criteria
> > stored in SQL Server 7.0 in my office at L.A. to the parent company's SQL
> > Server 2000 at TX and then update parent's dataset that has been sent
> before
> > monthly for whatever changes that have been made over the time. Can
> somebody
> > teach me a way how to do it? As I don't know which record what data value
> has
> > been changed at our office over the time so as to update the dataset at
> TX's
> > SQL Server. It definitely will have changes. Also our SQL Server has
> limited
> > resource and the transmitted dataset will be about 400-500K records at the
> > first population.
> >
> > Thank you in advance for your help.
>
>|||Without looking at your table structures and how the data is handled, I
couldn't tell you.
How would you do it normally?
You could use a RowVersion datatype in the tables at both sites and then
compare them. For RowVersions that are different, you could perform your
updates on those rows.
HTH
Rick Sawtell
"Emily" <Emily@.discussions.microsoft.com> wrote in message
news:B40AE998-4ABF-4DC8-8954-4F0E938018C3@.microsoft.com...
> Thanks for your help. But how can I tell which record has changes and
> requires to do an update to the TX's database?
> B.Regards,
> Emily
> "Rick Sawtell" wrote:
> > Take a look at DTS if you want to try to automate the process.
> >
> > If you would like to do it by hand, I would suggest that you use bcp to
move
> > the data out to a flat file, WinZip the file and ship it. On the TX
> > system, bcp that new data into a staging table and then perform your
> > updates.
> >
> > Note: Before performing your updates, you should probably back up the
TX
> > database. That way if you really do something strange, you can quickly
undo
> > it.
> >
> > Rick Sawtell
> > MCT, MCSD, MCDBA
> >
> >
> > "Emily" <Emily@.discussions.microsoft.com> wrote in message
> > news:6CDB8949-4450-4F4E-9A07-F67950847298@.microsoft.com...
> > > I have a project that requires to send dataset that meet certain
criteria
> > > stored in SQL Server 7.0 in my office at L.A. to the parent company's
SQL
> > > Server 2000 at TX and then update parent's dataset that has been sent
> > before
> > > monthly for whatever changes that have been made over the time. Can
> > somebody
> > > teach me a way how to do it? As I don't know which record what data
value
> > has
> > > been changed at our office over the time so as to update the dataset
at
> > TX's
> > > SQL Server. It definitely will have changes. Also our SQL Server has
> > limited
> > > resource and the transmitted dataset will be about 400-500K records at
the
> > > first population.
> > >
> > > Thank you in advance for your help.
> >
> >
> >|||The recordset is pulled from different tables by joining the foreign keys
with the main table. None of them has a column with timestamp datatype( I
guess this is the datatype that you refer to as there is no RowVersion
datatype in SQL Server 7.0) .
Correct me if I'm wrong.
All tables that are used to get the recordset have a primary key in integer
datatype like an autonumber but not include in the recordset.
Does it mean we should add an additional column to trigger if there is any
change?
Thank you very much for your help.
Emily
"Rick Sawtell" wrote:
> Without looking at your table structures and how the data is handled, I
> couldn't tell you.
> How would you do it normally?
> You could use a RowVersion datatype in the tables at both sites and then
> compare them. For RowVersions that are different, you could perform your
> updates on those rows.
> HTH
> Rick Sawtell
>
> "Emily" <Emily@.discussions.microsoft.com> wrote in message
> news:B40AE998-4ABF-4DC8-8954-4F0E938018C3@.microsoft.com...
> > Thanks for your help. But how can I tell which record has changes and
> > requires to do an update to the TX's database?
> >
> > B.Regards,
> > Emily
> >
> > "Rick Sawtell" wrote:
> >
> > > Take a look at DTS if you want to try to automate the process.
> > >
> > > If you would like to do it by hand, I would suggest that you use bcp to
> move
> > > the data out to a flat file, WinZip the file and ship it. On the TX
> > > system, bcp that new data into a staging table and then perform your
> > > updates.
> > >
> > > Note: Before performing your updates, you should probably back up the
> TX
> > > database. That way if you really do something strange, you can quickly
> undo
> > > it.
> > >
> > > Rick Sawtell
> > > MCT, MCSD, MCDBA
> > >
> > >
> > > "Emily" <Emily@.discussions.microsoft.com> wrote in message
> > > news:6CDB8949-4450-4F4E-9A07-F67950847298@.microsoft.com...
> > > > I have a project that requires to send dataset that meet certain
> criteria
> > > > stored in SQL Server 7.0 in my office at L.A. to the parent company's
> SQL
> > > > Server 2000 at TX and then update parent's dataset that has been sent
> > > before
> > > > monthly for whatever changes that have been made over the time. Can
> > > somebody
> > > > teach me a way how to do it? As I don't know which record what data
> value
> > > has
> > > > been changed at our office over the time so as to update the dataset
> at
> > > TX's
> > > > SQL Server. It definitely will have changes. Also our SQL Server has
> > > limited
> > > > resource and the transmitted dataset will be about 400-500K records at
> the
> > > > first population.
> > > >
> > > > Thank you in advance for your help.
> > >
> > >
> > >
>
>

How to transfer data to another site and update data later on

I have a project that requires to send dataset that meet certain criteria
stored in SQL Server 7.0 in my office at L.A. to the parent company's SQL
Server 2000 at TX and then update parent's dataset that has been sent before
monthly for whatever changes that have been made over the time. Can somebody
teach me a way how to do it? As I don't know which record what data value ha
s
been changed at our office over the time so as to update the dataset at TX's
SQL Server. It definitely will have changes. Also our SQL Server has limited
resource and the transmitted dataset will be about 400-500K records at the
first population.
Thank you in advance for your help.Take a look at DTS if you want to try to automate the process.
If you would like to do it by hand, I would suggest that you use bcp to move
the data out to a flat file, WinZip the file and ship it. On the TX
system, bcp that new data into a staging table and then perform your
updates.
Note: Before performing your updates, you should probably back up the TX
database. That way if you really do something strange, you can quickly undo
it.
Rick Sawtell
MCT, MCSD, MCDBA
"Emily" <Emily@.discussions.microsoft.com> wrote in message
news:6CDB8949-4450-4F4E-9A07-F67950847298@.microsoft.com...
> I have a project that requires to send dataset that meet certain criteria
> stored in SQL Server 7.0 in my office at L.A. to the parent company's SQL
> Server 2000 at TX and then update parent's dataset that has been sent
before
> monthly for whatever changes that have been made over the time. Can
somebody
> teach me a way how to do it? As I don't know which record what data value
has
> been changed at our office over the time so as to update the dataset at
TX's
> SQL Server. It definitely will have changes. Also our SQL Server has
limited
> resource and the transmitted dataset will be about 400-500K records at the
> first population.
> Thank you in advance for your help.|||Thanks for your help. But how can I tell which record has changes and
requires to do an update to the TX's database?
B.Regards,
Emily
"Rick Sawtell" wrote:

> Take a look at DTS if you want to try to automate the process.
> If you would like to do it by hand, I would suggest that you use bcp to mo
ve
> the data out to a flat file, WinZip the file and ship it. On the TX
> system, bcp that new data into a staging table and then perform your
> updates.
> Note: Before performing your updates, you should probably back up the TX
> database. That way if you really do something strange, you can quickly un
do
> it.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Emily" <Emily@.discussions.microsoft.com> wrote in message
> news:6CDB8949-4450-4F4E-9A07-F67950847298@.microsoft.com...
> before
> somebody
> has
> TX's
> limited
>
>|||Without looking at your table structures and how the data is handled, I
couldn't tell you.
How would you do it normally?
You could use a RowVersion datatype in the tables at both sites and then
compare them. For RowVersions that are different, you could perform your
updates on those rows.
HTH
Rick Sawtell
"Emily" <Emily@.discussions.microsoft.com> wrote in message
news:B40AE998-4ABF-4DC8-8954-4F0E938018C3@.microsoft.com...[vbcol=seagreen]
> Thanks for your help. But how can I tell which record has changes and
> requires to do an update to the TX's database?
> B.Regards,
> Emily
> "Rick Sawtell" wrote:
>
move[vbcol=seagreen]
TX[vbcol=seagreen]
undo[vbcol=seagreen]
criteria[vbcol=seagreen]
SQL[vbcol=seagreen]
value[vbcol=seagreen]
at[vbcol=seagreen]
the[vbcol=seagreen]|||The recordset is pulled from different tables by joining the foreign keys
with the main table. None of them has a column with timestamp datatype( I
guess this is the datatype that you refer to as there is no RowVersion
datatype in SQL Server 7.0) .
Correct me if I'm wrong.
All tables that are used to get the recordset have a primary key in integer
datatype like an autonumber but not include in the recordset.
Does it mean we should add an additional column to trigger if there is any
change?
Thank you very much for your help.
Emily
"Rick Sawtell" wrote:

> Without looking at your table structures and how the data is handled, I
> couldn't tell you.
> How would you do it normally?
> You could use a RowVersion datatype in the tables at both sites and then
> compare them. For RowVersions that are different, you could perform your
> updates on those rows.
> HTH
> Rick Sawtell
>
> "Emily" <Emily@.discussions.microsoft.com> wrote in message
> news:B40AE998-4ABF-4DC8-8954-4F0E938018C3@.microsoft.com...
> move
> TX
> undo
> criteria
> SQL
> value
> at
> the
>
>

How to transactionally update a DB Schema?

I am trying to build a database schema updater (in C#) that can be used to
upgrade the various databases associated with my company's productized and
custom applications.
I've come up with what I think is an effective way of storing, specifying,
and executing the required T-SQL scripts to change the database from one
schema version to a new one, but I am having trouble reconciling how to deal
with potential errors while upgrading.
Is there a way to transactionally perform various "CREATE/ALTER
TABLE/PROCEDURE/TRIGGER/VIEW" and "INSERT/UPDATE/DELETE" statements so that
if one fails that I can rollback to before the upgrade started? If SQL
Server doesn't provide this functionality, what would be a "best practice"
to handle these types of errors?
Thanks,
Matthew Belk
BizSpeed, Inc.
You can execute DDL as part of an explicit transaction so that you can
rollback in the case of an error. However , I personally would backup the
database prior the upgrade and restore if an error is encountered.
Hope this helps.
Dan Guzman
SQL Server MVP
"Matthew Belk" <mbelk@.bizspeed.com> wrote in message
news:uqNW53WHEHA.3564@.TK2MSFTNGP09.phx.gbl...
> I am trying to build a database schema updater (in C#) that can be used to
> upgrade the various databases associated with my company's productized and
> custom applications.
> I've come up with what I think is an effective way of storing, specifying,
> and executing the required T-SQL scripts to change the database from one
> schema version to a new one, but I am having trouble reconciling how to
deal
> with potential errors while upgrading.
> Is there a way to transactionally perform various "CREATE/ALTER
> TABLE/PROCEDURE/TRIGGER/VIEW" and "INSERT/UPDATE/DELETE" statements so
that
> if one fails that I can rollback to before the upgrade started? If SQL
> Server doesn't provide this functionality, what would be a "best practice"
> to handle these types of errors?
> Thanks,
> Matthew Belk
> BizSpeed, Inc.
>
|||I'm doing that, too, if something catastrophic were to happen, but in the
case of upgrading through multiple versions, I would like to commit the
transaction for each version as I successfully run all the scripts for that
version.
Thanks,
Matthew
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:ezC50FXHEHA.4088@.TK2MSFTNGP10.phx.gbl...
> You can execute DDL as part of an explicit transaction so that you can
> rollback in the case of an error. However , I personally would backup the
> database prior the upgrade and restore if an error is encountered.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Matthew Belk" <mbelk@.bizspeed.com> wrote in message
> news:uqNW53WHEHA.3564@.TK2MSFTNGP09.phx.gbl...
to
and
specifying,
> deal
> that
practice"
>
sql

How to transactionally update a DB Schema?

I am trying to build a database schema updater (in C#) that can be used to
upgrade the various databases associated with my company's productized and
custom applications.
I've come up with what I think is an effective way of storing, specifying,
and executing the required T-SQL scripts to change the database from one
schema version to a new one, but I am having trouble reconciling how to deal
with potential errors while upgrading.
Is there a way to transactionally perform various "CREATE/ALTER
TABLE/PROCEDURE/TRIGGER/VIEW" and "INSERT/UPDATE/DELETE" statements so that
if one fails that I can rollback to before the upgrade started? If SQL
Server doesn't provide this functionality, what would be a "best practice"
to handle these types of errors?
Thanks,
Matthew Belk
BizSpeed, Inc.You can execute DDL as part of an explicit transaction so that you can
rollback in the case of an error. However , I personally would backup the
database prior the upgrade and restore if an error is encountered.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Matthew Belk" <mbelk@.bizspeed.com> wrote in message
news:uqNW53WHEHA.3564@.TK2MSFTNGP09.phx.gbl...
> I am trying to build a database schema updater (in C#) that can be used to
> upgrade the various databases associated with my company's productized and
> custom applications.
> I've come up with what I think is an effective way of storing, specifying,
> and executing the required T-SQL scripts to change the database from one
> schema version to a new one, but I am having trouble reconciling how to
deal
> with potential errors while upgrading.
> Is there a way to transactionally perform various "CREATE/ALTER
> TABLE/PROCEDURE/TRIGGER/VIEW" and "INSERT/UPDATE/DELETE" statements so
that
> if one fails that I can rollback to before the upgrade started? If SQL
> Server doesn't provide this functionality, what would be a "best practice"
> to handle these types of errors?
> Thanks,
> Matthew Belk
> BizSpeed, Inc.
>|||I'm doing that, too, if something catastrophic were to happen, but in the
case of upgrading through multiple versions, I would like to commit the
transaction for each version as I successfully run all the scripts for that
version.
Thanks,
Matthew
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:ezC50FXHEHA.4088@.TK2MSFTNGP10.phx.gbl...
> You can execute DDL as part of an explicit transaction so that you can
> rollback in the case of an error. However , I personally would backup the
> database prior the upgrade and restore if an error is encountered.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Matthew Belk" <mbelk@.bizspeed.com> wrote in message
> news:uqNW53WHEHA.3564@.TK2MSFTNGP09.phx.gbl...
> > I am trying to build a database schema updater (in C#) that can be used
to
> > upgrade the various databases associated with my company's productized
and
> > custom applications.
> >
> > I've come up with what I think is an effective way of storing,
specifying,
> > and executing the required T-SQL scripts to change the database from one
> > schema version to a new one, but I am having trouble reconciling how to
> deal
> > with potential errors while upgrading.
> >
> > Is there a way to transactionally perform various "CREATE/ALTER
> > TABLE/PROCEDURE/TRIGGER/VIEW" and "INSERT/UPDATE/DELETE" statements so
> that
> > if one fails that I can rollback to before the upgrade started? If SQL
> > Server doesn't provide this functionality, what would be a "best
practice"
> > to handle these types of errors?
> >
> > Thanks,
> > Matthew Belk
> > BizSpeed, Inc.
> >
> >
>

How to transactionally update a DB Schema?

I am trying to build a database schema updater (in C#) that can be used to
upgrade the various databases associated with my company's productized and
custom applications.
I've come up with what I think is an effective way of storing, specifying,
and executing the required T-SQL scripts to change the database from one
schema version to a new one, but I am having trouble reconciling how to deal
with potential errors while upgrading.
Is there a way to transactionally perform various "CREATE/ALTER
TABLE/PROCEDURE/TRIGGER/VIEW" and "INSERT/UPDATE/DELETE" statements so that
if one fails that I can rollback to before the upgrade started? If SQL
Server doesn't provide this functionality, what would be a "best practice"
to handle these types of errors?
Thanks,
Matthew Belk
BizSpeed, Inc.You can execute DDL as part of an explicit transaction so that you can
rollback in the case of an error. However , I personally would backup the
database prior the upgrade and restore if an error is encountered.
Hope this helps.
Dan Guzman
SQL Server MVP
"Matthew Belk" <mbelk@.bizspeed.com> wrote in message
news:uqNW53WHEHA.3564@.TK2MSFTNGP09.phx.gbl...
> I am trying to build a database schema updater (in C#) that can be used to
> upgrade the various databases associated with my company's productized and
> custom applications.
> I've come up with what I think is an effective way of storing, specifying,
> and executing the required T-SQL scripts to change the database from one
> schema version to a new one, but I am having trouble reconciling how to
deal
> with potential errors while upgrading.
> Is there a way to transactionally perform various "CREATE/ALTER
> TABLE/PROCEDURE/TRIGGER/VIEW" and "INSERT/UPDATE/DELETE" statements so
that
> if one fails that I can rollback to before the upgrade started? If SQL
> Server doesn't provide this functionality, what would be a "best practice"
> to handle these types of errors?
> Thanks,
> Matthew Belk
> BizSpeed, Inc.
>|||I'm doing that, too, if something catastrophic were to happen, but in the
case of upgrading through multiple versions, I would like to commit the
transaction for each version as I successfully run all the scripts for that
version.
Thanks,
Matthew
"Dan Guzman" <danguzman@.nospam-earthlink.net> wrote in message
news:ezC50FXHEHA.4088@.TK2MSFTNGP10.phx.gbl...
> You can execute DDL as part of an explicit transaction so that you can
> rollback in the case of an error. However , I personally would backup the
> database prior the upgrade and restore if an error is encountered.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Matthew Belk" <mbelk@.bizspeed.com> wrote in message
> news:uqNW53WHEHA.3564@.TK2MSFTNGP09.phx.gbl...
to
and
specifying,
> deal
> that
practice"
>

how to trace table update?

Hi,
I know using sql profiler can trace table update, can
someone teach me how to do so? Thanks
regards,
florenceYou need to start SQL Profiler and then create a connection to your server.
Then, create a new trace and accept all defaults. This should help you trace
the statements that go to SQL Server. If you need to do more esoteric
things, refer to the BOL for more information.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"florence" <florence@.visualsolutions.com.my> wrote in message
news:0d0701c3a918$23033d70$a301280a@.phx.gbl...
> Hi,
> I know using sql profiler can trace table update, can
> someone teach me how to do so? Thanks
> regards,
> florence

how to tell when a database was lasted accessed by general users?

Hi,
In the Subject, by general users, I meant those users who did regular
database operations, like insert, update, delete, etc. rather than the users
who have special privileges to do database maintenance operations, like
backup. We need to clean up those databases that haven't been accessed for
quite a while. Right now, we back up all the databases.
Thanks in advance,
BingHi
AFAIK there is not an easy way without either prolonged profiling or
possibly enabling C2 auditing. Alternatively products like auditdb from
Lumigent http://www.lumigent.com/products/auditdb.html would be able to tell
you, and log readers like their log explorer
http://www.lumigent.com/products/le_sql.html would be show updates.
A maverick approach may be to make the database readonly and see who squeals
!!
John
"bing" wrote:

> Hi,
> In the Subject, by general users, I meant those users who did regular
> database operations, like insert, update, delete, etc. rather than the use
rs
> who have special privileges to do database maintenance operations, like
> backup. We need to clean up those databases that haven't been accessed fo
r
> quite a while. Right now, we back up all the databases.
> Thanks in advance,
> Bing

how to tell when a database was lasted accessed by general users?

Hi,
In the Subject, by general users, I meant those users who did regular
database operations, like insert, update, delete, etc. rather than the users
who have special privileges to do database maintenance operations, like
backup. We need to clean up those databases that haven't been accessed for
quite a while. Right now, we back up all the databases.
Thanks in advance,
Bing
Hi
AFAIK there is not an easy way without either prolonged profiling or
possibly enabling C2 auditing. Alternatively products like auditdb from
Lumigent http://www.lumigent.com/products/auditdb.html would be able to tell
you, and log readers like their log explorer
http://www.lumigent.com/products/le_sql.html would be show updates.
A maverick approach may be to make the database readonly and see who squeals!!
John
"bing" wrote:

> Hi,
> In the Subject, by general users, I meant those users who did regular
> database operations, like insert, update, delete, etc. rather than the users
> who have special privileges to do database maintenance operations, like
> backup. We need to clean up those databases that haven't been accessed for
> quite a while. Right now, we back up all the databases.
> Thanks in advance,
> Bing
sql

how to tell when a database was lasted accessed by general users?

Hi,
In the Subject, by general users, I meant those users who did regular
database operations, like insert, update, delete, etc. rather than the users
who have special privileges to do database maintenance operations, like
backup. We need to clean up those databases that haven't been accessed for
quite a while. Right now, we back up all the databases.
Thanks in advance,
BingHi
AFAIK there is not an easy way without either prolonged profiling or
possibly enabling C2 auditing. Alternatively products like auditdb from
Lumigent http://www.lumigent.com/products/auditdb.html would be able to tell
you, and log readers like their log explorer
http://www.lumigent.com/products/le_sql.html would be show updates.
A maverick approach may be to make the database readonly and see who squeals!!
John
"bing" wrote:
> Hi,
> In the Subject, by general users, I meant those users who did regular
> database operations, like insert, update, delete, etc. rather than the users
> who have special privileges to do database maintenance operations, like
> backup. We need to clean up those databases that haven't been accessed for
> quite a while. Right now, we back up all the databases.
> Thanks in advance,
> Bing