Initially, when I started to setup replication I received the error message ~
"one or more articles are published ...", so I issued the following commands
to remove replication settings from the DB:
sp_configure 'allow',1
GO
reconfigure with override
GO
USE ImageCraft
GO
sp_removedbreplication 'IMAGECRAFT'
GO
UPDATE sysobjects set replinfo=0 WHERE replinfo<>0
GO
Drop table MSdynamicsnapshotjobs
Drop table MSdynamicsnapshotviews
Drop table MSmerge_altsyncpartners
Drop table MSmerge_contents
Drop table MSmerge_delete_conflicts
Drop table MSmerge_errorlineage
Drop table MSmerge_genhistory
Drop table MSmerge_replinfo
Drop table MSmerge_tombstone
Drop table MSrepl_identity_range
Drop table sysmergearticles
Drop table sysmergepublications
Drop table sysmergeschemaarticles
Drop table sysmergeschemachange
Drop table sysmergesubscriptions
Drop table sysmergesubsetfilters
GO
sp_configure 'allow',0
GO
reconfigure with override
GO
Appearently, I overkilled it because I get an error message I've never seen
before when adding a table to the replication setup:
SQL Server Enterprise Manager could not initialize an article based on table
'BusinessUnit'.
Error 208: Invalid object name 'sysmergearticles'.
Invalid object name 'sysmergeschemaarticles'.
Invalid object name 'sysmergearticles'.
Invalid object name 'sysmergeschmaarticles'.
Could not use view or function 'sysmergeextendedarticlesview' because of
binding errors.
Could not use view or function 'sysmergeextendedarticlesview' because of
binding errors.
I did a restore on the I am trying to create the replication for, but still
get the same errors.
Any suggestions?
can you disable this database for merge publishing and then try to re-enable
it. Also what version of SQL are you running?
Hilary Cotter
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
"Steven" <Steven@.discussions.microsoft.com> wrote in message
news:1838D345-A23E-4CB6-A122-3736554334BE@.microsoft.com...
> Initially, when I started to setup replication I received the error
> message ~
> "one or more articles are published ...", so I issued the following
> commands
> to remove replication settings from the DB:
> sp_configure 'allow',1
> GO
> reconfigure with override
> GO
> USE ImageCraft
> GO
> sp_removedbreplication 'IMAGECRAFT'
> GO
> UPDATE sysobjects set replinfo=0 WHERE replinfo<>0
> GO
> Drop table MSdynamicsnapshotjobs
> Drop table MSdynamicsnapshotviews
> Drop table MSmerge_altsyncpartners
> Drop table MSmerge_contents
> Drop table MSmerge_delete_conflicts
> Drop table MSmerge_errorlineage
> Drop table MSmerge_genhistory
> Drop table MSmerge_replinfo
> Drop table MSmerge_tombstone
> Drop table MSrepl_identity_range
> Drop table sysmergearticles
> Drop table sysmergepublications
> Drop table sysmergeschemaarticles
> Drop table sysmergeschemachange
> Drop table sysmergesubscriptions
> Drop table sysmergesubsetfilters
> GO
> sp_configure 'allow',0
> GO
> reconfigure with override
> GO
> Appearently, I overkilled it because I get an error message I've never
> seen
> before when adding a table to the replication setup:
> SQL Server Enterprise Manager could not initialize an article based on
> table
> 'BusinessUnit'.
> Error 208: Invalid object name 'sysmergearticles'.
> Invalid object name 'sysmergeschemaarticles'.
> Invalid object name 'sysmergearticles'.
> Invalid object name 'sysmergeschmaarticles'.
> Could not use view or function 'sysmergeextendedarticlesview' because of
> binding errors.
> Could not use view or function 'sysmergeextendedarticlesview' because of
> binding errors.
> I did a restore on the I am trying to create the replication for, but
> still
> get the same errors.
> Any suggestions?
>
|||I tried this, but no success. The system tables required for replication
have been deleted and I'm not sure how to bring them back. This seems to be
crux anyways. Any further thoughts?
"Narayana Vyas Kondreddi" wrote:
> Try this. Using sp_dboption set 'published' and 'merge publish' options to
> false.
> Then from the publisher properties dialog box in enterprise manager, enable
> this database again for replication.
> Then try to setup a publication and see if it works.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Steven" <Steven@.discussions.microsoft.com> wrote in message
> news:1838D345-A23E-4CB6-A122-3736554334BE@.microsoft.com...
>
>
|||I tried this too, but no success. I seem to have deleted the system tables
required for replication and need to bring them back.
"Hilary Cotter" wrote:
> can you disable this database for merge publishing and then try to re-enable
> it. Also what version of SQL are you running?
> --
> Hilary Cotter
> 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
> "Steven" <Steven@.discussions.microsoft.com> wrote in message
> news:1838D345-A23E-4CB6-A122-3736554334BE@.microsoft.com...
>
>
Showing posts with label received. Show all posts
Showing posts with label received. Show all posts
Thursday, March 22, 2012
Wednesday, March 7, 2012
Can't query attached database
Hello.
I received a detached database/log from my client. I attached the
database to my SQLServer 2000 SP3 installation just fine. In the
enterprise manager I can query any table I want.
However, when I attempt to query a table via the query analyzer, it
always fails, even though I am logged in as the "sa".
Below is my query and the result. I am not having this trouble with any
other database on the system.
select * from employee
Below is the error message:
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'employee'.
Any help would be appreciated.
Thanks,
Christian
pariahware@.pariahware.com
Pariahware, Inc. Custom Software and Shareware
http://www.pariahware.com
--
God loved you so much that He gave His only son Jesus.
What have you done with God's gift?Is there really a table called employee? Are you in the right database? Who is the owner of that table?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?|||In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote:
> Is there really a table called employee?
Yes, I can view it in the enterprise manager.
> Are you in the right database?
Yes, I've even used the "use" command to make sure, on occassion.
> Who is the owner of that table?
The owner of the table is "dbo".
When I look under the db's users, "dbo" is a name entry, "sa" is the
login name and access is "permit".|||Try:
SELECT * FROM dbname.dbo.employee. Also, the server might be case-sensitive, make sure you use proper case.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-21E05C.16194316062004@.news2-ge0.southeast.rr.com...
> In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> wrote:
> > Is there really a table called employee?
> Yes, I can view it in the enterprise manager.
> > Are you in the right database?
> Yes, I've even used the "use" command to make sure, on occassion.
> > Who is the owner of that table?
> The owner of the table is "dbo".
> When I look under the db's users, "dbo" is a name entry, "sa" is the
> login name and access is "permit".|||In article
<pariahware-21E05C.16194316062004@.news2-ge0.southeast.rr.com>,
Christian Miller <pariahware@.pariahware.com> wrote:
> In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> wrote:
> > Is there really a table called employee?
> Yes, I can view it in the enterprise manager.
> > Are you in the right database?
> Yes, I've even used the "use" command to make sure, on occassion.
> > Who is the owner of that table?
> The owner of the table is "dbo".
> When I look under the db's users, "dbo" is a name entry, "sa" is the
> login name and access is "permit".
OK, apparently there is not a database table called "employee", but
there is one called "EMPLOYEE". I don't ever remember table name case
being an issue when performing a querying before. I normally uppercase
key words and lowercase table names. Is this a setting in my SQL Server
that I accidentally set?
Thanks,
Christian
pariahware@.pariahware.com
Pariahware, Inc. Custom Software and Shareware
http://www.pariahware.com
--
God loved you so much that He gave His only son Jesus.
What have you done with God's gift?|||Case sensitivity for object names is based on the database collation (if my memory serves me).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-11C0F9.16271516062004@.news2-ge0.southeast.rr.com...
> In article
> <pariahware-21E05C.16194316062004@.news2-ge0.southeast.rr.com>,
> Christian Miller <pariahware@.pariahware.com> wrote:
> > In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
> > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> > wrote:
> >
> > > Is there really a table called employee?
> > Yes, I can view it in the enterprise manager.
> >
> > > Are you in the right database?
> > Yes, I've even used the "use" command to make sure, on occassion.
> >
> > > Who is the owner of that table?
> > The owner of the table is "dbo".
> >
> > When I look under the db's users, "dbo" is a name entry, "sa" is the
> > login name and access is "permit".
> OK, apparently there is not a database table called "employee", but
> there is one called "EMPLOYEE". I don't ever remember table name case
> being an issue when performing a querying before. I normally uppercase
> key words and lowercase table names. Is this a setting in my SQL Server
> that I accidentally set?
>
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?|||In article <u2N$QN#UEHA.2920@.TK2MSFTNGP10.phx.gbl>,
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote:
> Case sensitivity for object names is based on the database collation (if my
> memory serves me).
If that per database file or per server? How would I turn off database
collation if I wanted to? I really appreciate all the help on this.
Thanks,
Christian
pariahware@.pariahware.com
Pariahware, Inc. Custom Software and Shareware
http://www.pariahware.com
--
God loved you so much that He gave His only son Jesus.
What have you done with God's gift?|||Try sp_helpsort to determine the the sort order.
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?
I received a detached database/log from my client. I attached the
database to my SQLServer 2000 SP3 installation just fine. In the
enterprise manager I can query any table I want.
However, when I attempt to query a table via the query analyzer, it
always fails, even though I am logged in as the "sa".
Below is my query and the result. I am not having this trouble with any
other database on the system.
select * from employee
Below is the error message:
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'employee'.
Any help would be appreciated.
Thanks,
Christian
pariahware@.pariahware.com
Pariahware, Inc. Custom Software and Shareware
http://www.pariahware.com
--
God loved you so much that He gave His only son Jesus.
What have you done with God's gift?Is there really a table called employee? Are you in the right database? Who is the owner of that table?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?|||In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote:
> Is there really a table called employee?
Yes, I can view it in the enterprise manager.
> Are you in the right database?
Yes, I've even used the "use" command to make sure, on occassion.
> Who is the owner of that table?
The owner of the table is "dbo".
When I look under the db's users, "dbo" is a name entry, "sa" is the
login name and access is "permit".|||Try:
SELECT * FROM dbname.dbo.employee. Also, the server might be case-sensitive, make sure you use proper case.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-21E05C.16194316062004@.news2-ge0.southeast.rr.com...
> In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> wrote:
> > Is there really a table called employee?
> Yes, I can view it in the enterprise manager.
> > Are you in the right database?
> Yes, I've even used the "use" command to make sure, on occassion.
> > Who is the owner of that table?
> The owner of the table is "dbo".
> When I look under the db's users, "dbo" is a name entry, "sa" is the
> login name and access is "permit".|||In article
<pariahware-21E05C.16194316062004@.news2-ge0.southeast.rr.com>,
Christian Miller <pariahware@.pariahware.com> wrote:
> In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> wrote:
> > Is there really a table called employee?
> Yes, I can view it in the enterprise manager.
> > Are you in the right database?
> Yes, I've even used the "use" command to make sure, on occassion.
> > Who is the owner of that table?
> The owner of the table is "dbo".
> When I look under the db's users, "dbo" is a name entry, "sa" is the
> login name and access is "permit".
OK, apparently there is not a database table called "employee", but
there is one called "EMPLOYEE". I don't ever remember table name case
being an issue when performing a querying before. I normally uppercase
key words and lowercase table names. Is this a setting in my SQL Server
that I accidentally set?
Thanks,
Christian
pariahware@.pariahware.com
Pariahware, Inc. Custom Software and Shareware
http://www.pariahware.com
--
God loved you so much that He gave His only son Jesus.
What have you done with God's gift?|||Case sensitivity for object names is based on the database collation (if my memory serves me).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-11C0F9.16271516062004@.news2-ge0.southeast.rr.com...
> In article
> <pariahware-21E05C.16194316062004@.news2-ge0.southeast.rr.com>,
> Christian Miller <pariahware@.pariahware.com> wrote:
> > In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
> > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> > wrote:
> >
> > > Is there really a table called employee?
> > Yes, I can view it in the enterprise manager.
> >
> > > Are you in the right database?
> > Yes, I've even used the "use" command to make sure, on occassion.
> >
> > > Who is the owner of that table?
> > The owner of the table is "dbo".
> >
> > When I look under the db's users, "dbo" is a name entry, "sa" is the
> > login name and access is "permit".
> OK, apparently there is not a database table called "employee", but
> there is one called "EMPLOYEE". I don't ever remember table name case
> being an issue when performing a querying before. I normally uppercase
> key words and lowercase table names. Is this a setting in my SQL Server
> that I accidentally set?
>
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?|||In article <u2N$QN#UEHA.2920@.TK2MSFTNGP10.phx.gbl>,
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote:
> Case sensitivity for object names is based on the database collation (if my
> memory serves me).
If that per database file or per server? How would I turn off database
collation if I wanted to? I really appreciate all the help on this.
Thanks,
Christian
pariahware@.pariahware.com
Pariahware, Inc. Custom Software and Shareware
http://www.pariahware.com
--
God loved you so much that He gave His only son Jesus.
What have you done with God's gift?|||Try sp_helpsort to determine the the sort order.
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?
Can't query attached database
Hello.
I received a detached database/log from my client. I attached the
database to my SQLServer 2000 SP3 installation just fine. In the
enterprise manager I can query any table I want.
However, when I attempt to query a table via the query analyzer, it
always fails, even though I am logged in as the "sa".
Below is my query and the result. I am not having this trouble with any
other database on the system.
select * from employee
Below is the error message:
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'employee'.
Any help would be appreciated.
Thanks,
Christian
pariahware@.pariahware.com
Pariahware, Inc. Custom Software and Shareware
http://www.pariahware.com
God loved you so much that He gave His only son Jesus.
What have you done with God's gift?
Is there really a table called employee? Are you in the right database? Who is the owner of that table?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?
|||In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote:
> Is there really a table called employee?
Yes, I can view it in the enterprise manager.
> Are you in the right database?
Yes, I've even used the "use" command to make sure, on occassion.
> Who is the owner of that table?
The owner of the table is "dbo".
When I look under the db's users, "dbo" is a name entry, "sa" is the
login name and access is "permit".
|||Try:
SELECT * FROM dbname.dbo.employee. Also, the server might be case-sensitive, make sure you use proper case.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-21E05C.16194316062004@.news2-ge0.southeast.rr.com...
> In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> wrote:
> Yes, I can view it in the enterprise manager.
> Yes, I've even used the "use" command to make sure, on occassion.
> The owner of the table is "dbo".
> When I look under the db's users, "dbo" is a name entry, "sa" is the
> login name and access is "permit".
|||Try sp_helpsort to determine the the sort order.
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?
I received a detached database/log from my client. I attached the
database to my SQLServer 2000 SP3 installation just fine. In the
enterprise manager I can query any table I want.
However, when I attempt to query a table via the query analyzer, it
always fails, even though I am logged in as the "sa".
Below is my query and the result. I am not having this trouble with any
other database on the system.
select * from employee
Below is the error message:
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'employee'.
Any help would be appreciated.
Thanks,
Christian
pariahware@.pariahware.com
Pariahware, Inc. Custom Software and Shareware
http://www.pariahware.com
God loved you so much that He gave His only son Jesus.
What have you done with God's gift?
Is there really a table called employee? Are you in the right database? Who is the owner of that table?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?
|||In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote:
> Is there really a table called employee?
Yes, I can view it in the enterprise manager.
> Are you in the right database?
Yes, I've even used the "use" command to make sure, on occassion.
> Who is the owner of that table?
The owner of the table is "dbo".
When I look under the db's users, "dbo" is a name entry, "sa" is the
login name and access is "permit".
|||Try:
SELECT * FROM dbname.dbo.employee. Also, the server might be case-sensitive, make sure you use proper case.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-21E05C.16194316062004@.news2-ge0.southeast.rr.com...
> In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> wrote:
> Yes, I can view it in the enterprise manager.
> Yes, I've even used the "use" command to make sure, on occassion.
> The owner of the table is "dbo".
> When I look under the db's users, "dbo" is a name entry, "sa" is the
> login name and access is "permit".
|||Try sp_helpsort to determine the the sort order.
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?
Can't query attached database
Hello.
I received a detached database/log from my client. I attached the
database to my SQLServer 2000 SP3 installation just fine. In the
enterprise manager I can query any table I want.
However, when I attempt to query a table via the query analyzer, it
always fails, even though I am logged in as the "sa".
Below is my query and the result. I am not having this trouble with any
other database on the system.
select * from employee
Below is the error message:
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'employee'.
Any help would be appreciated.
Thanks,
Christian
pariahware@.pariahware.com
Pariahware, Inc. Custom Software and Shareware
http://www.pariahware.com
--
God loved you so much that He gave His only son Jesus.
What have you done with God's gift?Is there really a table called employee? Are you in the right database? Who
is the owner of that table?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?|||In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote:
> Is there really a table called employee?
Yes, I can view it in the enterprise manager.
> Are you in the right database?
Yes, I've even used the "use" command to make sure, on occassion.
> Who is the owner of that table?
The owner of the table is "dbo".
When I look under the db's users, "dbo" is a name entry, "sa" is the
login name and access is "permit".|||Try:
SELECT * FROM dbname.dbo.employee. Also, the server might be case-sensitive,
make sure you use proper case.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-21E05C.16194316062004@.news2-ge0.southeast.rr.com...
> In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> wrote:
>
> Yes, I can view it in the enterprise manager.
>
> Yes, I've even used the "use" command to make sure, on occassion.
>
> The owner of the table is "dbo".
> When I look under the db's users, "dbo" is a name entry, "sa" is the
> login name and access is "permit".|||Try sp_helpsort to determine the the sort order.
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?
I received a detached database/log from my client. I attached the
database to my SQLServer 2000 SP3 installation just fine. In the
enterprise manager I can query any table I want.
However, when I attempt to query a table via the query analyzer, it
always fails, even though I am logged in as the "sa".
Below is my query and the result. I am not having this trouble with any
other database on the system.
select * from employee
Below is the error message:
Server: Msg 208, Level 16, State 1, Line 1
Invalid object name 'employee'.
Any help would be appreciated.
Thanks,
Christian
pariahware@.pariahware.com
Pariahware, Inc. Custom Software and Shareware
http://www.pariahware.com
--
God loved you so much that He gave His only son Jesus.
What have you done with God's gift?Is there really a table called employee? Are you in the right database? Who
is the owner of that table?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?|||In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote:
> Is there really a table called employee?
Yes, I can view it in the enterprise manager.
> Are you in the right database?
Yes, I've even used the "use" command to make sure, on occassion.
> Who is the owner of that table?
The owner of the table is "dbo".
When I look under the db's users, "dbo" is a name entry, "sa" is the
login name and access is "permit".|||Try:
SELECT * FROM dbname.dbo.employee. Also, the server might be case-sensitive,
make sure you use proper case.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-21E05C.16194316062004@.news2-ge0.southeast.rr.com...
> In article <uwTZNx9UEHA.1048@.TK2MSFTNGP09.phx.gbl>,
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
> wrote:
>
> Yes, I can view it in the enterprise manager.
>
> Yes, I've even used the "use" command to make sure, on occassion.
>
> The owner of the table is "dbo".
> When I look under the db's users, "dbo" is a name entry, "sa" is the
> login name and access is "permit".|||Try sp_helpsort to determine the the sort order.
"Christian Miller" <pariahware@.pariahware.com> wrote in message
news:pariahware-434093.15550916062004@.news2-ge0.southeast.rr.com...
> Hello.
> I received a detached database/log from my client. I attached the
> database to my SQLServer 2000 SP3 installation just fine. In the
> enterprise manager I can query any table I want.
> However, when I attempt to query a table via the query analyzer, it
> always fails, even though I am logged in as the "sa".
> Below is my query and the result. I am not having this trouble with any
> other database on the system.
> select * from employee
> Below is the error message:
> Server: Msg 208, Level 16, State 1, Line 1
> Invalid object name 'employee'.
> Any help would be appreciated.
> Thanks,
> Christian
> pariahware@.pariahware.com
> Pariahware, Inc. Custom Software and Shareware
> http://www.pariahware.com
> --
> God loved you so much that He gave His only son Jesus.
> What have you done with God's gift?
Friday, February 24, 2012
Can't manage SQL
I have a SQL Server running on a new W2k3 Server, and a user that received
the Sys Admin roles at this SQL Server. However, this user can't access this
SQL Server using the Service Manager nor stop/pause this server. The others
operations, suck as creating a new DB is ok for this group. Any help?
the error that i get is "error 5 (acess denied)"
thanks
NunoThe starting and stopping of a Server Service has nothing
to do with SQL and everything to do with the W2k3 roles.
So the problem here is your user does not have access
rights to stop the service as the W2k3 role will not let
them.
Have a chat to your server guys.
Peter
"Action speaks louder than words but not nearly as often"
Mark Twain
>--Original Message--
>I have a SQL Server running on a new W2k3 Server, and a
user that received
>the Sys Admin roles at this SQL Server. However, this
user can't access this
>SQL Server using the Service Manager nor stop/pause this
server. The others
>operations, suck as creating a new DB is ok for this
group. Any help?
>the error that i get is "error 5 (acess denied)"
>thanks
>Nuno
>.
>|||Hi,
To start any of the windows service user should be in Administrator or Power
user group. A login with SYSADMIN role can do
all the stuffs inside the SQL Server layer only not in Operating system side.
Note:
But the SQL Server Trusted users who fall in Admin group or power users
group can start and stop SQL server service.
Thanks
Hari
MCDBA
"Nuno" wrote:
> I have a SQL Server running on a new W2k3 Server, and a user that received
> the Sys Admin roles at this SQL Server. However, this user can't access this
> SQL Server using the Service Manager nor stop/pause this server. The others
> operations, suck as creating a new DB is ok for this group. Any help?
> the error that i get is "error 5 (acess denied)"
> thanks
> Nuno
>|||Without giving users total admin control to access (stop/start services) i
believe you can add the users to the print operators group. This would
achieve the results you are looking for.
"Hari Prasad" wrote:
> Hi,
> To start any of the windows service user should be in Administrator or Power
> user group. A login with SYSADMIN role can do
> all the stuffs inside the SQL Server layer only not in Operating system side.
> Note:
> But the SQL Server Trusted users who fall in Admin group or power users
> group can start and stop SQL server service.
> Thanks
> Hari
> MCDBA
> "Nuno" wrote:
> > I have a SQL Server running on a new W2k3 Server, and a user that received
> > the Sys Admin roles at this SQL Server. However, this user can't access this
> > SQL Server using the Service Manager nor stop/pause this server. The others
> > operations, suck as creating a new DB is ok for this group. Any help?
> >
> > the error that i get is "error 5 (acess denied)"
> >
> > thanks
> >
> > Nuno
> >
the Sys Admin roles at this SQL Server. However, this user can't access this
SQL Server using the Service Manager nor stop/pause this server. The others
operations, suck as creating a new DB is ok for this group. Any help?
the error that i get is "error 5 (acess denied)"
thanks
NunoThe starting and stopping of a Server Service has nothing
to do with SQL and everything to do with the W2k3 roles.
So the problem here is your user does not have access
rights to stop the service as the W2k3 role will not let
them.
Have a chat to your server guys.
Peter
"Action speaks louder than words but not nearly as often"
Mark Twain
>--Original Message--
>I have a SQL Server running on a new W2k3 Server, and a
user that received
>the Sys Admin roles at this SQL Server. However, this
user can't access this
>SQL Server using the Service Manager nor stop/pause this
server. The others
>operations, suck as creating a new DB is ok for this
group. Any help?
>the error that i get is "error 5 (acess denied)"
>thanks
>Nuno
>.
>|||Hi,
To start any of the windows service user should be in Administrator or Power
user group. A login with SYSADMIN role can do
all the stuffs inside the SQL Server layer only not in Operating system side.
Note:
But the SQL Server Trusted users who fall in Admin group or power users
group can start and stop SQL server service.
Thanks
Hari
MCDBA
"Nuno" wrote:
> I have a SQL Server running on a new W2k3 Server, and a user that received
> the Sys Admin roles at this SQL Server. However, this user can't access this
> SQL Server using the Service Manager nor stop/pause this server. The others
> operations, suck as creating a new DB is ok for this group. Any help?
> the error that i get is "error 5 (acess denied)"
> thanks
> Nuno
>|||Without giving users total admin control to access (stop/start services) i
believe you can add the users to the print operators group. This would
achieve the results you are looking for.
"Hari Prasad" wrote:
> Hi,
> To start any of the windows service user should be in Administrator or Power
> user group. A login with SYSADMIN role can do
> all the stuffs inside the SQL Server layer only not in Operating system side.
> Note:
> But the SQL Server Trusted users who fall in Admin group or power users
> group can start and stop SQL server service.
> Thanks
> Hari
> MCDBA
> "Nuno" wrote:
> > I have a SQL Server running on a new W2k3 Server, and a user that received
> > the Sys Admin roles at this SQL Server. However, this user can't access this
> > SQL Server using the Service Manager nor stop/pause this server. The others
> > operations, suck as creating a new DB is ok for this group. Any help?
> >
> > the error that i get is "error 5 (acess denied)"
> >
> > thanks
> >
> > Nuno
> >
Can't manage a remote SQL Server
I have a SQL Server running on a new W2k3 Server, and a group in the AD
received the Sys Admin roles at this SQL Server. However, this members can't
access this SQL Server using the Service Manager nor stop/pause this server.
The others operations, suck as creating a new DB is ok for this group. Any
help?What is the exact error message they get?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
received the Sys Admin roles at this SQL Server. However, this members can't
access this SQL Server using the Service Manager nor stop/pause this server.
The others operations, suck as creating a new DB is ok for this group. Any
help?What is the exact error message they get?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Subscribe to:
Posts (Atom)