Showing posts with label client. Show all posts
Showing posts with label client. Show all posts

Friday, March 30, 2012

Moving Client Network Utility

Hi Folks,
I'm having to move workstations and was wondering if anybody knew a quick way to move all the alias's from your client network utility from one workstation to another.
CheersSave the following key and restore it over the other workstations.
HKEY_LOCAL_MACHINE=>SOFTWARE=>MICROSOFT=>MSSQLSERVER=>CLIENT=>CONNECTTO

Howdy!

Monday, March 26, 2012

Moving a database from SQL Server to MSDE

Hi,
I have created quite a large database project that the client now wants to
run locally for demo purposes.
What is the best (& easiest for non-programmer client) way to transport a
snapshot of this database from one to the other - with the data still
intact? The VS.Net tools appear to only move the structure and stored
procedures etc..
Thanks in adavance,
StuStu
I prefer BACKUP/RESTORE commands
"Stu Lock" <s.lock@.cergis.com> wrote in message
news:eCF$cGyyEHA.3336@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have created quite a large database project that the client now wants to
> run locally for demo purposes.
> What is the best (& easiest for non-programmer client) way to transport a
> snapshot of this database from one to the other - with the data still
> intact? The VS.Net tools appear to only move the structure and stored
> procedures etc..
> Thanks in adavance,
> Stu
>|||How do you restore an SQL Server database to an MSDE instance that has no
database installed?
THnx.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23B1asKyyEHA.3840@.tk2msftngp13.phx.gbl...
> Stu
> I prefer BACKUP/RESTORE commands
>
>
> "Stu Lock" <s.lock@.cergis.com> wrote in message
> news:eCF$cGyyEHA.3336@.TK2MSFTNGP11.phx.gbl...
>|||"Stu Lock" <s.lock@.cergis.com> wrote in message
news:%23gQ5rBzyEHA.2540@.TK2MSFTNGP09.phx.gbl...
> How do you restore an SQL Server database to an MSDE instance that has no
> database installed?
>
Same way you'd restore it to any SQL Server. RESTORE DATABASE foo from
disk='\\foo\bar\baz.bak'
BOL will have more details.

> THnx.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:%23B1asKyyEHA.3840@.tk2msftngp13.phx.gbl...
a[vbcol=seagreen]
>|||Just be aware of the limitations of MSDE. Maximum DB size is 2GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:DVbmd.8248$qv5.8175@.twister.nyroc.rr.com...
> "Stu Lock" <s.lock@.cergis.com> wrote in message
> news:%23gQ5rBzyEHA.2540@.TK2MSFTNGP09.phx.gbl...
no[vbcol=seagreen]
> Same way you'd restore it to any SQL Server. RESTORE DATABASE foo from
> disk='\\foo\bar\baz.bak'
> BOL will have more details.
>
wants[vbcol=seagreen]
transport[vbcol=seagreen]
> a
>sql

Moving a database from SQL Server to MSDE

