Best way to copy database: failed

Showing posts with label failed. Show all posts

Sunday, March 25, 2012

Bind failed on TCP port 1433

Dolph
"Mark Allison" wrote:

> I didn't finish. :-/
> If you still cannot find the cause of the problem, I suggest that you
> reboot the server.
> In the case of 1) the solution is to put a small pause in your code
> before starting the MSSQLServer service again.
> In the case of 2) you will need to ensure that your application uses
> another port - perhaps there is a setting somewhere (maybe the registry)
> where you can tweak this.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Mark Allison wrote:
>
|||Dolph Larson wrote:
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
For the benefit of any other poor ***s trying to work this one out,
here's what I just found...
We got the "SuperSocket Info: Bind failed on TCP port 1433" error, yet
netstat says the socket _is_ listening. TCPView (from the excellent
sysinternals site) confirms that it's listening, and that it's SQL
server that doing it.
Stumped despite much googling, I suddenly realised we'd recently
installed a new remote access _client_ on this server, Windows Secure
Application Manager from netscreen. This seems to work by hooking the
TCP stack with an LSP. Needless to say, it was this that was messing
up SQL server - using the diagnostics tool to remove the LSP sorted it
out straight away.
Thinking back, I've seen problems with an LSP before: some weird
problem with Norton Antivirus left a machine in a state where ipconfig
said it was dialled up OK, it could ping, but it couldn't do email or
http... Zapping the LSP sorted it (not that I can remember how I
removed it!)
Cheers,
Martin.

Bind failed on TCP port 1433

Dolph
"Mark Allison" wrote:

> I didn't finish. :-/
> If you still cannot find the cause of the problem, I suggest that you
> reboot the server.
> In the case of 1) the solution is to put a small pause in your code
> before starting the MSSQLServer service again.
> In the case of 2) you will need to ensure that your application uses
> another port - perhaps there is a setting somewhere (maybe the registry)
> where you can tweak this.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Mark Allison wrote:
>|||Dolph Larson wrote:
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
For the benefit of any other poor ***s trying to work this one out,
here's what I just found...
We got the "SuperSocket Info: Bind failed on TCP port 1433" error, yet
netstat says the socket _is_ listening. TCPView (from the excellent
sysinternals site) confirms that it's listening, and that it's SQL
server that doing it.
Stumped despite much googling, I suddenly realised we'd recently
installed a new remote access _client_ on this server, Windows Secure
Application Manager from netscreen. This seems to work by hooking the
TCP stack with an LSP. Needless to say, it was this that was messing
up SQL server - using the diagnostics tool to remove the LSP sorted it
out straight away.
Thinking back, I've seen problems with an LSP before: some weird
problem with Norton Antivirus left a machine in a state where ipconfig
said it was dialled up OK, it could ping, but it couldn't do email or
http... Zapping the LSP sorted it (not that I can remember how I
removed it!)
Cheers,
Martin.

Bind failed on TCP port 1433

