detach db failed due to ghost cleanup

hi
i'm trying to detach a database. However i cant as the db is in use. I can
kill any user processes but not the non-user process 'ghost cleanup'. Because
of this the db is in use and the detach cannot occur.
I realise what the process 'ghost cleanup' is there for - but surely it
shouldn't be in use permanently? (db options such as shrink db are not set on
this db). There any safe way to disable?
Try putting the database in single user mode by using the ALTER DATABSE with
SET SINGLE_USER mode option and then try detaching.
"Dunxz" wrote:

> hi
> i'm trying to detach a database. However i cant as the db is in use. I can
> kill any user processes but not the non-user process 'ghost cleanup'. Because
> of this the db is in use and the detach cannot occur.
> I realise what the process 'ghost cleanup' is there for - but surely it
> shouldn't be in use permanently? (db options such as shrink db are not set on
> this db). There any safe way to disable?
>
|||Thanks
"Pragya" wrote:
[vbcol=seagreen]
> Try putting the database in single user mode by using the ALTER DATABSE with
> SET SINGLE_USER mode option and then try detaching.
>
> "Dunxz" wrote:

designer wanted

Hi!
I'm looking for (preferably free) a tool that is useful in graphical
representation of DB (something like Oracle Designer). Could you give me
some hints where to find one?
Thanx
Yaro
Visio is pretty good for any type of UML design as well as E-R Diagramming.
It can even generate classes for you as well as the SQL needed to create the
objects.
Its' relatively inexpensive as far as designers go.
Rick Sawtell
"Jarosaw Tajcher" <ziomuch@.wp.pl> wrote in message
news:cdrpao$q7e$1@.nemesis.news.tpi.pl...
> Hi!
> I'm looking for (preferably free) a tool that is useful in graphical
> representation of DB (something like Oracle Designer). Could you give me
> some hints where to find one?
> Thanx
> Yaro
>
|||The SQL Server (assuming you have already paid for it) comes with a diagramming tool. Also, MS Access (in case you aready have a copy of it) has a "relationship" tool which might be useful for your project (you can import pretty much any data into MS Acc
ess).
Not exactly, what you asked for, but you might already have the tool you are looking for...in your hands...
Tea C.
"Rick Sawtell" wrote:

> Visio is pretty good for any type of UML design as well as E-R Diagramming.
> It can even generate classes for you as well as the SQL needed to create the
> objects.
> Its' relatively inexpensive as far as designers go.
>
> Rick Sawtell
>
> "Jaros3aw Tajcher" <ziomuch@.wp.pl> wrote in message
> news:cdrpao$q7e$1@.nemesis.news.tpi.pl...
>
>
|||There is no inexpensive tool for data modelling. While the SQL Server,
Access and Visio, may work they all have drawbacks.
One key feature is the ability to create a database or at least tables
in a database directly from a diagram and to have changes in the
diagram relect in the tables and relationships.
Anothe key feature of a tool is the ability to store elements of the
model ina repository for future re-use. Any experience developer would
love to carry around a file of tables used on other projects as a
short cut to designing the current project.
Lastly, you should look for the data and OODB (UML) modeling symbols
for Visio that may now exist, some for no fee, if your goal is OODBs.
Lou Arnold
On Sat, 24 Jul 2004 19:06:02 -0700, "=?Utf-8?B?VGVhQw==?="
<smece1972@.yahoo.com.nospam> wrote:

>The SQL Server (assuming you have already paid for it) comes with a diagramming tool. Also, MS Access (in case you aready have a copy of it) has a "relationship" tool which might be useful for your project (you can import pretty much any data into MS Ac
cess).[vbcol=seagreen]
>Not exactly, what you asked for, but you might already have the tool you are looking for...in your hands...
>--
>Tea C.
>
>"Rick Sawtell" wrote:

Design and Performance question

Hi
I'm working now on a project that is Database oriented, and this
Database is so big and has millions of records, my question is:
Where must I put the business logic?
1- Client side: where client is responsible for the business logic.
2- Server Side: exceute the business logic in the server using stored
procedures and triggers...
3- Hybrid schema load balancing on the two sides.
I'm using MS.SQL Server2000
I have many of very complex queries, and many of complex views.
and finally can I depend on Jobs in MS.SQL Server in some tasks with
out impact the perfermance down.
Please reply ASAP
thanks a lot.
I try to put it where it is best suited.
Anything set based which acts on a large amount of data should be in stored
procs or performance will suffer.
Always interface with the db via SPs as you can monitor and correct problems
and change the database tructure without changing anything outside the db.
Anything not set based is up to you and may just depend on the avalability
of development expertise.
You can rely on jobs. Whether they mipact anything depends on what they do.
"Yousef Absee" wrote:

> Hi
> I'm working now on a project that is Database oriented, and this
> Database is so big and has millions of records, my question is:
> Where must I put the business logic?
> 1- Client side: where client is responsible for the business logic.
> 2- Server Side: exceute the business logic in the server using stored
> procedures and triggers...
> 3- Hybrid schema load balancing on the two sides.
> I'm using MS.SQL Server2000
> I have many of very complex queries, and many of complex views.
> and finally can I depend on Jobs in MS.SQL Server in some tasks with
> out impact the perfermance down.
> Please reply ASAP
> thanks a lot.
>
|||"Yousef Absee" <youstec@.gmail.com> wrote in message
news:1131554866.394769.115640@.g47g2000cwa.googlegr oups.com...
> Where must I put the business logic?
> 1- Client side: where client is responsible for the business logic.
In the bizClasses that are called by the GUI and directly interact with the
db. If that is via metaData it's even better.

> 2- Server Side: exceute the business logic in the server using stored
> procedures and triggers...
Well sure, These rules may not be business rules but basic data handeling
instead. Triggers that generate data in other tables for necessary reasons
is a good thing.

> 3- Hybrid schema load balancing on the two sides.
> I'm using MS.SQL Server2000
> I have many of very complex queries, and many of complex views.
> and finally can I depend on Jobs in MS.SQL Server in some tasks with
> out impact the perfermance down.
Depends on what the job is to do and what is happening at the same time?