Hi,
I have created quite a large database project that the client now wants to
run locally for demo purposes.
What is the best (& easiest for non-programmer client) way to transport a
snapshot of this database from one to the other - with the data still
intact? The VS.Net tools appear to only move the structure and stored
procedures etc..
Thanks in adavance,
StuStu
I prefer BACKUP/RESTORE commands
"Stu Lock" <s.lock@.cergis.com> wrote in message
news:eCF$cGyyEHA.3336@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have created quite a large database project that the client now wants to
> run locally for demo purposes.
> What is the best (& easiest for non-programmer client) way to transport a
> snapshot of this database from one to the other - with the data still
> intact? The VS.Net tools appear to only move the structure and stored
> procedures etc..
> Thanks in adavance,
> Stu
>|||How do you restore an SQL Server database to an MSDE instance that has no
database installed?
THnx.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23B1asKyyEHA.3840@.tk2msftngp13.phx.gbl...
> Stu
> I prefer BACKUP/RESTORE commands
>
>
> "Stu Lock" <s.lock@.cergis.com> wrote in message
> news:eCF$cGyyEHA.3336@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> I have created quite a large database project that the client now wants
>> to
>> run locally for demo purposes.
>> What is the best (& easiest for non-programmer client) way to transport a
>> snapshot of this database from one to the other - with the data still
>> intact? The VS.Net tools appear to only move the structure and stored
>> procedures etc..
>> Thanks in adavance,
>> Stu
>>
>|||"Stu Lock" <s.lock@.cergis.com> wrote in message
news:%23gQ5rBzyEHA.2540@.TK2MSFTNGP09.phx.gbl...
> How do you restore an SQL Server database to an MSDE instance that has no
> database installed?
>
Same way you'd restore it to any SQL Server. RESTORE DATABASE foo from
disk='\\foo\bar\baz.bak'
BOL will have more details.
> THnx.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:%23B1asKyyEHA.3840@.tk2msftngp13.phx.gbl...
> > Stu
> > I prefer BACKUP/RESTORE commands
> >
> >
> >
> >
> > "Stu Lock" <s.lock@.cergis.com> wrote in message
> > news:eCF$cGyyEHA.3336@.TK2MSFTNGP11.phx.gbl...
> >> Hi,
> >>
> >> I have created quite a large database project that the client now wants
> >> to
> >> run locally for demo purposes.
> >>
> >> What is the best (& easiest for non-programmer client) way to transport
a
> >> snapshot of this database from one to the other - with the data still
> >> intact? The VS.Net tools appear to only move the structure and stored
> >> procedures etc..
> >>
> >> Thanks in adavance,
> >>
> >> Stu
> >>
> >>
> >
> >
>|||Just be aware of the limitations of MSDE. Maximum DB size is 2GB.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:DVbmd.8248$qv5.8175@.twister.nyroc.rr.com...
> "Stu Lock" <s.lock@.cergis.com> wrote in message
> news:%23gQ5rBzyEHA.2540@.TK2MSFTNGP09.phx.gbl...
> > How do you restore an SQL Server database to an MSDE instance that has
no
> > database installed?
> >
> Same way you'd restore it to any SQL Server. RESTORE DATABASE foo from
> disk='\\foo\bar\baz.bak'
> BOL will have more details.
>
> > THnx.
> >
> >
> > "Uri Dimant" <urid@.iscar.co.il> wrote in message
> > news:%23B1asKyyEHA.3840@.tk2msftngp13.phx.gbl...
> > > Stu
> > > I prefer BACKUP/RESTORE commands
> > >
> > >
> > >
> > >
> > > "Stu Lock" <s.lock@.cergis.com> wrote in message
> > > news:eCF$cGyyEHA.3336@.TK2MSFTNGP11.phx.gbl...
> > >> Hi,
> > >>
> > >> I have created quite a large database project that the client now
wants
> > >> to
> > >> run locally for demo purposes.
> > >>
> > >> What is the best (& easiest for non-programmer client) way to
transport
> a
> > >> snapshot of this database from one to the other - with the data still
> > >> intact? The VS.Net tools appear to only move the structure and stored
> > >> procedures etc..
> > >>
> > >> Thanks in adavance,
> > >>
> > >> Stu
> > >>
> > >>
> > >
> > >
> >
> >
>

Moving a database from SQL Server to MSDE

