Showing posts with label attaching. Show all posts
Showing posts with label attaching. Show all posts

Tuesday, March 27, 2012

Error 9004 attaching a database

I've been given a database backup in the form of an .mdf file, a bunch
of .ndf files, and a .log file. When I try to attach the .mdf file in
Server Management Studio, I get error 9004, An error occurred while
processing the log.
Any suggestions?
Phil Hibbs.Phil,
Kevin Farlee's answer has helped a couple of people with your problem.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=598396&SiteID=1
RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193140510.353843.250240@.y27g2000pre.googlegroups.com...
> I've been given a database backup in the form of an .mdf file, a bunch
> of .ndf files, and a .log file. When I try to attach the .mdf file in
> Server Management Studio, I get error 9004, An error occurred while
> processing the log.
> Any suggestions?
> Phil Hibbs.
>|||On 23 Oct, 13:31, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Kevin Farlee's answer has helped a couple of people with your problem.
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=598396&SiteID=1
Hm, looked promising, but when I try to "bring online" the database
with the files replaced, I get a load of errors in this form:
E:\data\data_file_09.ndf is not a primary database file
I have a .mdf file and 26 .ndf files, it looks like the creation of
the empty database is creating these files in a different way to the
original database.
Phil Hibbs.|||Phil,
Did you first create the 26 ndf files in your database to be replaced before
trying to copy the files into place?
RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193148065.531336.193770@.e34g2000pro.googlegroups.com...
> On 23 Oct, 13:31, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> Kevin Farlee's answer has helped a couple of people with your problem.
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=598396&SiteID=1
> Hm, looked promising, but when I try to "bring online" the database
> with the files replaced, I get a load of errors in this form:
> E:\data\data_file_09.ndf is not a primary database file
> I have a .mdf file and 26 .ndf files, it looks like the creation of
> the empty database is creating these files in a different way to the
> original database.
> Phil Hibbs.
>|||On 23 Oct, 20:15, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Did you first create the 26 ndf files in your database to be replaced before
> trying to copy the files into place?
Yep. I made a big CREATE DATABASE statement with the .mdf and all
the .ndf files specified in it.
Phil Hibbs.|||On 23 Oct, 20:15, "Russell Fields" <russellfie...@.nomail.com> wrote:
> Did you first create the 26 ndf files in your database to be replaced before
> trying to copy the files into place?
Yep. I made a big CREATE DATABASE statement with the .mdf and all
the .ndf files specified in it.
Phil Hibbs.|||Phil,
I understand that you are using SQL Server 2005, since you mention
Management Studio. I have tested and not been able to duplicate your
problem. When you use SSMS to do the attach, have you pressed the Script
command at the top of the panel. This will provide an exact script of the
commands to be run. If you do that, perhaps you will see something helpful.
Or, you can post it here for review.
Obviously something is different between our setups. I am running SQL
Server 2005 SP2. Are you also running SP2? I ask because SP2 fixed some
Management Studio problems and you should update to it (plus some hotfixes)
if you have not done so.
This describe my patch level:
http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
For more recent fixes, see also: http://support.microsoft.com/kb/937137/LN/
RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193222031.764752.35650@.v29g2000prd.googlegroups.com...
> On 23 Oct, 20:15, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> Did you first create the 26 ndf files in your database to be replaced
>> before
>> trying to copy the files into place?
> Yep. I made a big CREATE DATABASE statement with the .mdf and all
> the .ndf files specified in it.
> Phil Hibbs.
>|||On 25 Oct, 17:34, "Russell Fields" <russellfie...@.nomail.com> wrote:
> I have tested and not been able to duplicate your
> problem.
I suspect that is because you don't have the same .mdf and .ndf
and .log files that I have.
Phil Hibbs.|||Phil, No doubt about that. Sorry this did not help. - RLF
"PhilHibbs" <snarks@.gmail.com> wrote in message
news:1193761341.010344.78000@.k79g2000hse.googlegroups.com...
> On 25 Oct, 17:34, "Russell Fields" <russellfie...@.nomail.com> wrote:
>> I have tested and not been able to duplicate your
>> problem.
> I suspect that is because you don't have the same .mdf and .ndf
> and .log files that I have.
> Phil Hibbs.
>

Thursday, March 22, 2012

Error 8115 in Enterprise Manager when I want to shrink my attached Database

