June 9, 2015 at 11:35 am
Sorry for the simple questions, just trying to understand the environment a little.
Is this the only instance of SQL Server on that machine? It seems a little weird that it is a production system but it is running SQL Server 2008 R2 RTM.
Have any patches/upgrades gone occurred on the instance recently?
Joie Andrew
"Since 1982"
June 9, 2015 at 11:56 am
Joie Andrew (6/9/2015)
Sorry for the simple questions, just trying to understand the environment a little.Is this the only instance of SQL Server on that machine? It seems a little weird that it is a production system but it is running SQL Server 2008 R2 RTM.
Have any patches/upgrades gone occurred on the instance recently?
Thanks Joie. I don't administrate this server. I only use it to storage the databases for a software I created. I required to install SQL Server on this machine and I get SQL 2008 Express. After some perfomance issues, the administrator install this versión of SQL Server 2008 R2. SQL Express service is disabled now, but both versions coexist now on this server. I don't exactly know what you mean about SQL Server 2008 R2 RTM for production. Is there a problema there?.
Do you think that this circunstance could be related to the data loss?
Thanks again for your interest
June 9, 2015 at 12:12 pm
I can't help but wonder if someone is trying to "reset the clock" to prevent the RTM version from expiring.
Have you discussed this problem with the server administrator?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
June 9, 2015 at 12:14 pm
Alvin Ramard (6/9/2015)
I can't help but wonder if someone is trying to "reset the clock" to prevent the RTM version from expiring.Have you discussed this problem with the server administrator?
No, server date and time are up to date.
June 9, 2015 at 12:19 pm
ericpap (6/9/2015)
Alvin Ramard (6/9/2015)
I can't help but wonder if someone is trying to "reset the clock" to prevent the RTM version from expiring.Have you discussed this problem with the server administrator?
No, server date and time are up to date.
It's not the server date/time I was thinking about. I was thing about the install date.
You haven't answered my second question. Have you discussed this problem with the server administrator?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
June 9, 2015 at 12:25 pm
Alvin Ramard (6/9/2015)
ericpap (6/9/2015)
Alvin Ramard (6/9/2015)
I can't help but wonder if someone is trying to "reset the clock" to prevent the RTM version from expiring.Have you discussed this problem with the server administrator?
No, server date and time are up to date.
It's not the server date/time I was thinking about. I was thing about the install date.
You haven't answered my second question. Have you discussed this problem with the server administrator?
Well is a complicated issue. There is no formal "server administrator" here. Just someone that install the service. Actually the server has serious security issues like all users belong to admin group....
June 9, 2015 at 12:30 pm
ericpap (6/9/2015)
Alvin Ramard (6/9/2015)
ericpap (6/9/2015)
Alvin Ramard (6/9/2015)
I can't help but wonder if someone is trying to "reset the clock" to prevent the RTM version from expiring.Have you discussed this problem with the server administrator?
No, server date and time are up to date.
It's not the server date/time I was thinking about. I was thing about the install date.
You haven't answered my second question. Have you discussed this problem with the server administrator?
Well is a complicated issue. There is no formal "server administrator" here. Just someone that install the service. Actually the server has serious security issues like all users belong to admin group....
Good luck.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
June 9, 2015 at 12:59 pm
ericpap (6/9/2015)
Alvin Ramard (6/9/2015)
ericpap (6/9/2015)
Alvin Ramard (6/9/2015)
I can't help but wonder if someone is trying to "reset the clock" to prevent the RTM version from expiring.Have you discussed this problem with the server administrator?
No, server date and time are up to date.
It's not the server date/time I was thinking about. I was thing about the install date.
You haven't answered my second question. Have you discussed this problem with the server administrator?
Well is a complicated issue. There is no formal "server administrator" here. Just someone that install the service. Actually the server has serious security issues like all users belong to admin group....
I'd say you'll have to ask those people with administrative access what happened. From the logs, it looks like someone took the mssql service offline, and once that happens, the .mdf and configuration can be modified with no auditing. Whatever organization this is, they really need to get their act together and stop treating the server likes it's their own personal sandbox.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
June 9, 2015 at 1:02 pm
ericpap (6/9/2015)
Alvin Ramard (6/9/2015)
ericpap (6/9/2015)
Alvin Ramard (6/9/2015)
I can't help but wonder if someone is trying to "reset the clock" to prevent the RTM version from expiring.Have you discussed this problem with the server administrator?
No, server date and time are up to date.
It's not the server date/time I was thinking about. I was thing about the install date.
You haven't answered my second question. Have you discussed this problem with the server administrator?
Well is a complicated issue. There is no formal "server administrator" here. Just someone that install the service. Actually the server has serious security issues like all users belong to admin group....
Oh, I worked in a place like that. I only made it 9 months.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 9, 2015 at 1:16 pm
Grant Fritchey (6/9/2015)
ericpap (6/9/2015)
Alvin Ramard (6/9/2015)
ericpap (6/9/2015)
Alvin Ramard (6/9/2015)
I can't help but wonder if someone is trying to "reset the clock" to prevent the RTM version from expiring.Have you discussed this problem with the server administrator?
No, server date and time are up to date.
It's not the server date/time I was thinking about. I was thing about the install date.
You haven't answered my second question. Have you discussed this problem with the server administrator?
Well is a complicated issue. There is no formal "server administrator" here. Just someone that install the service. Actually the server has serious security issues like all users belong to admin group....
Oh, I worked in a place like that. I only made it 9 months.
Funny, listening to all this reminds me of that guy from another discussion a couple weeks back who asked us to present a scientific argument why developers should not have sysadmin access to the database server. 😛
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
June 9, 2015 at 1:22 pm
Well is a complicated issue. There is no formal "server administrator" here. Just someone that install the service. Actually the server has serious security issues like all users belong to admin group....
So, basically there is almost no way to tell what has happened to this server then?... This does NOT sound like a good scenario. Since not only the db files seem different but the error logs as well it seems like SQL was possibly modified.
Not sure if this was covered already, but what about the Windows logs? Can you see if there are entries in the application log about any installs/uninstalls recently? Also can you see what the date of the latest SQL install is? Check C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Summary.txt and see what date is logged. It might tell you if there was an install recently.
Joie Andrew
"Since 1982"
June 9, 2015 at 1:25 pm
ericpap (6/9/2015)
Joie Andrew (6/9/2015)
Thank you for getting back with me on this.Another question, you say that you only have two logs available. If you look at the C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log directory do you not see the other ERRORLOG.X files? Those are straight text files and can be opened in Notepad if SQL Server cannot find them for some reason.
Yes. I have three files on log directory:
1) ErrorLog (this contains the log FROM 05/06/2015 11:55 till now)
2) ErrorLog.1 (Empty file, 0 bytes)
3) Log.trc (wich i don't know if it is helpfull)
And that's IT
There should be a lot more there. There should be at least 6 error log files by default and 5 log_nnnn.trc files (where nnnn is a large number)
Seriously starting to look like someone covering their tracks by deleting logs.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 9, 2015 at 1:39 pm
GilaMonster (6/9/2015)
ericpap (6/9/2015)
Joie Andrew (6/9/2015)
Thank you for getting back with me on this.Another question, you say that you only have two logs available. If you look at the C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log directory do you not see the other ERRORLOG.X files? Those are straight text files and can be opened in Notepad if SQL Server cannot find them for some reason.
Yes. I have three files on log directory:
1) ErrorLog (this contains the log FROM 05/06/2015 11:55 till now)
2) ErrorLog.1 (Empty file, 0 bytes)
3) Log.trc (wich i don't know if it is helpfull)
And that's IT
There should be a lot more there. There should be at least 6 error log files by default and 5 log_nnnn.trc files (where nnnn is a large number)
Seriously starting to look like someone covering their tracks by deleting logs.
Or, on second thoughts, like a freshly installed SQL Server.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 9, 2015 at 4:27 pm
GilaMonster (6/9/2015)
GilaMonster (6/9/2015)
ericpap (6/9/2015)
Joie Andrew (6/9/2015)
Thank you for getting back with me on this.Another question, you say that you only have two logs available. If you look at the C:\Archivos de programa\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log directory do you not see the other ERRORLOG.X files? Those are straight text files and can be opened in Notepad if SQL Server cannot find them for some reason.
Yes. I have three files on log directory:
1) ErrorLog (this contains the log FROM 05/06/2015 11:55 till now)
2) ErrorLog.1 (Empty file, 0 bytes)
3) Log.trc (wich i don't know if it is helpfull)
And that's IT
There should be a lot more there. There should be at least 6 error log files by default and 5 log_nnnn.trc files (where nnnn is a large number)
Seriously starting to look like someone covering their tracks by deleting logs.
Or, on second thoughts, like a freshly installed SQL Server.
Or someone restored the entire server from an old backup.
Whatever was done, I don't think you're likely to get to the bottom of it by looking at logs and such. I think it's time to take a stick to all & sundry until someone fesses up. The principal concern isn't even whatever horror they did to your system and your data (as bad as that is). The real horror is that they were able to do it and get away with it clean. Whatever happened, communication is hurting at your org and I'd start focusing there. From the sounds of things, I think you guys are just facing a loss on this data.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 10, 2015 at 12:45 am
ericpap (6/8/2015)
I'm facing a very complex situation with my software databases on a specific server. This is the second time this problem happend on this server. Basically while user where working on the system, with no apparently reason, all the data from three user databases where lost.The 3 databases where put on a previuos state from 1.5 month ago where all the databases changes made to this databases are lost, yes LOST! I had to restore a backup for all the databases but the data from passed two dates after the last backup where lost. The first time this happend, was with SQL Server Express 2008. Now happends on SQL Server 2008 R2 Standard.
I suspect a hardware / OS (Hard drive, RAM, etc) problem with the server itself, but no other data where lost (data files, etc) on SQL Server data.
The only lead i have to discover what happend is the Sql Server LOG, where i see some strange entrys:
1) All the log previous to 06/08/2015 11:55 (the exact moment where the problem apear) is lost.
2) An error during decryption, which don't know what it means.
3) A "Recovery complete" message
4) After that I see on the log constant message from CHECKDB over my users database (a lot of them) wich no one execute.
Does anyone have any idea of what could be hapenning here?
Is this a Hardware issue like I suspect?
Thanks!
Is this a Production Server?
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 15 posts - 31 through 45 (of 67 total)
You must be logged in to reply to this topic. Login to reply