Hi,
I have created quite a large database project that the client now wants to
run locally for demo purposes.
What is the best (& easiest for non-programmer client) way to transport a
snapshot of this database from one to the other - with the data still
intact? The VS.Net tools appear to only move the structure and stored
procedures etc..
Thanks in adavance,
Stu
Stu
I prefer BACKUP/RESTORE commands
"Stu Lock" <s.lock@.cergis.com> wrote in message
news:eCF$cGyyEHA.3336@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I have created quite a large database project that the client now wants to
> run locally for demo purposes.
> What is the best (& easiest for non-programmer client) way to transport a
> snapshot of this database from one to the other - with the data still
> intact? The VS.Net tools appear to only move the structure and stored
> procedures etc..
> Thanks in adavance,
> Stu
>
|||How do you restore an SQL Server database to an MSDE instance that has no
database installed?
THnx.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:%23B1asKyyEHA.3840@.tk2msftngp13.phx.gbl...
> Stu
> I prefer BACKUP/RESTORE commands
>
>
> "Stu Lock" <s.lock@.cergis.com> wrote in message
> news:eCF$cGyyEHA.3336@.TK2MSFTNGP11.phx.gbl...
>
|||"Stu Lock" <s.lock@.cergis.com> wrote in message
news:%23gQ5rBzyEHA.2540@.TK2MSFTNGP09.phx.gbl...
> How do you restore an SQL Server database to an MSDE instance that has no
> database installed?
>
Same way you'd restore it to any SQL Server. RESTORE DATABASE foo from
disk='\\foo\bar\baz.bak'
BOL will have more details.
[vbcol=seagreen]
> THnx.
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:%23B1asKyyEHA.3840@.tk2msftngp13.phx.gbl...
a
>
|||Just be aware of the limitations of MSDE. Maximum DB size is 2GB.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:DVbmd.8248$qv5.8175@.twister.nyroc.rr.com...[vbcol=seagreen]
> "Stu Lock" <s.lock@.cergis.com> wrote in message
> news:%23gQ5rBzyEHA.2540@.TK2MSFTNGP09.phx.gbl...
no[vbcol=seagreen]
> Same way you'd restore it to any SQL Server. RESTORE DATABASE foo from
> disk='\\foo\bar\baz.bak'
> BOL will have more details.
>
wants[vbcol=seagreen]
transport
> a
>

Friday, March 9, 2012

Move FTC from SS2K to SS2K5

Morning,

Here is my scenario:

I have a SQL Server 2000 server with 10 clients.

Each client has 5 Full-Text Catalogs. For ease of explanation let’s call the FTCs C1 thru C5.

Now each client’s FTCs are named the SAME. So each client has FTCs named C1, C2, C3, C4 and C5.

I need to move the clients to our new SQL Server 2005 Enterprise server.

I can backup up the DB using the native SQL Server 2000 backup command but that of course does not back up the FTCs.

So once I restore the client DB over to the new SS2K5 server, how do I re-enable the FTCs and rebuild them so that they are the same as what was over on the SS2K server.

Also, after the first client is complete, will I run into a duplicate FTC error when I try to recreate the subsequent clients on the server since they all have the same named FTCs?

If so, how do I overcome this event?

Thanks for any and all help!

JJKusch,

In SQL Server 2005, the format of full-text catalogs has changed significantly. This change requires all full-text catalogs from previous versions of SQL Server to be rebuilt.

Move FTC from SS2K to SS2K5

Morning,

Here is my scenario:

I have a SQL Server 2000 server with 10 clients.

Each client has 5 Full-Text Catalogs. For ease of explanation let’s call the FTCs C1 thru C5.

Now each client’s FTCs are named the SAME. So each client has FTCs named C1, C2, C3, C4 and C5.

I need to move the clients to our new SQL Server 2005 Enterprise server.

I can backup up the DB using the native SQL Server 2000 backup command but that of course does not back up the FTCs.

So once I restore the client DB over to the new SS2K5 server, how do I re-enable the FTCs and rebuild them so that they are the same as what was over on the SS2K server.

Also, after the first client is complete, will I run into a duplicate FTC error when I try to recreate the subsequent clients on the server since they all have the same named FTCs?

If so, how do I overcome this event?

Thanks for any and all help!

JJKusch,

In SQL Server 2005, the format of full-text catalogs has changed significantly. This change requires all full-text catalogs from previous versions of SQL Server to be rebuilt.

Saturday, February 25, 2012

Move Database to client