Hallo everbody,
I get Error 8115 "... Arithmetic overflow convertion numeric in datatype
numeric ..." when I want to shrink my database after attaching to sql server
2000.
No error occurs when I shrink my database with the query analyzer.
No error is reported when I try DBCC DBCHECK on the database.
So, whats the problem for the Enterprise Manager?
It's not only on my PC ... it occurs on other PCs too after attaching the
database to sql server 2000.
Any ideas?
Thanks und Greetings
Martin
My guess is a programming mistake in either EM or DMO. Does this happen when you open the shrink
dialog or when you press "OK"?
Is it a large database? Does it have many database files?
My guess is that EM or DMO executes some SQL statement that causes an overflow in the SQL code,
quite simply. Perhaps there's a KB article on this. Did you check? I ran profiler when opening the
dialog, and I can possibly see why an overflow can occur if you have strange figures in sysfiles, or
if you have many or large database...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Martin Schmeller" <martin.schmeller@.mcs-ag.com> wrote in message
news:exSk8soDFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Hallo everbody,
> I get Error 8115 "... Arithmetic overflow convertion numeric in datatype
> numeric ..." when I want to shrink my database after attaching to sql server
> 2000.
> No error occurs when I shrink my database with the query analyzer.
> No error is reported when I try DBCC DBCHECK on the database.
> So, whats the problem for the Enterprise Manager?
> It's not only on my PC ... it occurs on other PCs too after attaching the
> database to sql server 2000.
> Any ideas?
> Thanks und Greetings
> Martin
>

Error 8115 in Enterprise Manager when I want to shrink my attached Database

Hallo everbody,
I get Error 8115 "... Arithmetic overflow convertion numeric in datatype
numeric ..." when I want to shrink my database after attaching to sql server
2000.
No error occurs when I shrink my database with the query analyzer.
No error is reported when I try DBCC DBCHECK on the database.
So, whats the problem for the Enterprise Manager?
It's not only on my PC ... it occurs on other PCs too after attaching the
database to sql server 2000.
Any ideas?
Thanks und Greetings
MartinMy guess is a programming mistake in either EM or DMO. Does this happen when
you open the shrink
dialog or when you press "OK"?
Is it a large database? Does it have many database files?
My guess is that EM or DMO executes some SQL statement that causes an overfl
ow in the SQL code,
quite simply. Perhaps there's a KB article on this. Did you check? I ran pro
filer when opening the
dialog, and I can possibly see why an overflow can occur if you have strange
figures in sysfiles, or
if you have many or large database...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Martin Schmeller" <martin.schmeller@.mcs-ag.com> wrote in message
news:exSk8soDFHA.3824@.TK2MSFTNGP10.phx.gbl...
> Hallo everbody,
> I get Error 8115 "... Arithmetic overflow convertion numeric in datatype
> numeric ..." when I want to shrink my database after attaching to sql serv
er
> 2000.
> No error occurs when I shrink my database with the query analyzer.
> No error is reported when I try DBCC DBCHECK on the database.
> So, whats the problem for the Enterprise Manager?
> It's not only on my PC ... it occurs on other PCs too after attaching the
> database to sql server 2000.
> Any ideas?
> Thanks und Greetings
> Martin
>

Sunday, March 11, 2012

Error 5171 when attaching database

I am having an issue attaching a database. I am getting Error 5171 - ls is
not a primary database file.
We did not have a backup of a database, so I am not able to restore a
backup. The reason we do not have a backup of the database is a long story.
Anyways, somehow the SQL Server installation got corrupted and I was not able
to take a backup of the database. I had the mdf and ldf files. Once I
unsinstalled and installed SQL Server 2000 SP4, I was able to restore all
databases from a backup except for one, the one that did not have a backup.
But I had the mdf and ldf files. When I tried to attach the database, I got
the error above. Any help in this matter will be greatly appreciated.
Thanks,
Bill
A full backup would be very helpful, but anyway, take a look here:
http://www.sqlservercentral.com/scri...p?scriptid=599
HTH, Jens Suessmeyer.
|||>From the BOL:
sp_attach_db should only be executed on databases that were previously
detached from the database server using an explicit sp_detach_db
operation. If more than 16 files must be specified, use CREATE DATABASE
with the FOR ATTACH clause.
The database attached must have been created using the same code page
and sort order as SQL Server.
So check your collation on the server and if it is different than the
database (hopefully you have documented somewhere), find a SQL Server
that is on the same code page and attach there, change the collation of
the database, then detach and re-attach to the intended server.
Hope it will help.
Mel

