How can I check..

I have one database file in separate filegroup. I can't delete this file
because it is not empty.
How can I check which table is a part of this database file ?
select id, object_name(id) as 'Object', indid, name, s.groupid, fg.groupname
from sysindexes s inner join sysfilegroups fg
on s.groupid = fg.groupid
you can also put a where fg.groupname = 'myfilegroup'
to see only the objects on a particular FG
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"MK" <MK@.discussions.microsoft.com> wrote in message
news:FEC364E9-20CE-468B-A961-E56D70508032@.microsoft.com...
> I have one database file in separate filegroup. I can't delete this file
> because it is not empty.
> How can I check which table is a part of this database file ?

How can I check..

I have one database file in separate filegroup. I can't delete this file
because it is not empty.
How can I check which table is a part of this database file ?The easiest way is to do into Enterprise Manager, select
the table, right click and go to properties.
If you have a lot of tables then you can script them out
by selecting the database, all tasks, generate sql script,
then open it up in QA and do a search for the filegroup
you want to remove.
Peter
"I favor the Civil Rights Act of 1964 and it must be
enforced at gunpoint if necessary."
Ronald Reagan
>--Original Message--
>I have one database file in separate filegroup. I can't
delete this file
>because it is not empty.
>How can I check which table is a part of this database
file ?
>.
>|||select id, object_name(id) as 'Object', indid, name, s.groupid, fg.groupname
from sysindexes s inner join sysfilegroups fg
on s.groupid = fg.groupid
you can also put a where fg.groupname = 'myfilegroup'
to see only the objects on a particular FG
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"MK" <MK@.discussions.microsoft.com> wrote in message
news:FEC364E9-20CE-468B-A961-E56D70508032@.microsoft.com...
> I have one database file in separate filegroup. I can't delete this file
> because it is not empty.
> How can I check which table is a part of this database file ?

How can I check..

I have one database file in separate filegroup. I can't delete this file
because it is not empty.
How can I check which table is a part of this database file ?select id, object_name(id) as 'Object', indid, name, s.groupid, fg.groupname
from sysindexes s inner join sysfilegroups fg
on s.groupid = fg.groupid
you can also put a where fg.groupname = 'myfilegroup'
to see only the objects on a particular FG
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"MK" <MK@.discussions.microsoft.com> wrote in message
news:FEC364E9-20CE-468B-A961-E56D70508032@.microsoft.com...
> I have one database file in separate filegroup. I can't delete this file
> because it is not empty.
> How can I check which table is a part of this database file ?

Hot-standby SQL Server Using Alias Name?

I want to have a hot standby SQL server for my clients. My idea is to install
SQL on two separate machines, SRVA and SRVB, and configure continuous merge
replication between them. Client machines would connect to an alias name,
SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon failure, DNS
would be changed to point to SRVB. Could something like this work? If so, how
would one start to implement it?
Maybe a shorther question would be, is it possible for clients to connect to a
SQL server alias name (not a named instance) instead of the actual machine
name of the server?
--Eric RobinsonThis is a multi-part message in MIME format.
--=_NextPart_000_0370_01C3A9EA.14018070
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
Consider using a clustered installation of SQL Server. It has automatic
failover and requires no human intervention.
--
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Eric Robinson" <eric@._nospam_nvipa.com> wrote in message
news:CFN379384331352315@.news.microsoft.com...
I want to have a hot standby SQL server for my clients. My idea is to
install
SQL on two separate machines, SRVA and SRVB, and configure continuous merge
replication between them. Client machines would connect to an alias name,
SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon failure,
DNS
would be changed to point to SRVB. Could something like this work? If so,
how
would one start to implement it?
Maybe a shorther question would be, is it possible for clients to connect to
a
SQL server alias name (not a named instance) instead of the actual machine
name of the server?
--Eric Robinson
--=_NextPart_000_0370_01C3A9EA.14018070
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

Consider using a clustered =installation of SQL Server. It has automatic failover and requires no human intervention.
-- Tom
---T=homas A. Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL =Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql
"Eric Robinson" =wrote in message news:CFN3793843313523=15@.news.microsoft.com...I want to have a hot standby SQL server for my clients. My idea is to =install SQL on two separate machines, SRVA and SRVB, and configure =continuous merge replication between them. Client machines would connect to an alias =name, SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon =failure, DNS would be changed to point to SRVB. Could something like this =work? If so, how would one start to implement it?Maybe a shorther =question would be, is it possible for clients to connect to a SQL server =alias name (not a named instance) instead of the actual machine name of the server?--Eric Robinson

---

--=_NextPart_000_0370_01C3A9EA.14018070--

Hot Standby Server w/out Clustering?

I want to have a hot standby SQL server for my clients without clustering. My
idea is to install SQL on two separate machines, SRVA and SRVB, and configure
continuous merge replication between them. Client machines would connect to an
alias name, SRVC, with DNS for SRVC resolving to the IP address of SRVA. Upon
failure, DNS would be changed to point to SRVB. Could something like this
work?
Maybe a shorther question would be, is it possible for clients to connect to a
SQL server alias name (not a named instance) instead of the actual machine
name of the server?
--Eric RobinsonWhat it sounds like you need is log shipping, not merge
replication. Replication is not the best of solutions for
a standby solution, and if you use replication for some
form of availability, it's usually transactional.
Replication is good if you have some specific data to make
available, but you're limited by rowsize and such, but as
for a complete copy of your DB, replication is not the
way. Log shipping is the standard SQL method of making a
warm standby.
You can set up NLB to do what you want to alias things,
and this is all covered in the book SQL Server 2000 HIgh
Availability on how to set it up using it as a "switch"
mechanism - not load balanced - for SQL Server. There are
even configuration instructions on the CD-ROM.
>--Original Message--
>I want to have a hot standby SQL server for my clients
without clustering. My
>idea is to install SQL on two separate machines, SRVA and
SRVB, and configure
>continuous merge replication between them. Client
machines would connect to an
>alias name, SRVC, with DNS for SRVC resolving to the IP
address of SRVA. Upon
>failure, DNS would be changed to point to SRVB. Could
something like this
>work?
>Maybe a shorther question would be, is it possible for
clients to connect to a
>SQL server alias name (not a named instance) instead of
the actual machine
>name of the server?
>--Eric Robinson
>.
>|||To have standby , it is better to use Log shipping. U can
even write scripts to take backup and mover to otherserver
and restore ,
Replication is only for data propagation not for Standby.
In case of Replication schema changes won't be applied. Of
course Merge is not useful u need Transactioal replication.
>--Original Message--
>I want to have a hot standby SQL server for my clients
without clustering. My
>idea is to install SQL on two separate machines, SRVA and
SRVB, and configure
>continuous merge replication between them. Client
machines would connect to an
>alias name, SRVC, with DNS for SRVC resolving to the IP
address of SRVA. Upon
>failure, DNS would be changed to point to SRVB. Could
something like this
>work?
>Maybe a shorther question would be, is it possible for
clients to connect to a
>SQL server alias name (not a named instance) instead of
the actual machine
>name of the server?
>--Eric Robinson
>.
>