Hi,
We have a database that we built for a client and we would like to make a
backup of the database and restore the database on our clients Sql Server
box. Both environments are running SQL Server 2000 SP3a.
We make a backup of the database on our server and when we go to the clients
site and run the restore it complains and gives an error message that states
SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
tried the WITH MOVE but aree not experienced DBA so we are not sure if we
configured it right.
RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Data.MDF',
MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Log.LDF'
We were able to restore the database some how and then it gives us an
SQL-DMO error 21776.
Any ideas on how we should best approach this situation so that we can get
the full database (structure and data)?
Thanks for the assistance.Please post the entire error message. Error 21776 is the
generic error used for an object not found in a collection.
The specifics of what object in what collection would be in
the entire error message.
-Sue
On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
S@.discussions.microsoft.com> wrote:
>Hi,
>We have a database that we built for a client and we would like to make a
>backup of the database and restore the database on our clients Sql Server
>box. Both environments are running SQL Server 2000 SP3a.
>We make a backup of the database on our server and when we go to the clients
>site and run the restore it complains and gives an error message that states
>SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
>tried the WITH MOVE but aree not experienced DBA so we are not sure if we
>configured it right.
>RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
>WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Data.MDF',
>MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Log.LDF'
>
>We were able to restore the database some how and then it gives us an
>SQL-DMO error 21776.
>Any ideas on how we should best approach this situation so that we can get
>the full database (structure and data)?
>Thanks for the assistance.|||Hi,
Sorry Sue, I should have elaborated more:
We have two problems:
1. we areunable to restore the database properly using either the GUI based
restore tool in the Enterprise Manager or usign the Query Analyzer with the
script included.
2. We some how managed to restore the database on the client's server and
when we try to access any component of the "restored" database, we receive
the SQL-DMO 21776 error. Which states the following
"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databases
colelction. If the name is a qualified name, use [ ] to separate various
parts of the name and try again."
So what i am looking for is what is the best mechanism to move our database
from out SQL Server 2000 environment to the clients SQL Server 2000
environment where we can preserve the table structure and data contained
within the database.
As well, how can we delete the database that we were able to create but now
is not recognized by the Enterprise manager due to the 21776 error.
I hope this provides a more detailed explanation of the situation we are
facing.
Thanks for the assistance,
Rod
"Sue Hoegemeier" wrote:
> Please post the entire error message. Error 21776 is the
> generic error used for an object not found in a collection.
> The specifics of what object in what collection would be in
> the entire error message.
> -Sue
> On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
> S@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >We have a database that we built for a client and we would like to make a
> >backup of the database and restore the database on our clients Sql Server
> >box. Both environments are running SQL Server 2000 SP3a.
> >
> >We make a backup of the database on our server and when we go to the clients
> >site and run the restore it complains and gives an error message that states
> >SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
> >tried the WITH MOVE but aree not experienced DBA so we are not sure if we
> >configured it right.
> >
> >RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
> >WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
> >server\mssql\data\CDR-Prod_Data.MDF',
> >MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
> >server\mssql\data\CDR-Prod_Log.LDF'
> >
> >
> >We were able to restore the database some how and then it gives us an
> >SQL-DMO error 21776.
> >
> >Any ideas on how we should best approach this situation so that we can get
> >the full database (structure and data)?
> >
> >Thanks for the assistance.
>|||The best mechanism is a backup and restore. You can also use
sp_detach_db, copy the data and log files and have the
client attach the files with sp_attach_db.
I would guess many of the problems are from having a
non-standard database name. The rules for identifier and
what characters are allowed in what positions is in the
books online topic: Using Identifiers
In terms of how to delete the database now, try dropping the
database using query analyzer and putting brackets around
the database name.
drop database [CDR-Prod]
-Sue
On Mon, 14 Mar 2005 08:11:05 -0800, "Rod S"
<RodS@.discussions.microsoft.com> wrote:
>Hi,
>Sorry Sue, I should have elaborated more:
>We have two problems:
>1. we areunable to restore the database properly using either the GUI based
>restore tool in the Enterprise Manager or usign the Query Analyzer with the
>script included.
>2. We some how managed to restore the database on the client's server and
>when we try to access any component of the "restored" database, we receive
>the SQL-DMO 21776 error. Which states the following
>"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databases
>colelction. If the name is a qualified name, use [ ] to separate various
>parts of the name and try again."
>So what i am looking for is what is the best mechanism to move our database
>from out SQL Server 2000 environment to the clients SQL Server 2000
>environment where we can preserve the table structure and data contained
>within the database.
>As well, how can we delete the database that we were able to create but now
>is not recognized by the Enterprise manager due to the 21776 error.
>I hope this provides a more detailed explanation of the situation we are
>facing.
>Thanks for the assistance,
>Rod
>"Sue Hoegemeier" wrote:
>> Please post the entire error message. Error 21776 is the
>> generic error used for an object not found in a collection.
>> The specifics of what object in what collection would be in
>> the entire error message.
>> -Sue
>> On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
>> S@.discussions.microsoft.com> wrote:
>> >Hi,
>> >
>> >We have a database that we built for a client and we would like to make a
>> >backup of the database and restore the database on our clients Sql Server
>> >box. Both environments are running SQL Server 2000 SP3a.
>> >
>> >We make a backup of the database on our server and when we go to the clients
>> >site and run the restore it complains and gives an error message that states
>> >SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
>> >tried the WITH MOVE but aree not experienced DBA so we are not sure if we
>> >configured it right.
>> >
>> >RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
>> >WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
>> >server\mssql\data\CDR-Prod_Data.MDF',
>> >MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
>> >server\mssql\data\CDR-Prod_Log.LDF'
>> >
>> >
>> >We were able to restore the database some how and then it gives us an
>> >SQL-DMO error 21776.
>> >
>> >Any ideas on how we should best approach this situation so that we can get
>> >the full database (structure and data)?
>> >
>> >Thanks for the assistance.
>>