Error 5171 when attaching database

I am having an issue attaching a database. I am getting Error 5171 - ls is
not a primary database file.
We did not have a backup of a database, so I am not able to restore a
backup. The reason we do not have a backup of the database is a long story.
Anyways, somehow the SQL Server installation got corrupted and I was not abl
e
to take a backup of the database. I had the mdf and ldf files. Once I
unsinstalled and installed SQL Server 2000 SP4, I was able to restore all
databases from a backup except for one, the one that did not have a backup.
But I had the mdf and ldf files. When I tried to attach the database, I got
the error above. Any help in this matter will be greatly appreciated.
Thanks,
BillA full backup would be very helpful, but anyway, take a look here:
http://www.sqlservercentral.com/scr...sp?scriptid=599
HTH, Jens Suessmeyer.|||>From the BOL:
sp_attach_db should only be executed on databases that were previously
detached from the database server using an explicit sp_detach_db
operation. If more than 16 files must be specified, use CREATE DATABASE
with the FOR ATTACH clause.
The database attached must have been created using the same code page
and sort order as SQL Server.
So check your collation on the server and if it is different than the
database (hopefully you have documented somewhere), find a SQL Server
that is on the same code page and attach there, change the collation of
the database, then detach and re-attach to the intended server.
Hope it will help.
Mel|||Thank you guys for your help. I tried a few things and it did not work. If
one problem was fixed then another was created. Anyways, the users have sai
d
they do not need that database and they will probably recreate it if needed.
Bill
"MSLam" wrote:

> sp_attach_db should only be executed on databases that were previously
> detached from the database server using an explicit sp_detach_db
> operation. If more than 16 files must be specified, use CREATE DATABASE
> with the FOR ATTACH clause.
> The database attached must have been created using the same code page
> and sort order as SQL Server.
> So check your collation on the server and if it is different than the
> database (hopefully you have documented somewhere), find a SQL Server
> that is on the same code page and attach there, change the collation of
> the database, then detach and re-attach to the intended server.
> Hope it will help.
> Mel
>

Error 5171 when attaching database

I am having an issue attaching a database. I am getting Error 5171 - ls is
not a primary database file.
We did not have a backup of a database, so I am not able to restore a
backup. The reason we do not have a backup of the database is a long story.
Anyways, somehow the SQL Server installation got corrupted and I was not able
to take a backup of the database. I had the mdf and ldf files. Once I
unsinstalled and installed SQL Server 2000 SP4, I was able to restore all
databases from a backup except for one, the one that did not have a backup.
But I had the mdf and ldf files. When I tried to attach the database, I got
the error above. Any help in this matter will be greatly appreciated.
Thanks,
BillA full backup would be very helpful, but anyway, take a look here:
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
HTH, Jens Suessmeyer.|||>From the BOL:
sp_attach_db should only be executed on databases that were previously
detached from the database server using an explicit sp_detach_db
operation. If more than 16 files must be specified, use CREATE DATABASE
with the FOR ATTACH clause.
The database attached must have been created using the same code page
and sort order as SQL Server.
So check your collation on the server and if it is different than the
database (hopefully you have documented somewhere), find a SQL Server
that is on the same code page and attach there, change the collation of
the database, then detach and re-attach to the intended server.
Hope it will help.
Mel|||Thank you guys for your help. I tried a few things and it did not work. If
one problem was fixed then another was created. Anyways, the users have said
they do not need that database and they will probably recreate it if needed.
Bill
"MSLam" wrote:
> >From the BOL:
> sp_attach_db should only be executed on databases that were previously
> detached from the database server using an explicit sp_detach_db
> operation. If more than 16 files must be specified, use CREATE DATABASE
> with the FOR ATTACH clause.
> The database attached must have been created using the same code page
> and sort order as SQL Server.
> So check your collation on the server and if it is different than the
> database (hopefully you have documented somewhere), find a SQL Server
> that is on the same code page and attach there, change the collation of
> the database, then detach and re-attach to the intended server.
> Hope it will help.
> Mel
>

Friday, March 9, 2012

Error 5123 Operating System Error 32 on attaching a database

I have SQL Server loaded on my standalone laptop. I tried
to attach a database( xxx.MDF) and got an error as above.
How do I resolve this ?In your sp_attach_db statement, make sure the path to the
mdf, ldf files is correct.
Also, make sure the SQL Server service account has
permissions to the path, files that you are attaching.
-Sue
On Wed, 25 Feb 2004 10:19:26 -0800, "Kishore Kapadia"
<kishore_kapadia@.peoplesoft.com> wrote:

>I have SQL Server loaded on my standalone laptop. I tried
>to attach a database( xxx.MDF) and got an error as above.
>How do I resolve this ?

Sunday, February 26, 2012

Error 3624

All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
...Mukund.R.L.Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
..Mukund.R.L.
>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
>> All,
>> I have the below problem while attaching the database,
can
>> any one assist.
>> Thanks in advance.
>> --Error Details
>> Microsoft SQL-DMO(ODBC SQLState-HY000)
>> Error 3624
>> Location : recovery.C:2014
>> Expression: Curr-->log_length >0
>> SPID :53
>> ProcessorId: 1064
>> below is the last lines from Error Log
>> 2004-06-01 10:27:14.45 spid53 Stack Signature for
the
>> dump is 0x9A8706F6
>> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
>> File: <recovery.c>, line=2014
>> Failed Assertion = 'curr->log_length > 0'.
>> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
>> 20, State: 1.
>> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
>> 23, State: 7
>> 2004-06-01 10:27:15.93 spid53 An error occurred
while
>> processing the log for database 'UPSSISGR'..
>>
>> ...Mukund.R.L.
>>
>>
>.
>

Error 3624

All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
....Mukund.R.L.
Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>
|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
...Mukund.R.L.

>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from[vbcol=seagreen]
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
can[vbcol=seagreen]
the[vbcol=seagreen]
while
>.
>

Error 3624

All,
I have the below problem while attaching the database, can
any one assist.
Thanks in advance.
--Error Details
Microsoft SQL-DMO(ODBC SQLState-HY000)
Error 3624
Location : recovery.C:2014
Expression: Curr-->log_length >0
SPID :53
ProcessorId: 1064
below is the last lines from Error Log
2004-06-01 10:27:14.45 spid53 Stack Signature for the
dump is 0x9A8706F6
2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
File: <recovery.c>, line=2014
Failed Assertion = 'curr->log_length > 0'.
2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
20, State: 1.
2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
23, State: 7
2004-06-01 10:27:15.93 spid53 An error occurred while
processing the log for database 'UPSSISGR'..
...Mukund.R.L.Mukund.R.L.,
What version of SQL and service pack? Apply SP3a if you have SP2 or
earlier on 2000. Is there a stack dump or information in the Windows
Event log or SQL Server error log? You might be best raising a call with
MS PSS as it looks like you've been having this issue for a while from
my internet research.
SQL Server Support Centre
http://support.microsoft.com/default.aspx?pr=sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Mukund.R.L. wrote:
> All,
> I have the below problem while attaching the database, can
> any one assist.
> Thanks in advance.
> --Error Details
> Microsoft SQL-DMO(ODBC SQLState-HY000)
> Error 3624
> Location : recovery.C:2014
> Expression: Curr-->log_length >0
> SPID :53
> ProcessorId: 1064
> below is the last lines from Error Log
> 2004-06-01 10:27:14.45 spid53 Stack Signature for the
> dump is 0x9A8706F6
> 2004-06-01 10:27:14.46 spid53 SQL Server Assertion:
> File: <recovery.c>, line=2014
> Failed Assertion = 'curr->log_length > 0'.
> 2004-06-01 10:27:14.46 spid53 Error: 3624, Severity:
> 20, State: 1.
> 2004-06-01 10:27:15.93 spid53 Error: 9004, Severity:
> 23, State: 7
> 2004-06-01 10:27:15.93 spid53 An error occurred while
> processing the log for database 'UPSSISGR'..
>
> ...Mukund.R.L.
>
>|||Thanks for Your response.
I have SQL 2000 with service pack 3a.
..Mukund.R.L.

>--Original Message--
>Mukund.R.L.,
>What version of SQL and service pack? Apply SP3a if you
have SP2 or
>earlier on 2000. Is there a stack dump or information in
the Windows
>Event log or SQL Server error log? You might be best
raising a call with
>MS PSS as it looks like you've been having this issue for
a while from
>my internet research.
>SQL Server Support Centre
>http://support.microsoft.com/default.aspx?pr=sql
>--
>Mark Allison, SQL Server MVP
>http://www.markallison.co.uk
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>Mukund.R.L. wrote:
can[vbcol=seagreen]
the[vbcol=seagreen]
while[vbcol=seagreen]
>.
>