I installed SP3a and now I am getting this error message in the application
event log. Also, I can only connect to my server using namepipes. But
TCP/IP won't connect, even using 127.0.0.1 or the IP of my machine. The
event logs says that SQL is listening on 127.0.0.1:1433.
Can someone please help. I have not seen the answer and I have been
searching for 2 days now.
Log:
SQL server listening on 127.0.0.1: 1433.
SuperSocket Info: Bind failed on TCP port 1433.
SuperSocket info: (SpnRegister) : Error 1355.
Thanks in advance!Dolph,
There are two scenarios that I can think of that will cause this situation.
1) You have bounced the SQL Server service programmatically (probably in
C++) and the service has been stopped and restarted too quickly. SQL
Server does not release the port quickly enough before it is restarted
and thinks that another service is using port 1433. The bind, then fails.
2) Another application is using port 1433.
You can check your ports using this on the commandline:
netstat -a
Look at the local address column for <machinename>:ms-sql-s or
<machinename>:1433
On my Inspiron laptop I get these results:
Active Connections
Proto Local Address Foreign Address State
TCP inspiron4100:ftp inspiron4100:0 LISTENING
TCP inspiron4100:http inspiron4100:0 LISTENING
TCP inspiron4100:epmap inspiron4100:0 LISTENING
TCP inspiron4100:https inspiron4100:0 LISTENING
TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
TCP inspiron4100:1025 inspiron4100:0 LISTENING
TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
TCP inspiron4100:2869 inspiron4100:0 LISTENING
TCP inspiron4100:3389 inspiron4100:0 LISTENING
TCP inspiron4100:1028 inspiron4100:0 LISTENING
TCP inspiron4100:1061 inspiron4100:0 LISTENING
TCP inspiron4100:1134 localhost:1135 ESTABLISHED
TCP inspiron4100:1135 localhost:1134 ESTABLISHED
TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863
ESTABLISHED
TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
UDP inspiron4100:microsoft-ds *:*
UDP inspiron4100:isakmp *:*
UDP inspiron4100:1026 *:*
UDP inspiron4100:1069 *:*
UDP inspiron4100:1070 *:*
UDP inspiron4100:1131 *:*
UDP inspiron4100:ms-sql-m *:*
UDP inspiron4100:3456 *:*
UDP inspiron4100:4500 *:*
UDP inspiron4100:ntp *:*
UDP inspiron4100:1050 *:*
UDP inspiron4100:1057 *:*
UDP inspiron4100:1156 *:*
UDP inspiron4100:1900 *:*
UDP inspiron4100:ntp *:*
UDP inspiron4100:netbios-ns *:*
UDP inspiron4100:netbios-dgm *:*
UDP inspiron4100:1900 *:*
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Dolph Larson wrote:
> I installed SP3a and now I am getting this error message in the application
> event log. Also, I can only connect to my server using namepipes. But
> TCP/IP won't connect, even using 127.0.0.1 or the IP of my machine. The
> event logs says that SQL is listening on 127.0.0.1:1433.
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
> Log:
> SQL server listening on 127.0.0.1: 1433.
> SuperSocket Info: Bind failed on TCP port 1433.
> SuperSocket info: (SpnRegister) : Error 1355.
> Thanks in advance!|||I didn't finish. :-/
If you still cannot find the cause of the problem, I suggest that you
reboot the server.
In the case of 1) the solution is to put a small pause in your code
before starting the MSSQLServer service again.
In the case of 2) you will need to ensure that your application uses
another port - perhaps there is a setting somewhere (maybe the registry)
where you can tweak this.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Mark Allison wrote:
> Dolph,
> There are two scenarios that I can think of that will cause this situation.
> 1) You have bounced the SQL Server service programmatically (probably in
> C++) and the service has been stopped and restarted too quickly. SQL
> Server does not release the port quickly enough before it is restarted
> and thinks that another service is using port 1433. The bind, then fails.
> 2) Another application is using port 1433.
> You can check your ports using this on the commandline:
> netstat -a
> Look at the local address column for <machinename>:ms-sql-s or
> <machinename>:1433
> On my Inspiron laptop I get these results:
>
> Active Connections
> Proto Local Address Foreign Address State
> TCP inspiron4100:ftp inspiron4100:0 LISTENING
> TCP inspiron4100:http inspiron4100:0 LISTENING
> TCP inspiron4100:epmap inspiron4100:0 LISTENING
> TCP inspiron4100:https inspiron4100:0 LISTENING
> TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
> TCP inspiron4100:1025 inspiron4100:0 LISTENING
> TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
> TCP inspiron4100:2869 inspiron4100:0 LISTENING
> TCP inspiron4100:3389 inspiron4100:0 LISTENING
> TCP inspiron4100:1028 inspiron4100:0 LISTENING
> TCP inspiron4100:1061 inspiron4100:0 LISTENING
> TCP inspiron4100:1134 localhost:1135 ESTABLISHED
> TCP inspiron4100:1135 localhost:1134 ESTABLISHED
> TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
> TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863 ESTABLISHED
> TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
> TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
> TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
> UDP inspiron4100:microsoft-ds *:*
> UDP inspiron4100:isakmp *:*
> UDP inspiron4100:1026 *:*
> UDP inspiron4100:1069 *:*
> UDP inspiron4100:1070 *:*
> UDP inspiron4100:1131 *:*
> UDP inspiron4100:ms-sql-m *:*
> UDP inspiron4100:3456 *:*
> UDP inspiron4100:4500 *:*
> UDP inspiron4100:ntp *:*
> UDP inspiron4100:1050 *:*
> UDP inspiron4100:1057 *:*
> UDP inspiron4100:1156 *:*
> UDP inspiron4100:1900 *:*
> UDP inspiron4100:ntp *:*
> UDP inspiron4100:netbios-ns *:*
> UDP inspiron4100:netbios-dgm *:*
> UDP inspiron4100:1900 *:*
>
>
>|||Thanks for trying to help. Sadly, it can not be either case. I am not
doing anything with C++ and I have not downloaded any application lately that
is build on it. Esp. working with SQL server. I looked at the ports with
netstat -an and I see the port being listened by SQL Server. The server just
wont bind to that port. If I can't find a solution soon, I will be left to
do a re-install. :(
Dolph
"Mark Allison" wrote:
> I didn't finish. :-/
> If you still cannot find the cause of the problem, I suggest that you
> reboot the server.
> In the case of 1) the solution is to put a small pause in your code
> before starting the MSSQLServer service again.
> In the case of 2) you will need to ensure that your application uses
> another port - perhaps there is a setting somewhere (maybe the registry)
> where you can tweak this.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Mark Allison wrote:
> > Dolph,
> >
> > There are two scenarios that I can think of that will cause this situation.
> >
> > 1) You have bounced the SQL Server service programmatically (probably in
> > C++) and the service has been stopped and restarted too quickly. SQL
> > Server does not release the port quickly enough before it is restarted
> > and thinks that another service is using port 1433. The bind, then fails.
> >
> > 2) Another application is using port 1433.
> >
> > You can check your ports using this on the commandline:
> >
> > netstat -a
> >
> > Look at the local address column for <machinename>:ms-sql-s or
> > <machinename>:1433
> >
> > On my Inspiron laptop I get these results:
> >
> >
> > Active Connections
> >
> > Proto Local Address Foreign Address State
> > TCP inspiron4100:ftp inspiron4100:0 LISTENING
> > TCP inspiron4100:http inspiron4100:0 LISTENING
> > TCP inspiron4100:epmap inspiron4100:0 LISTENING
> > TCP inspiron4100:https inspiron4100:0 LISTENING
> > TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
> > TCP inspiron4100:1025 inspiron4100:0 LISTENING
> > TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
> > TCP inspiron4100:2869 inspiron4100:0 LISTENING
> > TCP inspiron4100:3389 inspiron4100:0 LISTENING
> > TCP inspiron4100:1028 inspiron4100:0 LISTENING
> > TCP inspiron4100:1061 inspiron4100:0 LISTENING
> > TCP inspiron4100:1134 localhost:1135 ESTABLISHED
> > TCP inspiron4100:1135 localhost:1134 ESTABLISHED
> > TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
> > TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863 ESTABLISHED
> > TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
> > TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
> > TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
> > UDP inspiron4100:microsoft-ds *:*
> > UDP inspiron4100:isakmp *:*
> > UDP inspiron4100:1026 *:*
> > UDP inspiron4100:1069 *:*
> > UDP inspiron4100:1070 *:*
> > UDP inspiron4100:1131 *:*
> > UDP inspiron4100:ms-sql-m *:*
> > UDP inspiron4100:3456 *:*
> > UDP inspiron4100:4500 *:*
> > UDP inspiron4100:ntp *:*
> > UDP inspiron4100:1050 *:*
> > UDP inspiron4100:1057 *:*
> > UDP inspiron4100:1156 *:*
> > UDP inspiron4100:1900 *:*
> > UDP inspiron4100:ntp *:*
> > UDP inspiron4100:netbios-ns *:*
> > UDP inspiron4100:netbios-dgm *:*
> > UDP inspiron4100:1900 *:*
> >
> >
> >
> >
> >
>|||Dolph Larson wrote:
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
For the benefit of any other poor ***s trying to work this one out,
here's what I just found...
We got the "SuperSocket Info: Bind failed on TCP port 1433" error, yet
netstat says the socket _is_ listening. TCPView (from the excellent
sysinternals site) confirms that it's listening, and that it's SQL
server that doing it.
Stumped despite much googling, I suddenly realised we'd recently
installed a new remote access _client_ on this server, Windows Secure
Application Manager from netscreen. This seems to work by hooking the
TCP stack with an LSP. Needless to say, it was this that was messing
up SQL server - using the diagnostics tool to remove the LSP sorted it
out straight away.
Thinking back, I've seen problems with an LSP before: some weird
problem with Norton Antivirus left a machine in a state where ipconfig
said it was dialled up OK, it could ping, but it couldn't do email or
http... Zapping the LSP sorted it (not that I can remember how I
removed it!)
Cheers,
Martin.