Move Database to client

Hi,
We have a database that we built for a client and we would like to make a
backup of the database and restore the database on our clients Sql Server
box. Both environments are running SQL Server 2000 SP3a.
We make a backup of the database on our server and when we go to the clients
site and run the restore it complains and gives an error message that states
SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
tried the WITH MOVE but aree not experienced DBA so we are not sure if we
configured it right.
RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Data.MDF',
MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Log.LDF'
We were able to restore the database some how and then it gives us an
SQL-DMO error 21776.
Any ideas on how we should best approach this situation so that we can get
the full database (structure and data)?
Thanks for the assistance.
Please post the entire error message. Error 21776 is the
generic error used for an object not found in a collection.
The specifics of what object in what collection would be in
the entire error message.
-Sue
On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
S@.discussions.microsoft.com> wrote:

>Hi,
>We have a database that we built for a client and we would like to make a
>backup of the database and restore the database on our clients Sql Server
>box. Both environments are running SQL Server 2000 SP3a.
>We make a backup of the database on our server and when we go to the clients
>site and run the restore it complains and gives an error message that states
>SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
>tried the WITH MOVE but aree not experienced DBA so we are not sure if we
>configured it right.
>RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
>WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Data.MDF',
>MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Log.LDF'
>
>We were able to restore the database some how and then it gives us an
>SQL-DMO error 21776.
>Any ideas on how we should best approach this situation so that we can get
>the full database (structure and data)?
>Thanks for the assistance.
|||Hi,
Sorry Sue, I should have elaborated more:
We have two problems:
1. we areunable to restore the database properly using either the GUI based
restore tool in the Enterprise Manager or usign the Query Analyzer with the
script included.
2. We some how managed to restore the database on the client's server and
when we try to access any component of the "restored" database, we receive
the SQL-DMO 21776 error. Which states the following
"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databases
colelction. If the name is a qualified name, use [ ] to separate various
parts of the name and try again."
So what i am looking for is what is the best mechanism to move our database
from out SQL Server 2000 environment to the clients SQL Server 2000
environment where we can preserve the table structure and data contained
within the database.
As well, how can we delete the database that we were able to create but now
is not recognized by the Enterprise manager due to the 21776 error.
I hope this provides a more detailed explanation of the situation we are
facing.
Thanks for the assistance,
Rod
"Sue Hoegemeier" wrote:

> Please post the entire error message. Error 21776 is the
> generic error used for an object not found in a collection.
> The specifics of what object in what collection would be in
> the entire error message.
> -Sue
> On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
> S@.discussions.microsoft.com> wrote:
>
>
|||The best mechanism is a backup and restore. You can also use
sp_detach_db, copy the data and log files and have the
client attach the files with sp_attach_db.
I would guess many of the problems are from having a
non-standard database name. The rules for identifier and
what characters are allowed in what positions is in the
books online topic: Using Identifiers
In terms of how to delete the database now, try dropping the
database using query analyzer and putting brackets around
the database name.
drop database [CDR-Prod]
-Sue
On Mon, 14 Mar 2005 08:11:05 -0800, "Rod S"
<RodS@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi,
>Sorry Sue, I should have elaborated more:
>We have two problems:
>1. we areunable to restore the database properly using either the GUI based
>restore tool in the Enterprise Manager or usign the Query Analyzer with the
>script included.
>2. We some how managed to restore the database on the client's server and
>when we try to access any component of the "restored" database, we receive
>the SQL-DMO 21776 error. Which states the following
>"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databases
>colelction. If the name is a qualified name, use [ ] to separate various
>parts of the name and try again."
>So what i am looking for is what is the best mechanism to move our database
>from out SQL Server 2000 environment to the clients SQL Server 2000
>environment where we can preserve the table structure and data contained
>within the database.
>As well, how can we delete the database that we were able to create but now
>is not recognized by the Enterprise manager due to the 21776 error.
>I hope this provides a more detailed explanation of the situation we are
>facing.
>Thanks for the assistance,
>Rod
>"Sue Hoegemeier" wrote:

Move Database to client

Hi,
We have a database that we built for a client and we would like to make a
backup of the database and restore the database on our clients Sql Server
box. Both environments are running SQL Server 2000 SP3a.
We make a backup of the database on our server and when we go to the clients
site and run the restore it complains and gives an error message that states
SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
tried the WITH MOVE but aree not experienced DBA so we are not sure if we
configured it right.
RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Data.MDF',
MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
server\mssql\data\CDR-Prod_Log.LDF'
We were able to restore the database some how and then it gives us an
SQL-DMO error 21776.
Any ideas on how we should best approach this situation so that we can get
the full database (structure and data)?
Thanks for the assistance.Please post the entire error message. Error 21776 is the
generic error used for an object not found in a collection.
The specifics of what object in what collection would be in
the entire error message.
-Sue
On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
S@.discussions.microsoft.com> wrote:

>Hi,
>We have a database that we built for a client and we would like to make a
>backup of the database and restore the database on our clients Sql Server
>box. Both environments are running SQL Server 2000 SP3a.
>We make a backup of the database on our server and when we go to the client
s
>site and run the restore it complains and gives an error message that state
s
>SQL-DMO (ODBC SQLState: 42000) and states we should use the WITH MOVE. We
>tried the WITH MOVE but aree not experienced DBA so we are not sure if we
>configured it right.
>RESTORE DATABASE TEST FROM DISK='C:\TEMP\CDR-Prod.BAK'
>WITH MOVE 'TEST_Data' TO 'c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Data.MDF',
>MOVE 'TEST_Log' TO ' c:\program files\microsoft sql
>server\mssql\data\CDR-Prod_Log.LDF'
>
>We were able to restore the database some how and then it gives us an
>SQL-DMO error 21776.
>Any ideas on how we should best approach this situation so that we can get
>the full database (structure and data)?
>Thanks for the assistance.|||Hi,
Sorry Sue, I should have elaborated more:
We have two problems:
1. we areunable to restore the database properly using either the GUI based
restore tool in the Enterprise Manager or usign the Query Analyzer with the
script included.
2. We some how managed to restore the database on the client's server and
when we try to access any component of the "restored" database, we receive
the SQL-DMO 21776 error. Which states the following
"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databas
es
colelction. If the name is a qualified name, use [ ] to separate variou
s
parts of the name and try again."
So what i am looking for is what is the best mechanism to move our database
from out SQL Server 2000 environment to the clients SQL Server 2000
environment where we can preserve the table structure and data contained
within the database.
As well, how can we delete the database that we were able to create but now
is not recognized by the Enterprise manager due to the 21776 error.
I hope this provides a more detailed explanation of the situation we are
facing.
Thanks for the assistance,
Rod
"Sue Hoegemeier" wrote:

> Please post the entire error message. Error 21776 is the
> generic error used for an object not found in a collection.
> The specifics of what object in what collection would be in
> the entire error message.
> -Sue
> On Sun, 13 Mar 2005 18:55:02 -0800, "Rod S" <Rod
> S@.discussions.microsoft.com> wrote:
>
>|||The best mechanism is a backup and restore. You can also use
sp_detach_db, copy the data and log files and have the
client attach the files with sp_attach_db.
I would guess many of the problems are from having a
non-standard database name. The rules for identifier and
what characters are allowed in what positions is in the
books online topic: Using Identifiers
In terms of how to delete the database now, try dropping the
database using query analyzer and putting brackets around
the database name.
drop database [CDR-Prod]
-Sue
On Mon, 14 Mar 2005 08:11:05 -0800, "Rod S"
<RodS@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi,
>Sorry Sue, I should have elaborated more:
>We have two problems:
>1. we areunable to restore the database properly using either the GUI based
>restore tool in the Enterprise Manager or usign the Query Analyzer with the
>script included.
>2. We some how managed to restore the database on the client's server and
>when we try to access any component of the "restored" database, we receive
>the SQL-DMO 21776 error. Which states the following
>"Error 21776: [SQL-DMO} The name 'CDR-Prod' was not found in the Databa
ses
>colelction. If the name is a qualified name, use [ ] to separate vario
us
>parts of the name and try again."
>So what i am looking for is what is the best mechanism to move our database
>from out SQL Server 2000 environment to the clients SQL Server 2000
>environment where we can preserve the table structure and data contained
>within the database.
>As well, how can we delete the database that we were able to create but now
>is not recognized by the Enterprise manager due to the 21776 error.
>I hope this provides a more detailed explanation of the situation we are
>facing.
>Thanks for the assistance,
>Rod
>"Sue Hoegemeier" wrote:
>

Monday, February 20, 2012

MS Reporting Service for Client Application

