Hi All,
Recently I lost my job, which I had for 6 years, because someone accused me
that I destroyed critical data on a Microsoft SB2000 server.
The damage was done on the SQL server data, so the commercial application
was malfunctioning.
The guy who wrote the commercial application (ERP) said that has evidence
showing that the damage was done from me. My poor knowledge of MS SB2000 and
SQL server and the thread that if I refuse the category they will get me in
the court, I forced to accept the category and leave the company that I
worked for 6 years.
Now I have a new better job, but I try to fix again my name and my image of
the 25 year professional work in computer industry
In my trial to prove that I am innocent and I have not damage any data I
need any possible help for the following.
If I can get from any log or other kind of tracing
a -not editable - (read only) information, so I can used it as evidence
Any help is welcome
Evan K
You could try to read the transaction log, if it is still available to you.
From there, with an appropriate tool, you can see who did what. Check, for
example, Lumigent Log Explorer (http://www.lumigent.com/).
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> Hi All,
> Recently I lost my job, which I had for 6 years, because someone accused
me
> that I destroyed critical data on a Microsoft SB2000 server.
> The damage was done on the SQL server data, so the commercial application
> was malfunctioning.
> The guy who wrote the commercial application (ERP) said that has evidence
> showing that the damage was done from me. My poor knowledge of MS SB2000
and
> SQL server and the thread that if I refuse the category they will get me
in
> the court, I forced to accept the category and leave the company that I
> worked for 6 years.
> Now I have a new better job, but I try to fix again my name and my image
of
> the 25 year professional work in computer industry
> In my trial to prove that I am innocent and I have not damage any data I
> need any possible help for the following.
> If I can get from any log or other kind of tracing
> a -not editable - (read only) information, so I can used it as evidence
> Any help is welcome
> Evan K
|||"Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> Hi All,
> Recently I lost my job, which I had for 6 years, because someone accused
> me
> that I destroyed critical data on a Microsoft SB2000 server.
> The damage was done on the SQL server data, so the commercial application
> was malfunctioning.
> The guy who wrote the commercial application (ERP) said that has evidence
> showing that the damage was done from me. My poor knowledge of MS SB2000
> and
> SQL server and the thread that if I refuse the category they will get me
> in
> the court, I forced to accept the category and leave the company that I
> worked for 6 years.
I'm just surprised on how s/he manage to say that you're the culprit.
Anyway, below are just to share my experiences. Believe me, it was a very
painful and grueling process to identify how the server was hacked.
An external hacker hacked into our system, replace a compiled .dll file by
appending 'drop table x'. To cut a long story short, it was because of too
much rights given to one of the directory in the IIS (which has the compiled
VB stored procedure in .dll) because the so called developer just know how
to program ERP systems, but has very minimal knowledge in managing an IIS
server let alone an application server.
There are (many) software (search for vb decompiler) that is able to read
the compiled .dll and de-compile.
Since the hacker overwrite the DLL file with his/her version, the SQL
profiler shows that the command was issued via a valid connection, ie from
someone in the local Intranet. Meaning, everytime someone logs into the ERP
system, the command "drop table x" would be issued.
This can also be confirmed by installing Ethereal network packet analyzer to
analyze the packets in real time.
We got lucky and we manage to pinpoint some files being changed by the so
called hacker. After that discovery it was just a matter of how to prevent
people from writing to the IIS.
However, I'm not sure if the above can be of any use to you and good luck.
(Sorry for my bad english as it is not my first language)
> Now I have a new better job, but I try to fix again my name and my image
> of
> the 25 year professional work in computer industry
> In my trial to prove that I am innocent and I have not damage any data I
> need any possible help for the following.
> If I can get from any log or other kind of tracing
> a -not editable - (read only) information, so I can used it as evidence
> Any help is welcome
Steven Ung
|||Thanks A LOT
"Dejan Sarka" wrote:
> You could try to read the transaction log, if it is still available to you.
> From there, with an appropriate tool, you can see who did what. Check, for
> example, Lumigent Log Explorer (http://www.lumigent.com/).
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
> message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> me
> and
> in
> of
>
>
|||Thanks Steven
"Steven Ung" wrote:
> "Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
> message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> I'm just surprised on how s/he manage to say that you're the culprit.
> Anyway, below are just to share my experiences. Believe me, it was a very
> painful and grueling process to identify how the server was hacked.
> An external hacker hacked into our system, replace a compiled .dll file by
> appending 'drop table x'. To cut a long story short, it was because of too
> much rights given to one of the directory in the IIS (which has the compiled
> VB stored procedure in .dll) because the so called developer just know how
> to program ERP systems, but has very minimal knowledge in managing an IIS
> server let alone an application server.
> There are (many) software (search for vb decompiler) that is able to read
> the compiled .dll and de-compile.
> Since the hacker overwrite the DLL file with his/her version, the SQL
> profiler shows that the command was issued via a valid connection, ie from
> someone in the local Intranet. Meaning, everytime someone logs into the ERP
> system, the command "drop table x" would be issued.
> This can also be confirmed by installing Ethereal network packet analyzer to
> analyze the packets in real time.
> We got lucky and we manage to pinpoint some files being changed by the so
> called hacker. After that discovery it was just a matter of how to prevent
> people from writing to the IIS.
> However, I'm not sure if the above can be of any use to you and good luck.
> (Sorry for my bad english as it is not my first language)
>
> --
> Steven Ung
>
>
Showing posts with label job. Show all posts
Showing posts with label job. Show all posts
Friday, March 30, 2012
Receiving this error since migrating to SQL 2000 from SQL 7
Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
once a day while running jobs through SQL Agent. It may not be the same job
having the problem. Any thoughts?
Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 0 (0) Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server Help file:
Help context: 0. Process Exit Code 1. The step failed.Three simple suggestions:
1- Run the DTS package manually and see where (Which step)
you get the error.
2- Create an output file through Package-->Properties--
>Logging in the DTS package and read the output file for
the error.
3- If you upgraded from SQL Server 7.0 to 2000, run
sp_updatestats stored proc for all the databases in the QA.
>--Original Message--
>Ever since migrating to SQL 2000 from SQL 7 I receive
this error at least
>once a day while running jobs through SQL Agent. It may
not be the same job
>having the problem. Any thoughts?
>Executed as user: domain\user. DTSRun: Loading...
Error: -2147467259
>(80004005); Provider Error: 0 (0) Error string:
Timeout expired
>Error source: Microsoft OLE DB Provider for SQL
Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.
>.
>|||The job is only failing once or twice a day even though it runs every hour or
in the case of another job, every 1/2 hour. It is never the same time of
day. I can run the DTS job manually and it work without failing. I will
give the logging a try and the sp_updatestats. I didn't upgrade the server -
it was a clean install and a restore from SQL 7. Thanks for your help
"Mark" wrote:
> Three simple suggestions:
> 1- Run the DTS package manually and see where (Which step)
> you get the error.
> 2- Create an output file through Package-->Properties--
> >Logging in the DTS package and read the output file for
> the error.
> 3- If you upgraded from SQL Server 7.0 to 2000, run
> sp_updatestats stored proc for all the databases in the QA.
>
>
> >--Original Message--
> >Ever since migrating to SQL 2000 from SQL 7 I receive
> this error at least
> >once a day while running jobs through SQL Agent. It may
> not be the same job
> >having the problem. Any thoughts?
> >
> >Executed as user: domain\user. DTSRun: Loading...
> Error: -2147467259
> >(80004005); Provider Error: 0 (0) Error string:
> Timeout expired
> >Error source: Microsoft OLE DB Provider for SQL
> Server Help file:
> > Help context: 0. Process Exit Code 1. The step failed.
> >.
> >
>|||I have ran the jobs numerous times with DTS and they do not fail. I have run
the sp_updatestats on all databases on this server and I have turned on
logging with DTS and this job does not log anything when I get the timeout
message. Thanks for any other advice you can give. My customer is getting
very frustrated that this keeps not running.
"Connie" wrote:
> Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
> once a day while running jobs through SQL Agent. It may not be the same job
> having the problem. Any thoughts?
> Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
> (80004005); Provider Error: 0 (0) Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.sql
once a day while running jobs through SQL Agent. It may not be the same job
having the problem. Any thoughts?
Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 0 (0) Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server Help file:
Help context: 0. Process Exit Code 1. The step failed.Three simple suggestions:
1- Run the DTS package manually and see where (Which step)
you get the error.
2- Create an output file through Package-->Properties--
>Logging in the DTS package and read the output file for
the error.
3- If you upgraded from SQL Server 7.0 to 2000, run
sp_updatestats stored proc for all the databases in the QA.
>--Original Message--
>Ever since migrating to SQL 2000 from SQL 7 I receive
this error at least
>once a day while running jobs through SQL Agent. It may
not be the same job
>having the problem. Any thoughts?
>Executed as user: domain\user. DTSRun: Loading...
Error: -2147467259
>(80004005); Provider Error: 0 (0) Error string:
Timeout expired
>Error source: Microsoft OLE DB Provider for SQL
Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.
>.
>|||The job is only failing once or twice a day even though it runs every hour or
in the case of another job, every 1/2 hour. It is never the same time of
day. I can run the DTS job manually and it work without failing. I will
give the logging a try and the sp_updatestats. I didn't upgrade the server -
it was a clean install and a restore from SQL 7. Thanks for your help
"Mark" wrote:
> Three simple suggestions:
> 1- Run the DTS package manually and see where (Which step)
> you get the error.
> 2- Create an output file through Package-->Properties--
> >Logging in the DTS package and read the output file for
> the error.
> 3- If you upgraded from SQL Server 7.0 to 2000, run
> sp_updatestats stored proc for all the databases in the QA.
>
>
> >--Original Message--
> >Ever since migrating to SQL 2000 from SQL 7 I receive
> this error at least
> >once a day while running jobs through SQL Agent. It may
> not be the same job
> >having the problem. Any thoughts?
> >
> >Executed as user: domain\user. DTSRun: Loading...
> Error: -2147467259
> >(80004005); Provider Error: 0 (0) Error string:
> Timeout expired
> >Error source: Microsoft OLE DB Provider for SQL
> Server Help file:
> > Help context: 0. Process Exit Code 1. The step failed.
> >.
> >
>|||I have ran the jobs numerous times with DTS and they do not fail. I have run
the sp_updatestats on all databases on this server and I have turned on
logging with DTS and this job does not log anything when I get the timeout
message. Thanks for any other advice you can give. My customer is getting
very frustrated that this keeps not running.
"Connie" wrote:
> Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
> once a day while running jobs through SQL Agent. It may not be the same job
> having the problem. Any thoughts?
> Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
> (80004005); Provider Error: 0 (0) Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.sql
Friday, March 23, 2012
Rebuilding Indexes
I am trying to rebuild indexes on system tables by using a script that will be called from a batch job. Does anyone have any ideas of how to do this? I know DBCC DBREINDEX does not support use on sytem tables.What version of SQL?
I'm also wondering why you want to do this. I've never even thought about it. SQL 2000 is supposed to update this stuff automatically. Maybe I shouldn't AssUme? hmm.
I really can't find anything on the subject.|||Never ever play with system tables using DBCCs, even MS discourages and does not support to do so.
As referred why do you want screw up your system?
I'm also wondering why you want to do this. I've never even thought about it. SQL 2000 is supposed to update this stuff automatically. Maybe I shouldn't AssUme? hmm.
I really can't find anything on the subject.|||Never ever play with system tables using DBCCs, even MS discourages and does not support to do so.
As referred why do you want screw up your system?
Rebuilding Full Text Catalog
Hi,
I have created a db install app that will install all datatables,
build full-text catalogs and add job scheduler to populate the
catalogs several times a day.
However, I would also like my catalogs to be rebuilt every midnight
and repopulated again. I know of Rebuild method and Start method but
how do I schedule it so it is rebuilt every midnight?
Thank you,
_dino_
Why do you want to do a rebuild? A full population should suffice.
To schedule a rebuild you would schedule sp_fulltext_catalog
'catalogname','rebuild'
Have this job run in the database you are full-text indexing.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Dino Buljubasic" <dino@.noplacelikehome.com> wrote in message
news:929nf11uhqac6ajetilqje30crccvjqast@.4ax.com...
> Hi,
> I have created a db install app that will install all datatables,
> build full-text catalogs and add job scheduler to populate the
> catalogs several times a day.
> However, I would also like my catalogs to be rebuilt every midnight
> and repopulated again. I know of Rebuild method and Start method but
> how do I schedule it so it is rebuilt every midnight?
> Thank you,
> _dino_
I have created a db install app that will install all datatables,
build full-text catalogs and add job scheduler to populate the
catalogs several times a day.
However, I would also like my catalogs to be rebuilt every midnight
and repopulated again. I know of Rebuild method and Start method but
how do I schedule it so it is rebuilt every midnight?
Thank you,
_dino_
Why do you want to do a rebuild? A full population should suffice.
To schedule a rebuild you would schedule sp_fulltext_catalog
'catalogname','rebuild'
Have this job run in the database you are full-text indexing.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Dino Buljubasic" <dino@.noplacelikehome.com> wrote in message
news:929nf11uhqac6ajetilqje30crccvjqast@.4ax.com...
> Hi,
> I have created a db install app that will install all datatables,
> build full-text catalogs and add job scheduler to populate the
> catalogs several times a day.
> However, I would also like my catalogs to be rebuilt every midnight
> and repopulated again. I know of Rebuild method and Start method but
> how do I schedule it so it is rebuilt every midnight?
> Thank you,
> _dino_
Tuesday, March 20, 2012
Rebuild Index grew database .mdf files
Hello,
Overnight, I had a Rebuild Index job run and it grew the size of the database.mdf file approximately 4 times. 300MB to 1.2GB. It also changed the initial size of the database to 1.2GB. Is there any way to recover this space or to shrink the database?
I tried to shrink it with DBCC SHRINKDATABASE to no avail (only recovered 40MB).
Do I have any options to reclaim the space?
Any ideas?
Thanks.It turns out that the cause of the increase in size of database files was due to the fact that I had the Rebuild Index job set with a fill factor of 10%. I tested a bit and found that if I set it to reorganize pages with the default amount of free space that it didn't triple/quadruple/etc the size of the files.
Case Closed!
Subscribe to:
Posts (Atom)