Bind failed on TCP port 1044.

I am getting this error in the Event Viewer and the clients are unable to
connect to the SQL server. What is wrong?
PLEASE HELP!!
ScottHi
You SQL Server is configured not to use the standard 1433 port, but this is
not a problem in itself.
By the time SQL Server starts, there is another application that is using
the port 1044. This results in SQL Server not being able to use it. You need
to either stop that application or configure SQL Server to use a different
port. Configure the port though Server Network Utility in the SQL Server men
u.
Regards
Mike
"scottdog129" wrote:

> I am getting this error in the Event Viewer and the clients are unable to
> connect to the SQL server. What is wrong?
> PLEASE HELP!!
> Scottsql

Bind failed on TCP port 1044.

I am getting this error in the Event Viewer and the clients are unable to
connect to the SQL server. What is wrong?
PLEASE HELP!!
Scott
Hi
You SQL Server is configured not to use the standard 1433 port, but this is
not a problem in itself.
By the time SQL Server starts, there is another application that is using
the port 1044. This results in SQL Server not being able to use it. You need
to either stop that application or configure SQL Server to use a different
port. Configure the port though Server Network Utility in the SQL Server menu.
Regards
Mike
"scottdog129" wrote:

> I am getting this error in the Event Viewer and the clients are unable to
> connect to the SQL server. What is wrong?
> PLEASE HELP!!
> Scott