1. We have Thin Client which is connecting to the Sql Express database. Is it
possible to use MS Reporting Service in Sql Express database.
2. What are the pre requisites shoule be there in my thin client to see my
reports in the thin client.SQL Express is not supported for RS 2000. It will be supported for RS 2005
with SQL Express but this will be a release after the release of SQL Server
2005. My understanding is sometime in the first half of next year.
What is your thin client? You can integrate reporting services multiple
ways. You can use URL integration (IE 6 works best). You can use web
services. Also, Visual Studio 2005 will have 2 controls, a winform and a
webform control. Note that these can work in local mode where no server is
required. There are some limitations (for instance you lose some exporting
formats, no scheduling etc) but in general pretty fully functional. You give
it a dataset and a report. Depending on what you want this might fulfill
your needs. In that case Express is just a datasource that you get your
dataset from. These controls will work in local mode with the release of VS
2005 (November).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mohan" <Mohan@.discussions.microsoft.com> wrote in message
news:100416CF-2203-4D42-A5D6-2D17328AE7D0@.microsoft.com...
> 1. We have Thin Client which is connecting to the Sql Express database. Is
> it
> possible to use MS Reporting Service in Sql Express database.
> 2. What are the pre requisites shoule be there in my thin client to see my
> reports in the thin client.
>|||Hi Bruce,
Thanks for you reply.
My Requrments is I want to view a report in my thin client(windows
applicaion). what the pre requisits need in the client applicaion.
Regards
Mohan
"Bruce L-C [MVP]" wrote:
> SQL Express is not supported for RS 2000. It will be supported for RS 2005
> with SQL Express but this will be a release after the release of SQL Server
> 2005. My understanding is sometime in the first half of next year.
> What is your thin client? You can integrate reporting services multiple
> ways. You can use URL integration (IE 6 works best). You can use web
> services. Also, Visual Studio 2005 will have 2 controls, a winform and a
> webform control. Note that these can work in local mode where no server is
> required. There are some limitations (for instance you lose some exporting
> formats, no scheduling etc) but in general pretty fully functional. You give
> it a dataset and a report. Depending on what you want this might fulfill
> your needs. In that case Express is just a datasource that you get your
> dataset from. These controls will work in local mode with the release of VS
> 2005 (November).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Mohan" <Mohan@.discussions.microsoft.com> wrote in message
> news:100416CF-2203-4D42-A5D6-2D17328AE7D0@.microsoft.com...
> > 1. We have Thin Client which is connecting to the Sql Express database. Is
> > it
> > possible to use MS Reporting Service in Sql Express database.
> >
> > 2. What are the pre requisites shoule be there in my thin client to see my
> > reports in the thin client.
> >
> >
>
>|||RS 2005 for Express is not available yet even in beta form. The controls are
available with the Visual Studio beta (which is currently release
candidate). The controls are free with VS. No licensing needed to create or
run the report. All is client side, you provide the report, you provide the
dataset. If you need server side and express then you will have to wait
until that combination is released next year. My understanding is that
Express has some other limitations (for instance, I think the data you are
going after has to be on the same box as the report, it doesn't support
cubes, etc).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Mohan" <Mohan@.discussions.microsoft.com> wrote in message
news:422C3A50-41A2-4F0B-94DA-6BE627D0FBAC@.microsoft.com...
> Hi Bruce,
> Thanks for you reply.
> My Requrments is I want to view a report in my thin client(windows
> applicaion). what the pre requisits need in the client applicaion.
> Regards
> Mohan
> "Bruce L-C [MVP]" wrote:
>> SQL Express is not supported for RS 2000. It will be supported for RS
>> 2005
>> with SQL Express but this will be a release after the release of SQL
>> Server
>> 2005. My understanding is sometime in the first half of next year.
>> What is your thin client? You can integrate reporting services multiple
>> ways. You can use URL integration (IE 6 works best). You can use web
>> services. Also, Visual Studio 2005 will have 2 controls, a winform and a
>> webform control. Note that these can work in local mode where no server
>> is
>> required. There are some limitations (for instance you lose some
>> exporting
>> formats, no scheduling etc) but in general pretty fully functional. You
>> give
>> it a dataset and a report. Depending on what you want this might fulfill
>> your needs. In that case Express is just a datasource that you get your
>> dataset from. These controls will work in local mode with the release of
>> VS
>> 2005 (November).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Mohan" <Mohan@.discussions.microsoft.com> wrote in message
>> news:100416CF-2203-4D42-A5D6-2D17328AE7D0@.microsoft.com...
>> > 1. We have Thin Client which is connecting to the Sql Express database.
>> > Is
>> > it
>> > possible to use MS Reporting Service in Sql Express database.
>> >
>> > 2. What are the pre requisites shoule be there in my thin client to see
>> > my
>> > reports in the thin client.
>> >
>> >
>>