A database file is demaged, no backup, anyway to fix it?

A database file (*.mdf) is demaged, no backup, anyway to fix it?
--frank, using sql2000
The only tool I know of is http://www.officerecovery.com/mssql/.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Frank Lee" <Reply@.to.newsgroup> wrote in message news:edAwrp6IGHA.208@.tk2msftngp13.phx.gbl...
>A database file (*.mdf) is demaged, no backup, anyway to fix it?
> --frank, using sql2000
>
|||If that doesn't work, you can put the database in emergency mode and then
use DBCC PAGE to manually extract data. Very slow, very time consuming, and
no guarantees. I've only had to do it once and it wasn't very pretty.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23CIeUI$IGHA.668@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> The only tool I know of is http://www.officerecovery.com/mssql/.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Frank Lee" <Reply@.to.newsgroup> wrote in message
> news:edAwrp6IGHA.208@.tk2msftngp13.phx.gbl...
sql

A database file is demaged, no backup, anyway to fix it?

A database file (*.mdf) is demaged, no backup, anyway to fix it?
--frank, using sql2000The only tool I know of is http://www.officerecovery.com/mssql/.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Frank Lee" <Reply@.to.newsgroup> wrote in message news:edAwrp6IGHA.208@.tk2msftngp13.phx.gbl...
>A database file (*.mdf) is demaged, no backup, anyway to fix it?
> --frank, using sql2000
>|||If that doesn't work, you can put the database in emergency mode and then
use DBCC PAGE to manually extract data. Very slow, very time consuming, and
no guarantees. I've only had to do it once and it wasn't very pretty.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23CIeUI$IGHA.668@.TK2MSFTNGP11.phx.gbl...
> The only tool I know of is http://www.officerecovery.com/mssql/.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Frank Lee" <Reply@.to.newsgroup> wrote in message
> news:edAwrp6IGHA.208@.tk2msftngp13.phx.gbl...
>>A database file (*.mdf) is demaged, no backup, anyway to fix it?
>> --frank, using sql2000

A database file is demaged, no backup, anyway to fix it?

A database file (*.mdf) is demaged, no backup, anyway to fix it?
--frank, using sql2000The only tool I know of is http://www.officerecovery.com/mssql/.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Frank Lee" <Reply@.to.newsgroup> wrote in message news:edAwrp6IGHA.208@.tk2msftngp13.phx.gbl.
.
>A database file (*.mdf) is demaged, no backup, anyway to fix it?
> --frank, using sql2000
>|||If that doesn't work, you can put the database in emergency mode and then
use DBCC PAGE to manually extract data. Very slow, very time consuming, and
no guarantees. I've only had to do it once and it wasn't very pretty.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23CIeUI$IGHA.668@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> The only tool I know of is http://www.officerecovery.com/mssql/.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Frank Lee" <Reply@.to.newsgroup> wrote in message
> news:edAwrp6IGHA.208@.tk2msftngp13.phx.gbl...

A connection was successfully established with the server, but then an error occurred during the

Hi All,

When i'm trying to access a sql server from a different pc,i'm getting the following error..

Plz help me how to fix this..

A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476

Server Name: 10.11.144.145
Error Number: 64
Severity: 20
State: 0

Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Regards,

Sailendra.

Hi ,

This problem generally occurs in windows 2003 server with service pack 1.

Solution is :-

Steps

<!--[if !supportLists]-->1. <!--[endif]-->regedit

<!--[if !supportLists]-->2. <!--[endif]-->HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\\Parameters

<!--[if !supportLists]-->3. <!--[endif]-->Add Dword value with name “SynAttackProtect” and set value “00000000 “in hexdecimal.

Regards
Rajesh

A connection was successfully established with the server, but then an error occurred during the

Hi All,

When i'm trying to access a sql server from a different pc,i'm getting the following error..

Plz help me how to fix this..

A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476

Server Name: 10.11.144.145
Error Number: 64
Severity: 20
State: 0

Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Regards,

Sailendra.

Hi ,

This problem generally occurs in windows 2003 server with service pack 1.

Solution is :-

Steps

<!--[if !supportLists]-->1. <!--[endif]-->regedit

<!--[if !supportLists]-->2. <!--[endif]-->HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\\Parameters

<!--[if !supportLists]-->3. <!--[endif]-->Add Dword value with name “SynAttackProtect” and set value “00000000 “in hexdecimal.

Regards
Rajeshsql

64bit and performance counters

Does anyone know if the hotfix mentioned in KB article 812915
[FIX: "Performance Monitor Shared Memory Setup Failed: -1" Error Message
When You Start SQL Server]
is the same for 64bit as for 32bit, my first guess is no - but I have to
ask.
We just installed 64bit SQL Server 2 weeks ago and now the performace
counters are gone and the above "-1" message shows up in the SQL Server
errolog. This looks exactly like the same problem we encountered with 32
bit.
Thanks,
FrankmHi Frankm,
From your descriptions, I understood that you would like to the fix in
KB:812915 will be possible for your performance counter issue. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know:)
Based on my knowledge, it will be suitable for your 64bit SQL Server as you
could find the following information in the KB
----
The information in this article applies to:
Microsoft SQL Server 2000 (all editions) SP3
----
You could contact PSS as KB told to ask for a hotfix :) If the hotfix
doesn't resolve your issue, your issue may be not share the same root cause
as fixed in KB: 812915. In this way, I will be glad to continue our
troubleshooting until it is resolved :)
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Are you sure that the Hotfix will work for 64bit?
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:YhgxzlmWEHA.3484@.cpmsftngxa10.phx.gbl...
> Hi Frankm,
> From your descriptions, I understood that you would like to the fix in
> KB:812915 will be possible for your performance counter issue. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know:)
> Based on my knowledge, it will be suitable for your 64bit SQL Server as
you
> could find the following information in the KB
> ----
> The information in this article applies to:
> Microsoft SQL Server 2000 (all editions) SP3
> ----
> You could contact PSS as KB told to ask for a hotfix :) If the hotfix
> doesn't resolve your issue, your issue may be not share the same root
cause
> as fixed in KB: 812915. In this way, I will be glad to continue our
> troubleshooting until it is resolved :)
>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi frankm,
I am sure that hotfix will work for 64bit SQL Server :)
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||Thank you - I will attempt to apply the patch.
Thank you again ...
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:XE7dHSYXEHA.308@.cpmsftngxa10.phx.gbl...
> Hi frankm,
> I am sure that hotfix will work for 64bit SQL Server :)
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi Frankm,
Thanks for your prompt updates!
You could post back the result after applying the patches to Re-Open this
thread if the patch doesn't work for you. In this case, you issue might be
another root causes that has no relationship with KB: 812915 and it is
highly appreciated if you could create a new thread so that we could
troubleshooting this issue for you :)
Anyway, thanks for using MSDN Newsgroup! We are here to be of assistance
whenever you have problems!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!