Thursday, March 22, 2012

Bii.exe V1.0-1 Utility for SQL Server 2000

I tried using this utilily to upload images into a table with a bigint datatype but it failed saying it does not support such datatypes. Is there another version of the bii utility that can support all the data types supported by SQL server 2000?
From http://developmentnow.com/g/118_2004_11_0_18_0/microsoft-public-sqlserver-server.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
I'm not aware of away to load images into a bigint column but I am curious
as to what kind of images do you have that fit into an 8 byte column?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Emmanuel" <nospam@.developmentnow.com> wrote in message
news:273fc90b-d4fa-4fbb-a9e3-7c35d65974f9@.developmentnow.com...
>I tried using this utilily to upload images into a table with a bigint
>datatype but it failed saying it does not support such datatypes. Is there
>another version of the bii utility that can support all the data types
>supported by SQL server 2000?
> From
> http://developmentnow.com/g/118_2004_11_0_18_0/microsoft-public-sqlserver-server.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com

Bii.exe V1.0-1 Utility for SQL Server 2000

I tried using this utilily to upload images into a table with a bigint datatype but it failed saying it does not support such datatypes. Is there another version of the bii utility that can support all the data types supported by SQL server 2000
From http://developmentnow.com/g/118_2004_11_0_18_0/microsoft-public-sqlserver-server.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.comI'm not aware of away to load images into a bigint column but I am curious
as to what kind of images do you have that fit into an 8 byte column?
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Emmanuel" <nospam@.developmentnow.com> wrote in message
news:273fc90b-d4fa-4fbb-a9e3-7c35d65974f9@.developmentnow.com...
>I tried using this utilily to upload images into a table with a bigint
>datatype but it failed saying it does not support such datatypes. Is there
>another version of the bii utility that can support all the data types
>supported by SQL server 2000?
> From
> http://developmentnow.com/g/118_2004_11_0_18_0/microsoft-public-sqlserver-server.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com

Bii.exe V1.0-1 Utility for SQL Server 2000

I tried using this utilily to upload images into a table with a bigint datat
ype but it failed saying it does not support such datatypes. Is there anothe
r version of the bii utility that can support all the data types supported b
y SQL server 2000?
From http://developmentnow.com/g/118_200...
ver.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.comI'm not aware of away to load images into a bigint column but I am curious
as to what kind of images do you have that fit into an 8 byte column?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Emmanuel" <nospam@.developmentnow.com> wrote in message
news:273fc90b-d4fa-4fbb-a9e3-7c35d65974f9@.developmentnow.com...
>I tried using this utilily to upload images into a table with a bigint
>datatype but it failed saying it does not support such datatypes. Is there
>another version of the bii utility that can support all the data types
>supported by SQL server 2000?
> From
> http://developmentnow.com/g/118_200...ver
.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com

