Could not run BEGIN TRANSACTION in database whatever because the database is read-only.

I had a databases running on SQL Server (EVALUATION VERSION).

I moved it to another system running:

-Windows 2000 Server
-IIS 5.0
-BlueDragon Server
-MSDE

I applied all of the latest service packs, security updates, etc...
Intalled SQL Server Web Data Administrator and .NET framework.

I attached the database using sp_attach_db:
>osql U sa
>password
>Sp_attach_db whatever',
>@.filename1 = C:\Program Files\Microsoft SQL
Server\MSSQL\Data\CollaborationTools.mdf',
>@.filename2 = C:\Program Files\Microsoft SQL
Server\MSSQL\Data\CollaborationTools.ldf'
>go

I added my datasource using the ODBC Admin Tool...
Verified it using the BlueDragon Admin Datasources page...

But now I'm getting the error message:

'Could not run BEGIN TRANSACTION in database 'whatever' because the
database is read-only.'

Any help/guidance would be appreciated.
Thanks very much.

Shaunokay, thanks for the guidance...

here's what i did:

i went to the location of the .mdf and .ldf files and made sure the
read only attribute wasn't checked.

i then entered the following commands via the cmd prompt:

>osql U sa
>password
>USE master
>EXEC sp_dboption collaboration', read only', FALSE'
>go

I verified by viewing the database properties in the Web Data
Administrator. The Status of the Database now reads Normal' not
Standby'.

Thanks very much.

-shaun|||"SS" <stiznoit@.yahoo.com> wrote in message
news:dab7211.0404141325.6df43251@.posting.google.co m...
> But now I'm getting the error message:
> 'Could not run BEGIN TRANSACTION in database 'whatever' because the
> database is read-only.'

Unless I'm missing something, it's pretty obvious. For some reason database
"whatever" has the read-only flag set.

See db_options to reset.

And since of course since it's read only, there's no point in allowing a
transaction since you can't do anything in it anyway.

> Any help/guidance would be appreciated.
> Thanks very much.
> Shaun|||okay, thanks for the guidance...

here's what i did:

i went to the location of the .mdf and .ldf files and made sure the
read only attribute wasn't checked.

i then entered the following commands via the cmd prompt:

>osql U sa
>password
>USE master
>EXEC sp_dboption collaboration', read only', FALSE'
>go

I verified by viewing the database properties in the Web Data
Administrator. The Status of the Database now reads Normal' not
Standby'.

Thanks very much.

-shaun

Could not run BEGIN TRANSACTION in database whatever because the database is read-only.

I had a databases running on SQL Server (EVALUATION VERSION).

I moved it to another system running:

-Windows 2000 Server
-IIS 5.0
-BlueDragon Server
-MSDE

I applied all of the latest service packs, security updates, etc...
Intalled SQL Server Web Data Administrator and .NET framework.

I attached the database using sp_attach_db:
>osql U sa
>password
>Sp_attach_db whatever',
>@.filename1 = C:\Program Files\Microsoft SQL
Server\MSSQL\Data\CollaborationTools.mdf',
>@.filename2 = C:\Program Files\Microsoft SQL
Server\MSSQL\Data\CollaborationTools.ldf'
>go

I added my datasource using the ODBC Admin Tool...
Verified it using the BlueDragon Admin Datasources page...

But now I'm getting the error message:

'Could not run BEGIN TRANSACTION in database 'whatever' because the
database is read-only.'

Any help/guidance would be appreciated.
Thanks very much.

Shaun"SS" <stiznoit@.yahoo.com> wrote in message
news:dab7211.0404141325.6df43251@.posting.google.co m...
> But now I'm getting the error message:
> 'Could not run BEGIN TRANSACTION in database 'whatever' because the
> database is read-only.'

Unless I'm missing something, it's pretty obvious. For some reason database
"whatever" has the read-only flag set.

See db_options to reset.

And since of course since it's read only, there's no point in allowing a
transaction since you can't do anything in it anyway.

> Any help/guidance would be appreciated.
> Thanks very much.
> Shaunsql

Could not drop procedure.

I have made transaction replication and it's working fine and now I want to
drop one procedure from publisher database but its gave me an error that you
can't drop the procedure b/c it's beeing used in Replication .. what should
I do? can any tell me .
Thanks in advance.
Noor
I am using the following commands but still it gave me an error.
sp_droparticle 'LMS','CmsUpdateIndividualTest', 1,1
Server: Msg 14046, Level 16, State 1, Procedure sp_droparticle, Line 161
Could not drop article. A subscription exists on it.
Any idea about this ?
Thanks
Noor
"Noorali Issani" <naissani@.softhome.net> wrote in message
news:eg%23cZgVEEHA.1600@.tk2msftngp13.phx.gbl...
> I have made transaction replication and it's working fine and now I want
to
> drop one procedure from publisher database but its gave me an error that
you
> can't drop the procedure b/c it's beeing used in Replication .. what
should
> I do? can any tell me .
> Thanks in advance.
> Noor
>
|||First you have to remove the article from any subscriptions that subscribe
to it. You can drop the subscription for that article ONLY:
Use pubs
go
sp_dropsubscription @.publication = 'pubs' , @.article ='authors',
@.subscriber='ALL'
Then drop the article from the publication:
sp_droparticle @.publication = 'pubs', @.article = 'authors'
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Could not allocate space for object 'MSrepl_commands' in database

We have transaction replication set up in SQL 2K environment . It's simple
SQL 2k publisher to SQL 2K subscriber (both Enterprise). It works fine but
some times(once a week or so) we get error message "Could not allocate space
for object 'MSrepl_commands' in database 'zzzz_distribution' " and log reader
agent gets stopped. I don't see any issues with space and both data and log
files are set for auto grow. When I go back and see DB size is very minimal.
Can you throw some ideas.
Thanks,
Prabhu
This looks like a problem with the distribution database being unable to
grow, can you confirm that the distribution database has space to grow, and
the growth increment is not a percent but a fixed amount like 100 Mgs.
http://www.zetainteractive.com - Shift Happens!
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
"Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
news:7BD73EC1-0AF2-494B-AD3C-6AE6F3D2D605@.microsoft.com...
> We have transaction replication set up in SQL 2K environment . It's simple
> SQL 2k publisher to SQL 2K subscriber (both Enterprise). It works fine but
> some times(once a week or so) we get error message "Could not allocate
> space
> for object 'MSrepl_commands' in database 'zzzz_distribution' " and log
> reader
> agent gets stopped. I don't see any issues with space and both data and
> log
> files are set for auto grow. When I go back and see DB size is very
> minimal.
> Can you throw some ideas.
> Thanks,
> Prabhu