We have a SQL 2000 server running Enterprise Edition. We also have a separate machine running SQL 2000, Standard edition. We then detached the database from the Enterprise server, copied the MDF and LDF files to the Standard server and reattached. Currently, a program running on the Standard Edition server is returning an error message when trying to access "systables". The questions are as follows:
1) is this error a result of the copy process?
2) is this a recoverable error, and if so, how?
3) are there any other problems and side-effects of which we need to be aware?I have moved databases between Standard and Enterprise several times before, and not had this issue, so it can be done. Without any other information, I can only guess as to why this is happening, but here is my guess:
The user-account being used by the program that is throwing the error probably has a different default database setting than on the Enterprise version. In other words, UserX on the Enterprise server probably has a default database pointing to the application database, and on the Standard edition has a default database of something like Master.
This would cause a problem in implicit database references. If the program issues a command like SELECT * FROM systables, thinking it is going to automatically be pointing to the application database, but is actually pointing to something else, it will not be able to find systables. The proper syntax for the query would explicitly state the table name SELECT * FROM [dbname].dbo.systables, in which case the default database setting of the user would not affect the code.|||The default database for the user is the same on both servers. Any other ideas? Is there any other information I could give that might be of assistance?
Originally posted by bpdWork
I have moved databases between Standard and Enterprise several times before, and not had this issue, so it can be done. Without any other information, I can only guess as to why this is happening, but here is my guess:
The user-account being used by the program that is throwing the error probably has a different default database setting than on the Enterprise version. In other words, UserX on the Enterprise server probably has a default database pointing to the application database, and on the Standard edition has a default database of something like Master.
This would cause a problem in implicit database references. If the program issues a command like SELECT * FROM systables, thinking it is going to automatically be pointing to the application database, but is actually pointing to something else, it will not be able to find systables. The proper syntax for the query would explicitly state the table name SELECT * FROM [dbname].dbo.systables, in which case the default database setting of the user would not affect the code.|||1) Are you sure the database you moved has the table systables, and that it is not in a different database?
2) Does the user account being used by the application have SELECT (etc) permissions for the table?
The exact error message might be helpful.|||check the service pack level|||We've found the issue. Basically, an error was made during the installation of the software. To everyone, thanks for the help.
Showing posts with label separate. Show all posts
Showing posts with label separate. Show all posts
Monday, March 26, 2012
Enterprise or Standard? Infinite Clickthrough??
We are going to separate reporting services from our database server by
putting RS on a single separate server. We need to know if we can use
Standard or if we have to purchase Enterprise. We have Enterprise for our DB
server. The major differences between the 2 editions are data driven
subscriptions, which we do not need at this time, and infinite clickthrough.
I cannot find a good definition of infinite clickthrough. We have reports
that navigate to other reports. In Standard, is some clickthrough still
available but only up to a certain number of clicks?
Any details would really be appreciated.
StephanieI searched a little on this because I run with Standard and I've never come
up across this limitation. I found out the reason for why I have never
noticed it. It has to do with Report Builder (which I do not use). Here is a
posting by a Program Manager for RS:
>>>>>>>>>>
Infinte Clickthrough is a feature of Report Builder. It allows you to
automatically drill between reports by using the relationships between
entities in the Report Model. The drillthroughs are created "on the fly"
without having to build them beforehand. Workgroup and standard edition only
get pre-defined drillthroughs.
----
Brian Welcker, Microsoft
>>>>>>>>>
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
news:2CAC3038-95EA-4D0D-9E84-8EDE1DE24D8A@.microsoft.com...
> We are going to separate reporting services from our database server by
> putting RS on a single separate server. We need to know if we can use
> Standard or if we have to purchase Enterprise. We have Enterprise for our
> DB
> server. The major differences between the 2 editions are data driven
> subscriptions, which we do not need at this time, and infinite
> clickthrough.
> I cannot find a good definition of infinite clickthrough. We have reports
> that navigate to other reports. In Standard, is some clickthrough still
> available but only up to a certain number of clicks?
> Any details would really be appreciated.
> Stephanie|||Bruce,
Thanks for the quick response. I read that article, too, and still was a
bit confused. I do not use Report Builder either. I do, however, have
navigation set up to jump from one report to another.
Is it your opinion as well that I should be able to run Reporting Services
Standard Edition on a separate server and still have the ability to use the
Navigation tab and jump from one report to another? If so, would there be a
limit on the number of jumps I can execute? I have a call in to MS but I am
looking for any feedback as well. The cost difference is enough to warrant
some research.
Stephanie
"Bruce L-C [MVP]" wrote:
> I searched a little on this because I run with Standard and I've never come
> up across this limitation. I found out the reason for why I have never
> noticed it. It has to do with Report Builder (which I do not use). Here is a
> posting by a Program Manager for RS:
> >>>>>>>>>>
> Infinte Clickthrough is a feature of Report Builder. It allows you to
> automatically drill between reports by using the relationships between
> entities in the Report Model. The drillthroughs are created "on the fly"
> without having to build them beforehand. Workgroup and standard edition only
> get pre-defined drillthroughs.
>
> ----
> Brian Welcker, Microsoft
> >>>>>>>>>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
>
>
>
> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
> news:2CAC3038-95EA-4D0D-9E84-8EDE1DE24D8A@.microsoft.com...
> > We are going to separate reporting services from our database server by
> > putting RS on a single separate server. We need to know if we can use
> > Standard or if we have to purchase Enterprise. We have Enterprise for our
> > DB
> > server. The major differences between the 2 editions are data driven
> > subscriptions, which we do not need at this time, and infinite
> > clickthrough.
> > I cannot find a good definition of infinite clickthrough. We have reports
> > that navigate to other reports. In Standard, is some clickthrough still
> > available but only up to a certain number of clicks?
> >
> > Any details would really be appreciated.
> >
> > Stephanie
>
>|||I think it was pretty clear that the infinite clickthrough was a report
builder feature. I run standard and have lots of drill through (that is what
jump to report is called). If there is a limit I have not seen it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
news:7DE14E7D-779B-4068-943B-69BA1D726A51@.microsoft.com...
> Bruce,
> Thanks for the quick response. I read that article, too, and still was a
> bit confused. I do not use Report Builder either. I do, however, have
> navigation set up to jump from one report to another.
> Is it your opinion as well that I should be able to run Reporting Services
> Standard Edition on a separate server and still have the ability to use
> the
> Navigation tab and jump from one report to another? If so, would there be
> a
> limit on the number of jumps I can execute? I have a call in to MS but I
> am
> looking for any feedback as well. The cost difference is enough to
> warrant
> some research.
> Stephanie
> "Bruce L-C [MVP]" wrote:
>> I searched a little on this because I run with Standard and I've never
>> come
>> up across this limitation. I found out the reason for why I have never
>> noticed it. It has to do with Report Builder (which I do not use). Here
>> is a
>> posting by a Program Manager for RS:
>> >>>>>>>>>>
>> Infinte Clickthrough is a feature of Report Builder. It allows you
>> to
>> automatically drill between reports by using the relationships between
>> entities in the Report Model. The drillthroughs are created "on the fly"
>> without having to build them beforehand. Workgroup and standard edition
>> only
>> get pre-defined drillthroughs.
>>
>> ----
>> Brian Welcker, Microsoft
>> >>>>>>>>>
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>>
>>
>>
>> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
>> news:2CAC3038-95EA-4D0D-9E84-8EDE1DE24D8A@.microsoft.com...
>> > We are going to separate reporting services from our database server by
>> > putting RS on a single separate server. We need to know if we can use
>> > Standard or if we have to purchase Enterprise. We have Enterprise for
>> > our
>> > DB
>> > server. The major differences between the 2 editions are data driven
>> > subscriptions, which we do not need at this time, and infinite
>> > clickthrough.
>> > I cannot find a good definition of infinite clickthrough. We have
>> > reports
>> > that navigate to other reports. In Standard, is some clickthrough
>> > still
>> > available but only up to a certain number of clicks?
>> >
>> > Any details would really be appreciated.
>> >
>> > Stephanie
>>|||First of all, SSRS is bundled with SQL Server for free. If you have
SQL Enterprise 2005 then you have all the SSRS enterprise features,
including clickthrough reporting.
Infinite Clickthrough is indeed a feature of Report Builder. If you
have a Report Model created for your database, what this allows is
dynamic ad-hoc reports generated by SSRS itself. Basically it allows
you to drill-down indefinitely with the Report Builder dynamically
creating reports which are based off of the fields and relationships
on your database from the Report Model.
Basically, if the report your looking at references data that has a
relationship to another table, those fields will be hyperlinks. If
you click on the hyperlink SSRS will create a report based on the
table refereced by the link you clicked on. This can be done
indefinitely, like a virtual tour of your database. So, for example,
from a customer report you can click on their order total to see a
report showing their orders, from there you can click on a particular
order's details to see the actual items ordered, from there you can
click on a line item to see the item's general details, from there you
can click on the last PO for the item, etc.
You can always create your own reports that you drill-through. There
is no limit to how many of these manual reports you can create or
drill-through. The difference is SSRS will actually do all this for
you if you have Enterprise. This seems like a really basic feature
since all the infrastructure is in place with SSRS standard. We would
like to take advantage of clickthrough reporting but we don't have
enterprise. The cost to upgrade is pretty astronomical for this
feature.|||Thanks for the description.
Just a little clarification of why this matters to the person who posted.
They are putting RS on a different server than the database. It is not free
in that case. You have to have a license for each machine that RS is
installed on. So let's say you have a web farm (which required enterprise).
For each server on the web farm that has RS installed you need an enterprise
license on that server.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Matt Penner" <mattpenner2007@.gmail.com> wrote in message
news:1194451200.927016.283220@.z24g2000prh.googlegroups.com...
> First of all, SSRS is bundled with SQL Server for free. If you have
> SQL Enterprise 2005 then you have all the SSRS enterprise features,
> including clickthrough reporting.
> Infinite Clickthrough is indeed a feature of Report Builder. If you
> have a Report Model created for your database, what this allows is
> dynamic ad-hoc reports generated by SSRS itself. Basically it allows
> you to drill-down indefinitely with the Report Builder dynamically
> creating reports which are based off of the fields and relationships
> on your database from the Report Model.
> Basically, if the report your looking at references data that has a
> relationship to another table, those fields will be hyperlinks. If
> you click on the hyperlink SSRS will create a report based on the
> table refereced by the link you clicked on. This can be done
> indefinitely, like a virtual tour of your database. So, for example,
> from a customer report you can click on their order total to see a
> report showing their orders, from there you can click on a particular
> order's details to see the actual items ordered, from there you can
> click on a line item to see the item's general details, from there you
> can click on the last PO for the item, etc.
> You can always create your own reports that you drill-through. There
> is no limit to how many of these manual reports you can create or
> drill-through. The difference is SSRS will actually do all this for
> you if you have Enterprise. This seems like a really basic feature
> since all the infrastructure is in place with SSRS standard. We would
> like to take advantage of clickthrough reporting but we don't have
> enterprise. The cost to upgrade is pretty astronomical for this
> feature.
>|||First of all, SSRS is bundled with SQL Server for free. If you have
SQL Enterprise 2005 then you have all the SSRS enterprise features,
including clickthrough reporting.
Infinite Clickthrough is indeed a feature of Report Builder. If you
have a Report Model created for your database, what this allows is
dynamic ad-hoc reports generated by SSRS itself. Basically it allows
you to drill-down indefinitely with the Report Builder dynamically
creating reports which are based off of the fields and relationships
on your database from the Report Model.
Basically, if the report your looking at references data that has a
relationship to another table, those fields will be hyperlinks. If
you click on the hyperlink SSRS will create a report based on the
table refereced by the link you clicked on. This can be done
indefinitely, like a virtual tour of your database. So, for example,
from a customer report you can click on their order total to see a
report showing their orders, from there you can click on a particular
order's details to see the actual items ordered, from there you can
click on a line item to see the item's general details, from there you
can click on the last PO for the item, etc.
You can always create your own reports that you drill-through. There
is no limit to how many of these manual reports you can create or
drill-through. The difference is SSRS will actually do all this for
you if you have Enterprise. This seems like a really basic feature
since all the infrastructure is in place with SSRS standard. We would
like to take advantage of clickthrough reporting but we don't have
enterprise. The cost to upgrade is pretty astronomical for this
feature.
putting RS on a single separate server. We need to know if we can use
Standard or if we have to purchase Enterprise. We have Enterprise for our DB
server. The major differences between the 2 editions are data driven
subscriptions, which we do not need at this time, and infinite clickthrough.
I cannot find a good definition of infinite clickthrough. We have reports
that navigate to other reports. In Standard, is some clickthrough still
available but only up to a certain number of clicks?
Any details would really be appreciated.
StephanieI searched a little on this because I run with Standard and I've never come
up across this limitation. I found out the reason for why I have never
noticed it. It has to do with Report Builder (which I do not use). Here is a
posting by a Program Manager for RS:
>>>>>>>>>>
Infinte Clickthrough is a feature of Report Builder. It allows you to
automatically drill between reports by using the relationships between
entities in the Report Model. The drillthroughs are created "on the fly"
without having to build them beforehand. Workgroup and standard edition only
get pre-defined drillthroughs.
----
Brian Welcker, Microsoft
>>>>>>>>>
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
news:2CAC3038-95EA-4D0D-9E84-8EDE1DE24D8A@.microsoft.com...
> We are going to separate reporting services from our database server by
> putting RS on a single separate server. We need to know if we can use
> Standard or if we have to purchase Enterprise. We have Enterprise for our
> DB
> server. The major differences between the 2 editions are data driven
> subscriptions, which we do not need at this time, and infinite
> clickthrough.
> I cannot find a good definition of infinite clickthrough. We have reports
> that navigate to other reports. In Standard, is some clickthrough still
> available but only up to a certain number of clicks?
> Any details would really be appreciated.
> Stephanie|||Bruce,
Thanks for the quick response. I read that article, too, and still was a
bit confused. I do not use Report Builder either. I do, however, have
navigation set up to jump from one report to another.
Is it your opinion as well that I should be able to run Reporting Services
Standard Edition on a separate server and still have the ability to use the
Navigation tab and jump from one report to another? If so, would there be a
limit on the number of jumps I can execute? I have a call in to MS but I am
looking for any feedback as well. The cost difference is enough to warrant
some research.
Stephanie
"Bruce L-C [MVP]" wrote:
> I searched a little on this because I run with Standard and I've never come
> up across this limitation. I found out the reason for why I have never
> noticed it. It has to do with Report Builder (which I do not use). Here is a
> posting by a Program Manager for RS:
> >>>>>>>>>>
> Infinte Clickthrough is a feature of Report Builder. It allows you to
> automatically drill between reports by using the relationships between
> entities in the Report Model. The drillthroughs are created "on the fly"
> without having to build them beforehand. Workgroup and standard edition only
> get pre-defined drillthroughs.
>
> ----
> Brian Welcker, Microsoft
> >>>>>>>>>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
>
>
>
> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
> news:2CAC3038-95EA-4D0D-9E84-8EDE1DE24D8A@.microsoft.com...
> > We are going to separate reporting services from our database server by
> > putting RS on a single separate server. We need to know if we can use
> > Standard or if we have to purchase Enterprise. We have Enterprise for our
> > DB
> > server. The major differences between the 2 editions are data driven
> > subscriptions, which we do not need at this time, and infinite
> > clickthrough.
> > I cannot find a good definition of infinite clickthrough. We have reports
> > that navigate to other reports. In Standard, is some clickthrough still
> > available but only up to a certain number of clicks?
> >
> > Any details would really be appreciated.
> >
> > Stephanie
>
>|||I think it was pretty clear that the infinite clickthrough was a report
builder feature. I run standard and have lots of drill through (that is what
jump to report is called). If there is a limit I have not seen it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
news:7DE14E7D-779B-4068-943B-69BA1D726A51@.microsoft.com...
> Bruce,
> Thanks for the quick response. I read that article, too, and still was a
> bit confused. I do not use Report Builder either. I do, however, have
> navigation set up to jump from one report to another.
> Is it your opinion as well that I should be able to run Reporting Services
> Standard Edition on a separate server and still have the ability to use
> the
> Navigation tab and jump from one report to another? If so, would there be
> a
> limit on the number of jumps I can execute? I have a call in to MS but I
> am
> looking for any feedback as well. The cost difference is enough to
> warrant
> some research.
> Stephanie
> "Bruce L-C [MVP]" wrote:
>> I searched a little on this because I run with Standard and I've never
>> come
>> up across this limitation. I found out the reason for why I have never
>> noticed it. It has to do with Report Builder (which I do not use). Here
>> is a
>> posting by a Program Manager for RS:
>> >>>>>>>>>>
>> Infinte Clickthrough is a feature of Report Builder. It allows you
>> to
>> automatically drill between reports by using the relationships between
>> entities in the Report Model. The drillthroughs are created "on the fly"
>> without having to build them beforehand. Workgroup and standard edition
>> only
>> get pre-defined drillthroughs.
>>
>> ----
>> Brian Welcker, Microsoft
>> >>>>>>>>>
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>>
>>
>>
>> "Stephanie" <Stephanie@.discussions.microsoft.com> wrote in message
>> news:2CAC3038-95EA-4D0D-9E84-8EDE1DE24D8A@.microsoft.com...
>> > We are going to separate reporting services from our database server by
>> > putting RS on a single separate server. We need to know if we can use
>> > Standard or if we have to purchase Enterprise. We have Enterprise for
>> > our
>> > DB
>> > server. The major differences between the 2 editions are data driven
>> > subscriptions, which we do not need at this time, and infinite
>> > clickthrough.
>> > I cannot find a good definition of infinite clickthrough. We have
>> > reports
>> > that navigate to other reports. In Standard, is some clickthrough
>> > still
>> > available but only up to a certain number of clicks?
>> >
>> > Any details would really be appreciated.
>> >
>> > Stephanie
>>|||First of all, SSRS is bundled with SQL Server for free. If you have
SQL Enterprise 2005 then you have all the SSRS enterprise features,
including clickthrough reporting.
Infinite Clickthrough is indeed a feature of Report Builder. If you
have a Report Model created for your database, what this allows is
dynamic ad-hoc reports generated by SSRS itself. Basically it allows
you to drill-down indefinitely with the Report Builder dynamically
creating reports which are based off of the fields and relationships
on your database from the Report Model.
Basically, if the report your looking at references data that has a
relationship to another table, those fields will be hyperlinks. If
you click on the hyperlink SSRS will create a report based on the
table refereced by the link you clicked on. This can be done
indefinitely, like a virtual tour of your database. So, for example,
from a customer report you can click on their order total to see a
report showing their orders, from there you can click on a particular
order's details to see the actual items ordered, from there you can
click on a line item to see the item's general details, from there you
can click on the last PO for the item, etc.
You can always create your own reports that you drill-through. There
is no limit to how many of these manual reports you can create or
drill-through. The difference is SSRS will actually do all this for
you if you have Enterprise. This seems like a really basic feature
since all the infrastructure is in place with SSRS standard. We would
like to take advantage of clickthrough reporting but we don't have
enterprise. The cost to upgrade is pretty astronomical for this
feature.|||Thanks for the description.
Just a little clarification of why this matters to the person who posted.
They are putting RS on a different server than the database. It is not free
in that case. You have to have a license for each machine that RS is
installed on. So let's say you have a web farm (which required enterprise).
For each server on the web farm that has RS installed you need an enterprise
license on that server.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Matt Penner" <mattpenner2007@.gmail.com> wrote in message
news:1194451200.927016.283220@.z24g2000prh.googlegroups.com...
> First of all, SSRS is bundled with SQL Server for free. If you have
> SQL Enterprise 2005 then you have all the SSRS enterprise features,
> including clickthrough reporting.
> Infinite Clickthrough is indeed a feature of Report Builder. If you
> have a Report Model created for your database, what this allows is
> dynamic ad-hoc reports generated by SSRS itself. Basically it allows
> you to drill-down indefinitely with the Report Builder dynamically
> creating reports which are based off of the fields and relationships
> on your database from the Report Model.
> Basically, if the report your looking at references data that has a
> relationship to another table, those fields will be hyperlinks. If
> you click on the hyperlink SSRS will create a report based on the
> table refereced by the link you clicked on. This can be done
> indefinitely, like a virtual tour of your database. So, for example,
> from a customer report you can click on their order total to see a
> report showing their orders, from there you can click on a particular
> order's details to see the actual items ordered, from there you can
> click on a line item to see the item's general details, from there you
> can click on the last PO for the item, etc.
> You can always create your own reports that you drill-through. There
> is no limit to how many of these manual reports you can create or
> drill-through. The difference is SSRS will actually do all this for
> you if you have Enterprise. This seems like a really basic feature
> since all the infrastructure is in place with SSRS standard. We would
> like to take advantage of clickthrough reporting but we don't have
> enterprise. The cost to upgrade is pretty astronomical for this
> feature.
>|||First of all, SSRS is bundled with SQL Server for free. If you have
SQL Enterprise 2005 then you have all the SSRS enterprise features,
including clickthrough reporting.
Infinite Clickthrough is indeed a feature of Report Builder. If you
have a Report Model created for your database, what this allows is
dynamic ad-hoc reports generated by SSRS itself. Basically it allows
you to drill-down indefinitely with the Report Builder dynamically
creating reports which are based off of the fields and relationships
on your database from the Report Model.
Basically, if the report your looking at references data that has a
relationship to another table, those fields will be hyperlinks. If
you click on the hyperlink SSRS will create a report based on the
table refereced by the link you clicked on. This can be done
indefinitely, like a virtual tour of your database. So, for example,
from a customer report you can click on their order total to see a
report showing their orders, from there you can click on a particular
order's details to see the actual items ordered, from there you can
click on a line item to see the item's general details, from there you
can click on the last PO for the item, etc.
You can always create your own reports that you drill-through. There
is no limit to how many of these manual reports you can create or
drill-through. The difference is SSRS will actually do all this for
you if you have Enterprise. This seems like a really basic feature
since all the infrastructure is in place with SSRS standard. We would
like to take advantage of clickthrough reporting but we don't have
enterprise. The cost to upgrade is pretty astronomical for this
feature.
Sunday, March 11, 2012
Enterprise Manager over a VPN gets No items
I have an environment that has 18 separate SQL server machines. When
connected to the LAN I can connect to each and expand the databases tab no
problem. When I try the same over a VPN I find that three of my servers will
connect but on expanding the databases I get a long pause then 'No items'.
I've checked around and found some references to the same problem (SQL
server mag site) but no resolutions. I'm running XP pro and my SQL is sp3.
The three servers in question have only TCP and named pipes in the net lib,
they are all on Win2K one is on sp3, one on sp2 and one is 'out of the box'.
The VPN has ports 1433 and 1434 udp and tcp allowed.
connected to the LAN I can connect to each and expand the databases tab no
problem. When I try the same over a VPN I find that three of my servers will
connect but on expanding the databases I get a long pause then 'No items'.
I've checked around and found some references to the same problem (SQL
server mag site) but no resolutions. I'm running XP pro and my SQL is sp3.
The three servers in question have only TCP and named pipes in the net lib,
they are all on Win2K one is on sp3, one on sp2 and one is 'out of the box'.
The VPN has ports 1433 and 1434 udp and tcp allowed.
Does anyone have any suggestions as to what is causing this, its got to be
something simple but I've been looking at this so long now I cant see the
wood for the trees.
Help appreciated.There is a least one known issue that can produce this:
http://support.microsoft.com/default.aspx?scid=kb;[LN];Q315523
Here are some comments from an MS engineer on it:
http://groups.google.ch/groups?hl=e...%40cpmsftngxa06
There are several Google groups hits on this, by the way:
http://groups.google.com/groups?hl=...ems&sa=N&tab=wg
Simon
"Simon" <spamplin@.hss.com> wrote in message
news:bdpe27$k71$1@.hercules.btinternet.com...
> I have an environment that has 18 separate SQL server machines. When
> connected to the LAN I can connect to each and expand the databases tab no
> problem. When I try the same over a VPN I find that three of my servers
will
> connect but on expanding the databases I get a long pause then 'No items'.
> I've checked around and found some references to the same problem (SQL
> server mag site) but no resolutions. I'm running XP pro and my SQL is sp3.
> The three servers in question have only TCP and named pipes in the net
lib,
> they are all on Win2K one is on sp3, one on sp2 and one is 'out of the
box'.
> The VPN has ports 1433 and 1434 udp and tcp allowed.
> Does anyone have any suggestions as to what is causing this, its got to be
> something simple but I've been looking at this so long now I cant see the
> wood for the trees.
> Help appreciated.
Friday, February 24, 2012
Enterprise Manager Availability
Is Enterprise Manager and Query Analyzer available as separate licenses? or
downloads?
Ritche M wrote:
> Is Enterprise Manager and Query Analyzer available as separate
> licenses? or downloads?
If you purchase a CAL using a client licensing model, that gives you the
rights to install the client tools. If you already have a processor
license, your users can install client tools. The client tools are
installed from the main SQL Server CD. There are no separate downloads
AFAIK. None of this applies if you don't own a SQL Server license. There
are some free and more capable retail tools out there to perform the
functions of SQL EM / QA.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||check out http://www.agileinfollc.com DataStudio, it has superior user
interface and functionalities for managing SQL Server and other databases.
John King
http://www.agileinfollc.com
"Ritche M" <Ritche M@.discussions.microsoft.com> wrote in message
news:F291C016-4266-446C-B2E8-B68ACCDA0C27@.microsoft.com...
> Is Enterprise Manager and Query Analyzer available as separate licenses?
> or
> downloads?
downloads?
Ritche M wrote:
> Is Enterprise Manager and Query Analyzer available as separate
> licenses? or downloads?
If you purchase a CAL using a client licensing model, that gives you the
rights to install the client tools. If you already have a processor
license, your users can install client tools. The client tools are
installed from the main SQL Server CD. There are no separate downloads
AFAIK. None of this applies if you don't own a SQL Server license. There
are some free and more capable retail tools out there to perform the
functions of SQL EM / QA.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||check out http://www.agileinfollc.com DataStudio, it has superior user
interface and functionalities for managing SQL Server and other databases.
John King
http://www.agileinfollc.com
"Ritche M" <Ritche M@.discussions.microsoft.com> wrote in message
news:F291C016-4266-446C-B2E8-B68ACCDA0C27@.microsoft.com...
> Is Enterprise Manager and Query Analyzer available as separate licenses?
> or
> downloads?
Friday, February 17, 2012
Enterprise Manager
Is Enterprise Manager available as a separate download and installable on a
system with MSDE installed?
Are there any similar third-party tools?
Many thanks.
Am Fri, 11 Nov 2005 19:51:45 -0600 schrieb Andrew Chalk:
> Is Enterprise Manager available as a separate download and installable on a
> system with MSDE installed?
> Are there any similar third-party tools?
> Many thanks.
No, Enterprise Manager is not free, it's part of the 'big' SQL-Server,
where you have to pay for. You can manage MSDE with EM, yes, but you are
not allowed to copy EM from somebody or to give it away for free. You can
buy a SQL-Server Developer Edition CD from Microsoft (around 60$), this
includes an EM you can use for development.
Or you can use this free tool (can handle SQL2005 too!):
http://sqlmanager.net/en/products/mssql/manager
(the lite version is free)
bye,
Helmut
|||Thanks, I'll check it out.
- Andrew
"helmut woess" <hw@.iis.at> wrote in message
news:2pvy6t2z8b4o.1xpt7hatujbcl.dlg@.40tude.net...
> Am Fri, 11 Nov 2005 19:51:45 -0600 schrieb Andrew Chalk:
>
> No, Enterprise Manager is not free, it's part of the 'big' SQL-Server,
> where you have to pay for. You can manage MSDE with EM, yes, but you are
> not allowed to copy EM from somebody or to give it away for free. You can
> buy a SQL-Server Developer Edition CD from Microsoft (around 60$), this
> includes an EM you can use for development.
> Or you can use this free tool (can handle SQL2005 too!):
> http://sqlmanager.net/en/products/mssql/manager
> (the lite version is free)
> bye,
> Helmut
system with MSDE installed?
Are there any similar third-party tools?
Many thanks.
Am Fri, 11 Nov 2005 19:51:45 -0600 schrieb Andrew Chalk:
> Is Enterprise Manager available as a separate download and installable on a
> system with MSDE installed?
> Are there any similar third-party tools?
> Many thanks.
No, Enterprise Manager is not free, it's part of the 'big' SQL-Server,
where you have to pay for. You can manage MSDE with EM, yes, but you are
not allowed to copy EM from somebody or to give it away for free. You can
buy a SQL-Server Developer Edition CD from Microsoft (around 60$), this
includes an EM you can use for development.
Or you can use this free tool (can handle SQL2005 too!):
http://sqlmanager.net/en/products/mssql/manager
(the lite version is free)
bye,
Helmut
|||Thanks, I'll check it out.
- Andrew
"helmut woess" <hw@.iis.at> wrote in message
news:2pvy6t2z8b4o.1xpt7hatujbcl.dlg@.40tude.net...
> Am Fri, 11 Nov 2005 19:51:45 -0600 schrieb Andrew Chalk:
>
> No, Enterprise Manager is not free, it's part of the 'big' SQL-Server,
> where you have to pay for. You can manage MSDE with EM, yes, but you are
> not allowed to copy EM from somebody or to give it away for free. You can
> buy a SQL-Server Developer Edition CD from Microsoft (around 60$), this
> includes an EM you can use for development.
> Or you can use this free tool (can handle SQL2005 too!):
> http://sqlmanager.net/en/products/mssql/manager
> (the lite version is free)
> bye,
> Helmut
Wednesday, February 15, 2012
enterprise key?
has anyone heard of this? A unique key separate from primary keys? Something
that stands apart from say, clientID, employeeID, companyID,...? thx, -hazzThere is the ability to create a unique index and a unique constraint. I've
never heard of "enterprise keys" with specific relation to SQL Server.
http://www.aspfaq.com/
(Reverse address to reply.)
"Hazz" <hazz@.nospameroosonic.net> wrote in message
news:#A8K3arIFHA.3108@.tk2msftngp13.phx.gbl...
> has anyone heard of this? A unique key separate from primary keys?
Something
> that stands apart from say, clientID, employeeID, companyID,...?
thx, -hazz
>|||Are you looking for a uniqueidentifier data type? It can create unique
values using NEWID().
Simon Worth
"Hazz" <hazz@.nospameroosonic.net> wrote in message
news:%23A8K3arIFHA.3108@.tk2msftngp13.phx.gbl...
> has anyone heard of this? A unique key separate from primary keys?
Something
> that stands apart from say, clientID, employeeID, companyID,...?
thx, -hazz
>|||Thank you Aaron.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:uXMBpdrIFHA.3484@.TK2MSFTNGP12.phx.gbl...
> There is the ability to create a unique index and a unique constraint.
> I've
> never heard of "enterprise keys" with specific relation to SQL Server.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Hazz" <hazz@.nospameroosonic.net> wrote in message
> news:#A8K3arIFHA.3108@.tk2msftngp13.phx.gbl...
> Something
> thx, -hazz
>|||Thank you Simon.
"Simon Worth" <REMOVEFIRST_simon.worth@.gmail.com> wrote in message
news:%23MBjFgyIFHA.2132@.TK2MSFTNGP14.phx.gbl...
> Are you looking for a uniqueidentifier data type? It can create unique
> values using NEWID().
> --
> Simon Worth
>
> "Hazz" <hazz@.nospameroosonic.net> wrote in message
> news:%23A8K3arIFHA.3108@.tk2msftngp13.phx.gbl...
> Something
> thx, -hazz
>
that stands apart from say, clientID, employeeID, companyID,...? thx, -hazzThere is the ability to create a unique index and a unique constraint. I've
never heard of "enterprise keys" with specific relation to SQL Server.
http://www.aspfaq.com/
(Reverse address to reply.)
"Hazz" <hazz@.nospameroosonic.net> wrote in message
news:#A8K3arIFHA.3108@.tk2msftngp13.phx.gbl...
> has anyone heard of this? A unique key separate from primary keys?
Something
> that stands apart from say, clientID, employeeID, companyID,...?
thx, -hazz
>|||Are you looking for a uniqueidentifier data type? It can create unique
values using NEWID().
Simon Worth
"Hazz" <hazz@.nospameroosonic.net> wrote in message
news:%23A8K3arIFHA.3108@.tk2msftngp13.phx.gbl...
> has anyone heard of this? A unique key separate from primary keys?
Something
> that stands apart from say, clientID, employeeID, companyID,...?
thx, -hazz
>|||Thank you Aaron.
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:uXMBpdrIFHA.3484@.TK2MSFTNGP12.phx.gbl...
> There is the ability to create a unique index and a unique constraint.
> I've
> never heard of "enterprise keys" with specific relation to SQL Server.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Hazz" <hazz@.nospameroosonic.net> wrote in message
> news:#A8K3arIFHA.3108@.tk2msftngp13.phx.gbl...
> Something
> thx, -hazz
>|||Thank you Simon.
"Simon Worth" <REMOVEFIRST_simon.worth@.gmail.com> wrote in message
news:%23MBjFgyIFHA.2132@.TK2MSFTNGP14.phx.gbl...
> Are you looking for a uniqueidentifier data type? It can create unique
> values using NEWID().
> --
> Simon Worth
>
> "Hazz" <hazz@.nospameroosonic.net> wrote in message
> news:%23A8K3arIFHA.3108@.tk2msftngp13.phx.gbl...
> Something
> thx, -hazz
>
Subscribe to:
Posts (Atom)