Tuesday, March 20, 2012

Big Problem Sql server 2000 database crash

I have a small sql server 2000 database that has never been backed up. The
drive where the main database file resides failed on the server but the
drive where the transaction logs is still good.
Can I recover the database from just the transaction logs? And can you
point me to some documentation on how to do this?
Thank you
JoelYou can't restore any transaction logs without first restoring a full
backup.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Joel" <nowhere@.nowhere.com> wrote in message
news:%23gyxCqhxGHA.1248@.TK2MSFTNGP02.phx.gbl...
I have a small sql server 2000 database that has never been backed up. The
drive where the main database file resides failed on the server but the
drive where the transaction logs is still good.
Can I recover the database from just the transaction logs? And can you
point me to some documentation on how to do this?
Thank you
Joel|||If I remember correctly, you can't even back up the transaction log
without first backing up the database.
Roy Harvey
Beacon Falls, CT
On Tue, 22 Aug 2006 15:47:31 -0400, "Tom Moreau"
<tom@.dont.spam.me.cips.ca> wrote:

>You can't restore any transaction logs without first restoring a full
>backup.
>--
> Tom
>----
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Toronto, ON Canada|||Roy Harvey wrote:
> If I remember correctly, you can't even back up the transaction log
> without first backing up the database.
>
And for the OP, the moral of this story is...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I know it might be stretching it a bit, but can I recreate a database and
then somehow use the log file to repopulate the database file?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OSHYaPixGHA.2260@.TK2MSFTNGP03.phx.gbl...
> You can't restore any transaction logs without first restoring a full
> backup.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> "Joel" <nowhere@.nowhere.com> wrote in message
> news:%23gyxCqhxGHA.1248@.TK2MSFTNGP02.phx.gbl...
> I have a small sql server 2000 database that has never been backed up.
> The
> drive where the main database file resides failed on the server but the
> drive where the transaction logs is still good.
> Can I recover the database from just the transaction logs? And can you
> point me to some documentation on how to do this?
> Thank you
> Joel
>|||The moral is even if it is a semi "test" database back it up.
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:44EB6274.9080507@.realsqlguy.com...
> Roy Harvey wrote:
> And for the OP, the moral of this story is...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Joel wrote:
> The moral is even if it is a semi "test" database back it up.
>
Bingo!!
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Nope, that's not possible.
Bob
"Joel" wrote:

> I know it might be stretching it a bit, but can I recreate a database and
> then somehow use the log file to repopulate the database file?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:OSHYaPixGHA.2260@.TK2MSFTNGP03.phx.gbl...
>
>

Big Problem Sql server 2000 database crash

