Hello
I am coming from Sybase and are learning SQL-Server now.
In Sybase there is a feature called "proxy table" which makes it possible to create a proxy table that really exists in another database. But it appears a ordinary local table to a user. Does a similar feature exists in SQL-server? Anyone knows?
Thanks
Per
Per,
No, but you can fully qualify the object in the other database to access
it. i.e.
select * from database2.dbo.objectname
You will need the appropriate permissions on the other object.
You may also wish to look at cross-database ownership chaining in the
updated Books online available from www.microsoft.com/sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Per wrote:
> Hello
> I am coming from Sybase and are learning SQL-Server now.
> In Sybase there is a feature called "proxy table" which makes it possible to create a proxy table that really exists in another database. But it appears a ordinary local table to a user. Does a similar feature exists in SQL-server? Anyone knows?
> Thanks
> Per
|||Hi
To add to Marks post...you can also create a view in the "current" database.
That would mean that the three part name is only require in the view
definition.
John
"Per" <anonymous@.discussions.microsoft.com> wrote in message
news:CD9FFDA6-BCE1-4D83-8960-1D612462424D@.microsoft.com...
> Hello
> I am coming from Sybase and are learning SQL-Server now.
> In Sybase there is a feature called "proxy table" which makes it possible
to create a proxy table that really exists in another database. But it
appears a ordinary local table to a user. Does a similar feature exists in
SQL-server? Anyone knows?
> Thanks
> Per
Showing posts with label feature. Show all posts
Showing posts with label feature. Show all posts
Wednesday, March 28, 2012
Is it possible to make "proxy tables" win SQL-server 2000?
Hello
I am coming from Sybase and are learning SQL-Server now.
In Sybase there is a feature called "proxy table" which makes it possible to
create a proxy table that really exists in another database. But it appears
a ordinary local table to a user. Does a similar feature exists in SQL-serv
er? Anyone knows?
Thanks
PerPer,
No, but you can fully qualify the object in the other database to access
it. i.e.
select * from database2.dbo.objectname
You will need the appropriate permissions on the other object.
You may also wish to look at cross-database ownership chaining in the
updated Books online available from www.microsoft.com/sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Per wrote:
> Hello
> I am coming from Sybase and are learning SQL-Server now.
> In Sybase there is a feature called "proxy table" which makes it possible
to create a proxy table that really exists in another database. But it appea
rs a ordinary local table to a user. Does a similar feature exists in SQL-se
rver? Anyone knows?
> Thanks
> Per|||Hi
To add to Marks post...you can also create a view in the "current" database.
That would mean that the three part name is only require in the view
definition.
John
"Per" <anonymous@.discussions.microsoft.com> wrote in message
news:CD9FFDA6-BCE1-4D83-8960-1D612462424D@.microsoft.com...
> Hello
> I am coming from Sybase and are learning SQL-Server now.
> In Sybase there is a feature called "proxy table" which makes it possible
to create a proxy table that really exists in another database. But it
appears a ordinary local table to a user. Does a similar feature exists in
SQL-server? Anyone knows?
> Thanks
> Per
I am coming from Sybase and are learning SQL-Server now.
In Sybase there is a feature called "proxy table" which makes it possible to
create a proxy table that really exists in another database. But it appears
a ordinary local table to a user. Does a similar feature exists in SQL-serv
er? Anyone knows?
Thanks
PerPer,
No, but you can fully qualify the object in the other database to access
it. i.e.
select * from database2.dbo.objectname
You will need the appropriate permissions on the other object.
You may also wish to look at cross-database ownership chaining in the
updated Books online available from www.microsoft.com/sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Per wrote:
> Hello
> I am coming from Sybase and are learning SQL-Server now.
> In Sybase there is a feature called "proxy table" which makes it possible
to create a proxy table that really exists in another database. But it appea
rs a ordinary local table to a user. Does a similar feature exists in SQL-se
rver? Anyone knows?
> Thanks
> Per|||Hi
To add to Marks post...you can also create a view in the "current" database.
That would mean that the three part name is only require in the view
definition.
John
"Per" <anonymous@.discussions.microsoft.com> wrote in message
news:CD9FFDA6-BCE1-4D83-8960-1D612462424D@.microsoft.com...
> Hello
> I am coming from Sybase and are learning SQL-Server now.
> In Sybase there is a feature called "proxy table" which makes it possible
to create a proxy table that really exists in another database. But it
appears a ordinary local table to a user. Does a similar feature exists in
SQL-server? Anyone knows?
> Thanks
> Per
Friday, February 24, 2012
Is DB Mirroring supported in SQL 2005?
I just read the follwing statement in the help file.
Important:
Microsoft support policies do not apply to the database mirroring feature in
SQL Server 2005. Database mirroring is currently disabled by default, but may
be enabled for evaluation purposes only by using trace flag 1400 as a startup
parameter. (For more information about trace flags, see Trace Flags
(Transact-SQL).) Database mirroring should not be used in production
environments, and Microsoft support services will not support databases or
applications that use database mirroring. Database mirroring documentation is
included in SQL Server 2005 for evaluation purposes only, and the
Documentation Policy for SQL Server 2005 Support and Upgrade does not apply
to the database mirroring documentation.
I know that mirroring wasn't available in the original release, but was
available after installing sp1, which I have installed. Is it supported and
safe to use?
Another question I have is, If a snapshot is created off the mirror, which
is on a seperate server from production, and mirroring with high protection
is being used, is it possible for a long running report to cause performance
issues on the prod server? Or could the report prevent the mirror from
getting updated?
Thanks
--
MG>I just read the follwing statement in the help file.
When you upgraded your server to SP1, did you also install the updated Books
Online documentation? The help files are updated frequently. The most
recent official release is July 2006:
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
But if you want the most recent copy (including some information on SP2) you
can get it here:
http://www.microsoft.com/downloads/details.aspx?familyid=19db0b42-a5b2-456f-9c5c-f295cdd58d7a
A|||Thanks
I only installed sp1, but not the updated documentation.
--
MG
"Aaron Bertrand [SQL Server MVP]" wrote:
> >I just read the follwing statement in the help file.
> When you upgraded your server to SP1, did you also install the updated Books
> Online documentation? The help files are updated frequently. The most
> recent official release is July 2006:
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> But if you want the most recent copy (including some information on SP2) you
> can get it here:
> http://www.microsoft.com/downloads/details.aspx?familyid=19db0b42-a5b2-456f-9c5c-f295cdd58d7a
> A
>
>
Important:
Microsoft support policies do not apply to the database mirroring feature in
SQL Server 2005. Database mirroring is currently disabled by default, but may
be enabled for evaluation purposes only by using trace flag 1400 as a startup
parameter. (For more information about trace flags, see Trace Flags
(Transact-SQL).) Database mirroring should not be used in production
environments, and Microsoft support services will not support databases or
applications that use database mirroring. Database mirroring documentation is
included in SQL Server 2005 for evaluation purposes only, and the
Documentation Policy for SQL Server 2005 Support and Upgrade does not apply
to the database mirroring documentation.
I know that mirroring wasn't available in the original release, but was
available after installing sp1, which I have installed. Is it supported and
safe to use?
Another question I have is, If a snapshot is created off the mirror, which
is on a seperate server from production, and mirroring with high protection
is being used, is it possible for a long running report to cause performance
issues on the prod server? Or could the report prevent the mirror from
getting updated?
Thanks
--
MG>I just read the follwing statement in the help file.
When you upgraded your server to SP1, did you also install the updated Books
Online documentation? The help files are updated frequently. The most
recent official release is July 2006:
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
But if you want the most recent copy (including some information on SP2) you
can get it here:
http://www.microsoft.com/downloads/details.aspx?familyid=19db0b42-a5b2-456f-9c5c-f295cdd58d7a
A|||Thanks
I only installed sp1, but not the updated documentation.
--
MG
"Aaron Bertrand [SQL Server MVP]" wrote:
> >I just read the follwing statement in the help file.
> When you upgraded your server to SP1, did you also install the updated Books
> Online documentation? The help files are updated frequently. The most
> recent official release is July 2006:
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> But if you want the most recent copy (including some information on SP2) you
> can get it here:
> http://www.microsoft.com/downloads/details.aspx?familyid=19db0b42-a5b2-456f-9c5c-f295cdd58d7a
> A
>
>
Is DB Mirroring supported in SQL 2005?
I just read the follwing statement in the help file.
Important:
Microsoft support policies do not apply to the database mirroring feature in
SQL Server 2005. Database mirroring is currently disabled by default, but may
be enabled for evaluation purposes only by using trace flag 1400 as a startup
parameter. (For more information about trace flags, see Trace Flags
(Transact-SQL).) Database mirroring should not be used in production
environments, and Microsoft support services will not support databases or
applications that use database mirroring. Database mirroring documentation is
included in SQL Server 2005 for evaluation purposes only, and the
Documentation Policy for SQL Server 2005 Support and Upgrade does not apply
to the database mirroring documentation.
I know that mirroring wasn't available in the original release, but was
available after installing sp1, which I have installed. Is it supported and
safe to use?
Another question I have is, If a snapshot is created off the mirror, which
is on a seperate server from production, and mirroring with high protection
is being used, is it possible for a long running report to cause performance
issues on the prod server? Or could the report prevent the mirror from
getting updated?
Thanks
MG
>I just read the follwing statement in the help file.
When you upgraded your server to SP1, did you also install the updated Books
Online documentation? The help files are updated frequently. The most
recent official release is July 2006:
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
But if you want the most recent copy (including some information on SP2) you
can get it here:
http://www.microsoft.com/downloads/details.aspx?familyid=19db0b42-a5b2-456f-9c5c-f295cdd58d7a
A
|||Thanks
I only installed sp1, but not the updated documentation.
MG
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you upgraded your server to SP1, did you also install the updated Books
> Online documentation? The help files are updated frequently. The most
> recent official release is July 2006:
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> But if you want the most recent copy (including some information on SP2) you
> can get it here:
> http://www.microsoft.com/downloads/details.aspx?familyid=19db0b42-a5b2-456f-9c5c-f295cdd58d7a
> A
>
>
Important:
Microsoft support policies do not apply to the database mirroring feature in
SQL Server 2005. Database mirroring is currently disabled by default, but may
be enabled for evaluation purposes only by using trace flag 1400 as a startup
parameter. (For more information about trace flags, see Trace Flags
(Transact-SQL).) Database mirroring should not be used in production
environments, and Microsoft support services will not support databases or
applications that use database mirroring. Database mirroring documentation is
included in SQL Server 2005 for evaluation purposes only, and the
Documentation Policy for SQL Server 2005 Support and Upgrade does not apply
to the database mirroring documentation.
I know that mirroring wasn't available in the original release, but was
available after installing sp1, which I have installed. Is it supported and
safe to use?
Another question I have is, If a snapshot is created off the mirror, which
is on a seperate server from production, and mirroring with high protection
is being used, is it possible for a long running report to cause performance
issues on the prod server? Or could the report prevent the mirror from
getting updated?
Thanks
MG
>I just read the follwing statement in the help file.
When you upgraded your server to SP1, did you also install the updated Books
Online documentation? The help files are updated frequently. The most
recent official release is July 2006:
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
But if you want the most recent copy (including some information on SP2) you
can get it here:
http://www.microsoft.com/downloads/details.aspx?familyid=19db0b42-a5b2-456f-9c5c-f295cdd58d7a
A
|||Thanks
I only installed sp1, but not the updated documentation.
MG
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you upgraded your server to SP1, did you also install the updated Books
> Online documentation? The help files are updated frequently. The most
> recent official release is July 2006:
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> But if you want the most recent copy (including some information on SP2) you
> can get it here:
> http://www.microsoft.com/downloads/details.aspx?familyid=19db0b42-a5b2-456f-9c5c-f295cdd58d7a
> A
>
>
Is DB Mirroring supported in SQL 2005?
I just read the follwing statement in the help file.
Important:
Microsoft support policies do not apply to the database mirroring feature in
SQL Server 2005. Database mirroring is currently disabled by default, but ma
y
be enabled for evaluation purposes only by using trace flag 1400 as a startu
p
parameter. (For more information about trace flags, see Trace Flags
(Transact-SQL).) Database mirroring should not be used in production
environments, and Microsoft support services will not support databases or
applications that use database mirroring. Database mirroring documentation i
s
included in SQL Server 2005 for evaluation purposes only, and the
Documentation Policy for SQL Server 2005 Support and Upgrade does not apply
to the database mirroring documentation.
I know that mirroring wasn't available in the original release, but was
available after installing sp1, which I have installed. Is it supported and
safe to use?
Another question I have is, If a snapshot is created off the mirror, which
is on a seperate server from production, and mirroring with high protection
is being used, is it possible for a long running report to cause performance
issues on the prod server? Or could the report prevent the mirror from
getting updated?
Thanks
--
MG>I just read the follwing statement in the help file.
When you upgraded your server to SP1, did you also install the updated Books
Online documentation? The help files are updated frequently. The most
recent official release is July 2006:
http://www.microsoft.com/technet/pr...oads/books.mspx
But if you want the most recent copy (including some information on SP2) you
can get it here:
http://www.microsoft.com/downloads/.../>
295cdd58d7a
A|||Thanks
I only installed sp1, but not the updated documentation.
--
MG
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you upgraded your server to SP1, did you also install the updated Boo
ks
> Online documentation? The help files are updated frequently. The most
> recent official release is July 2006:
> http://www.microsoft.com/technet/pr...oads/books.mspx
> But if you want the most recent copy (including some information on SP2) y
ou
> can get it here:
> http://www.microsoft.com/downloads/...
-f295cdd58d7a
> A
>
>
Important:
Microsoft support policies do not apply to the database mirroring feature in
SQL Server 2005. Database mirroring is currently disabled by default, but ma
y
be enabled for evaluation purposes only by using trace flag 1400 as a startu
p
parameter. (For more information about trace flags, see Trace Flags
(Transact-SQL).) Database mirroring should not be used in production
environments, and Microsoft support services will not support databases or
applications that use database mirroring. Database mirroring documentation i
s
included in SQL Server 2005 for evaluation purposes only, and the
Documentation Policy for SQL Server 2005 Support and Upgrade does not apply
to the database mirroring documentation.
I know that mirroring wasn't available in the original release, but was
available after installing sp1, which I have installed. Is it supported and
safe to use?
Another question I have is, If a snapshot is created off the mirror, which
is on a seperate server from production, and mirroring with high protection
is being used, is it possible for a long running report to cause performance
issues on the prod server? Or could the report prevent the mirror from
getting updated?
Thanks
--
MG>I just read the follwing statement in the help file.
When you upgraded your server to SP1, did you also install the updated Books
Online documentation? The help files are updated frequently. The most
recent official release is July 2006:
http://www.microsoft.com/technet/pr...oads/books.mspx
But if you want the most recent copy (including some information on SP2) you
can get it here:
http://www.microsoft.com/downloads/.../>
295cdd58d7a
A|||Thanks
I only installed sp1, but not the updated documentation.
--
MG
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you upgraded your server to SP1, did you also install the updated Boo
ks
> Online documentation? The help files are updated frequently. The most
> recent official release is July 2006:
> http://www.microsoft.com/technet/pr...oads/books.mspx
> But if you want the most recent copy (including some information on SP2) y
ou
> can get it here:
> http://www.microsoft.com/downloads/...
-f295cdd58d7a
> A
>
>
Subscribe to:
Posts (Atom)