I have a small sql server 2000 database that has never been backed up. The
drive where the main database file resides failed on the server but the
drive where the transaction logs is still good.
Can I recover the database from just the transaction logs? And can you
point me to some documentation on how to do this?
Thank you
JoelYou can't restore any transaction logs without first restoring a full
backup.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Joel" <nowhere@.nowhere.com> wrote in message
news:%23gyxCqhxGHA.1248@.TK2MSFTNGP02.phx.gbl...
I have a small sql server 2000 database that has never been backed up. The
drive where the main database file resides failed on the server but the
drive where the transaction logs is still good.
Can I recover the database from just the transaction logs? And can you
point me to some documentation on how to do this?
Thank you
Joel|||If I remember correctly, you can't even back up the transaction log
without first backing up the database.
Roy Harvey
Beacon Falls, CT
On Tue, 22 Aug 2006 15:47:31 -0400, "Tom Moreau"
<tom@.dont.spam.me.cips.ca> wrote:
>You can't restore any transaction logs without first restoring a full
>backup.
>--
> Tom
>----
>Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>SQL Server MVP
>Toronto, ON Canada|||Roy Harvey wrote:
> If I remember correctly, you can't even back up the transaction log
> without first backing up the database.
>
And for the OP, the moral of this story is...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I know it might be stretching it a bit, but can I recreate a database and
then somehow use the log file to repopulate the database file?
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OSHYaPixGHA.2260@.TK2MSFTNGP03.phx.gbl...
> You can't restore any transaction logs without first restoring a full
> backup.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> "Joel" <nowhere@.nowhere.com> wrote in message
> news:%23gyxCqhxGHA.1248@.TK2MSFTNGP02.phx.gbl...
> I have a small sql server 2000 database that has never been backed up.
> The
> drive where the main database file resides failed on the server but the
> drive where the transaction logs is still good.
> Can I recover the database from just the transaction logs? And can you
> point me to some documentation on how to do this?
> Thank you
> Joel
>|||The moral is even if it is a semi "test" database back it up.
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:44EB6274.9080507@.realsqlguy.com...
> Roy Harvey wrote:
>> If I remember correctly, you can't even back up the transaction log
>> without first backing up the database.
> And for the OP, the moral of this story is...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Joel wrote:
> The moral is even if it is a semi "test" database back it up.
>
Bingo!!
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Nope, that's not possible.
Bob
"Joel" wrote:
> I know it might be stretching it a bit, but can I recreate a database and
> then somehow use the log file to repopulate the database file?
> "Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
> news:OSHYaPixGHA.2260@.TK2MSFTNGP03.phx.gbl...
> > You can't restore any transaction logs without first restoring a full
> > backup.
> >
> > --
> > Tom
> >
> > ----
> > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> > SQL Server MVP
> > Toronto, ON Canada
> > .
> > "Joel" <nowhere@.nowhere.com> wrote in message
> > news:%23gyxCqhxGHA.1248@.TK2MSFTNGP02.phx.gbl...
> > I have a small sql server 2000 database that has never been backed up.
> > The
> > drive where the main database file resides failed on the server but the
> > drive where the transaction logs is still good.
> >
> > Can I recover the database from just the transaction logs? And can you
> > point me to some documentation on how to do this?
> >
> > Thank you
> >
> > Joel
> >
> >
>
>

Big problem

I have two databases that replicate with merge replication. A couple of days, the replication process failed while trying to do a re-initialization (with upload changes to publisher option enabled) and it seemed that some of the records in the subscriber
were missing. So I did a restore of the subscriber and then I then kicked off another re-initialization (with upload changes to publisher option enabled) and it has completed succesfully. However, now it seems that some of the older data that was created
in the subscriber are no longer in the subscriber but they are in the publisher. In addition to this, some of the records that were created in the subscriber did not upload to the publisher.
Is there any way to manually flag records to force them to replicate (for inserts)?
You could try doing a dummy update on the relevant rows (or all rows if necessary). Something like
Update MyTable set fname = fname
should do it.
HTH,
Paul Ibison
|||Yes, I tried this, but the problem is that I need to know which column has changed for each row. Is there any way to get it to replicate the whole row?
|||In your first post you explain that there are some rows on the publisher which don't exist on the subscriber and vice-versa. For some reason the merge triggers didn't fire and MSmerge_contents doesn't contain the the row value, so it is not replicated. Up
dating these rows - any column - will force an entry to this system table, and this should then be replicated. However your second post explains you need to know which column has changed for each row, which is what confuses me

. Why is this required - d
o you also have rows which which exist on both publisher and subscriber but are not synchronized and contain different data?
Regards,
Paul Ibison
|||to force a row to be replicated again use sp_mergedummyupdate.
When the update is done on the other end SQL Server constructs the parameters for the stored procedure so that only the changed column is updated. So, it is stored somewhere. Figuring out where is not for mere mortals such as I - it is for the likes of su
ch as Mr. Ibison

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||Paul,
Yes, sorry, I was not clear in my first description of the problem. There are some instances where there is already a recod there but it is an older version, and there are some instances where the records are not there at all. I was mixing the two problem
s up.
Thank you (and Hilary) for your answers. they have been very helpfull.

Sunday, March 25, 2012

Bind failed on TCP port 1433

Bind failed on TCP port 1433

Bind failed on TCP port 1433

Bind failed on TCP port 1044.

Bind failed on TCP port 1044.

Thursday, March 22, 2012

Bii.exe V1.0-1 Utility for SQL Server 2000

Bii.exe V1.0-1 Utility for SQL Server 2000

Bii.exe V1.0-1 Utility for SQL Server 2000

Tuesday, March 20, 2012

Big Problem Sql server 2000 database crash

Big Problem Sql server 2000 database crash

Big problem

Best way to copy database

Blog Archive

About Me