TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476[ /url]
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Cannot obtain the schema rowset "DBSCHEMA_CATALOGS" for OLE DB provider "SQL Server" for linked server "(null)". The provider supports the interface, but returns a failure code when it is used. (Microsoft SQL Server, Error: 7311)
For help, click: [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .3042&EvtSrc=MSSQLServer&EvtID=7311&LinkId=20476[/url]
BUTTONS:
OK
The links take you to the "We're sorry page," which doesn't help.
Thanks,
Tony
Tony
Could be a bug
http://connect.microsoft.com/SQLServer/feedback/Validation.aspx?FeedbackID=261012
"Tony" <tsheehan@.tji-holdings.com> wrote in message news:ekk$S$cbIHA.4172@.TK2MSFTNGP02.phx.gbl...
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476[ /url]
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Cannot obtain the schema rowset "DBSCHEMA_CATALOGS" for OLE DB provider "SQL Server" for linked server "(null)". The provider supports the interface, but returns a failure code when it is used. (Microsoft SQL Server, Error: 7311)
For help, click: [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .3042&EvtSrc=MSSQLServer&EvtID=7311&LinkId=20476[/url]
BUTTONS:
OK
The links take you to the "We're sorry page," which doesn't help.
Thanks,
Tony
2012年3月22日星期四
2012年3月20日星期二
Any way to track if a person does a select on a table?
We have a situation where we would like to know who is accessing our data.
We know we could make a user read only but we'd also like to know what they
did to retrieve the data.
I guess what I need is Query Profiler but limit it to a specific user. Since
the user will have read only privileges, I won't have to worry about them
changing the data.
I just want to know that they accessed it.
BTW - they will be doing this through an ODBC connection in Access.
TIA - Jeff.
I think you answered your own question
Profile the database, filter the
user, save the trace to a table and query the table for the results...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>
|||Consider creating a SQL Trace with the desired events and filters. You can
create such a trace using the Profiler GUI and then script/run the trace to
log to a file.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>
|||network packet sniffing is the most efficient/effective way to do this.
There are several products on the market that do this now.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>
We know we could make a user read only but we'd also like to know what they
did to retrieve the data.
I guess what I need is Query Profiler but limit it to a specific user. Since
the user will have read only privileges, I won't have to worry about them
changing the data.
I just want to know that they accessed it.
BTW - they will be doing this through an ODBC connection in Access.
TIA - Jeff.
I think you answered your own question
Profile the database, filter theuser, save the trace to a table and query the table for the results...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>
|||Consider creating a SQL Trace with the desired events and filters. You can
create such a trace using the Profiler GUI and then script/run the trace to
log to a file.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>
|||network packet sniffing is the most efficient/effective way to do this.
There are several products on the market that do this now.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>
Any way to track if a person does a select on a table?
We have a situation where we would like to know who is accessing our data.
We know we could make a user read only but we'd also like to know what they
did to retrieve the data.
I guess what I need is Query Profiler but limit it to a specific user. Since
the user will have read only privileges, I won't have to worry about them
changing the data.
I just want to know that they accessed it.
BTW - they will be doing this through an ODBC connection in Access.
TIA - Jeff.I think you answered your own question :) Profile the database, filter the
user, save the trace to a table and query the table for the results...
--
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>|||Consider creating a SQL Trace with the desired events and filters. You can
create such a trace using the Profiler GUI and then script/run the trace to
log to a file.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>|||network packet sniffing is the most efficient/effective way to do this.
There are several products on the market that do this now.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>
We know we could make a user read only but we'd also like to know what they
did to retrieve the data.
I guess what I need is Query Profiler but limit it to a specific user. Since
the user will have read only privileges, I won't have to worry about them
changing the data.
I just want to know that they accessed it.
BTW - they will be doing this through an ODBC connection in Access.
TIA - Jeff.I think you answered your own question :) Profile the database, filter the
user, save the trace to a table and query the table for the results...
--
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>|||Consider creating a SQL Trace with the desired events and filters. You can
create such a trace using the Profiler GUI and then script/run the trace to
log to a file.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>|||network packet sniffing is the most efficient/effective way to do this.
There are several products on the market that do this now.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>
Any way to track if a person does a select on a table?
We have a situation where we would like to know who is accessing our data.
We know we could make a user read only but we'd also like to know what they
did to retrieve the data.
I guess what I need is Query Profiler but limit it to a specific user. Since
the user will have read only privileges, I won't have to worry about them
changing the data.
I just want to know that they accessed it.
BTW - they will be doing this through an ODBC connection in Access.
TIA - Jeff.I think you answered your own question Profile the database, filter the
user, save the trace to a table and query the table for the results...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>|||Consider creating a SQL Trace with the desired events and filters. You can
create such a trace using the Profiler GUI and then script/run the trace to
log to a file.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>|||network packet sniffing is the most efficient/effective way to do this.
There are several products on the market that do this now.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>
We know we could make a user read only but we'd also like to know what they
did to retrieve the data.
I guess what I need is Query Profiler but limit it to a specific user. Since
the user will have read only privileges, I won't have to worry about them
changing the data.
I just want to know that they accessed it.
BTW - they will be doing this through an ODBC connection in Access.
TIA - Jeff.I think you answered your own question
Profile the database, filter theuser, save the trace to a table and query the table for the results...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>|||Consider creating a SQL Trace with the desired events and filters. You can
create such a trace using the Profiler GUI and then script/run the trace to
log to a file.
Hope this helps.
Dan Guzman
SQL Server MVP
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>|||network packet sniffing is the most efficient/effective way to do this.
There are several products on the market that do this now.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Mufasa" <jb@.nowhere.com> wrote in message
news:%23nOYhFqPIHA.3532@.TK2MSFTNGP04.phx.gbl...
> We have a situation where we would like to know who is accessing our data.
> We know we could make a user read only but we'd also like to know what
> they did to retrieve the data.
> I guess what I need is Query Profiler but limit it to a specific user.
> Since the user will have read only privileges, I won't have to worry about
> them changing the data.
> I just want to know that they accessed it.
> BTW - they will be doing this through an ODBC connection in Access.
> TIA - Jeff.
>
2012年2月16日星期四
Any free tools for accessing and managing ISP SQL account?
Hi:
Very new to MS SQL, but our ISP provides us with a SQL account which we want
to use.
But the question is we don't know if there is any free tools (e.g. DbaMgr
2K) that we can use to access and/or administrate to our SQL account as
DbaMgr 2K, which we can see the DB information and/or to change the design
and data.
Thanks in advance.
xfile wrote:
> Hi:
> Very new to MS SQL, but our ISP provides us with a SQL account which
> we want to use.
> But the question is we don't know if there is any free tools (e.g.
> DbaMgr 2K) that we can use to access and/or administrate to our SQL
> account as DbaMgr 2K, which we can see the DB information and/or to
> change the design and data.
> Thanks in advance.
Web Data Administrator from Microsoft. It's free and designed for what
you need it for.
http://www.microsoft.com/downloads/d...displaylang=en
David Gugick
Imceda Software
www.imceda.com
|||Hi:
Thanks so much, and I am currently studying the page and will test the tool.
I have posted many places, but you are the first and only one replies.
Thanks so much.
We were thinking to change ISP and maybe move to mySQL platform if we cannot
find such a tool.
Many thanks again.
"David Gugick" <davidg-nospam@.imceda.com>
??:%23xr4mDe$EHA.3700@.tk2msftngp13.phx.gbl...
> xfile wrote:
> Web Data Administrator from Microsoft. It's free and designed for what you
> need it for.
> http://www.microsoft.com/downloads/d...displaylang=en
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
|||xfile wrote:
> Hi:
> Thanks so much, and I am currently studying the page and will test
> the tool.
> I have posted many places, but you are the first and only one replies.
> Thanks so much.
> We were thinking to change ISP and maybe move to mySQL platform if we
> cannot find such a tool.
>
There are a number of tools, both free and retail. We offer Speed IDE
Pro, Microsoft has the free Web Data Administrator, but there are
others. You may get a lot of responses with options.
David Gugick
Imceda Software
www.imceda.com
|||The Web Data Administrator is good. You can also get the
free version of Toad for SQL Server from:
http://www.toadsoft.com/toadsqlserve..._sqlserver.htm
You can also find a list of third party products at:
http://www.aspfaq.com/show.asp?id=2442
-Sue
On Wed, 19 Jan 2005 13:09:37 +0800, "xfile"
<cou-cou@.remove.nospam.com> wrote:
>Hi:
>Thanks so much, and I am currently studying the page and will test the tool.
>I have posted many places, but you are the first and only one replies.
>Thanks so much.
>We were thinking to change ISP and maybe move to mySQL platform if we cannot
>find such a tool.
>Many thanks again.
>
>"David Gugick" <davidg-nospam@.imceda.com>
>??:%23xr4mDe$EHA.3700@.tk2msftngp13.phx.gbl.. .
>
|||Hi:
Thanks for all the information.
Maybe I am too new to this thing, but where exactly shall I install Web Data
Administrator to?
I assume it will be under Program Files, but maybe not.
According to this article,
http://www.databasejournal.com/featu...e.php/3330301, the
installation will take care of itself and all I have to do is to type:
http://<webserver>/webadmin/default.aspx and it will show up the page.
Well, I typed localhost or the default server name of my local machine, and
it gives me an error message for files cannot be found.
On previous tries, I put the Web folders under the IIS www and give it a
name called sqlwebAdmin and made it a FP 2002 web, but then I got another
error message for the incorrect security using Windows as authentication and
needed to modify configuration file which I don't know how to.
I could not find many articles on the web talking about how to install and
configure it. Seems no one but me have the problem.
Thanks again for your information, and I will look into those
"Sue Hoegemeier" <Sue_H@.nomail.please>
??:3n0tu01pit72b5j3fa27g39jng7s6792lk@.4ax.com ...
> The Web Data Administrator is good. You can also get the
> free version of Toad for SQL Server from:
> http://www.toadsoft.com/toadsqlserve..._sqlserver.htm
> You can also find a list of third party products at:
> http://www.aspfaq.com/show.asp?id=2442
> -Sue
> On Wed, 19 Jan 2005 13:09:37 +0800, "xfile"
> <cou-cou@.remove.nospam.com> wrote:
>
Very new to MS SQL, but our ISP provides us with a SQL account which we want
to use.
But the question is we don't know if there is any free tools (e.g. DbaMgr
2K) that we can use to access and/or administrate to our SQL account as
DbaMgr 2K, which we can see the DB information and/or to change the design
and data.
Thanks in advance.
xfile wrote:
> Hi:
> Very new to MS SQL, but our ISP provides us with a SQL account which
> we want to use.
> But the question is we don't know if there is any free tools (e.g.
> DbaMgr 2K) that we can use to access and/or administrate to our SQL
> account as DbaMgr 2K, which we can see the DB information and/or to
> change the design and data.
> Thanks in advance.
Web Data Administrator from Microsoft. It's free and designed for what
you need it for.
http://www.microsoft.com/downloads/d...displaylang=en
David Gugick
Imceda Software
www.imceda.com
|||Hi:
Thanks so much, and I am currently studying the page and will test the tool.
I have posted many places, but you are the first and only one replies.
Thanks so much.
We were thinking to change ISP and maybe move to mySQL platform if we cannot
find such a tool.
Many thanks again.
"David Gugick" <davidg-nospam@.imceda.com>
??:%23xr4mDe$EHA.3700@.tk2msftngp13.phx.gbl...
> xfile wrote:
> Web Data Administrator from Microsoft. It's free and designed for what you
> need it for.
> http://www.microsoft.com/downloads/d...displaylang=en
>
> --
> David Gugick
> Imceda Software
> www.imceda.com
|||xfile wrote:
> Hi:
> Thanks so much, and I am currently studying the page and will test
> the tool.
> I have posted many places, but you are the first and only one replies.
> Thanks so much.
> We were thinking to change ISP and maybe move to mySQL platform if we
> cannot find such a tool.
>
There are a number of tools, both free and retail. We offer Speed IDE
Pro, Microsoft has the free Web Data Administrator, but there are
others. You may get a lot of responses with options.
David Gugick
Imceda Software
www.imceda.com
|||The Web Data Administrator is good. You can also get the
free version of Toad for SQL Server from:
http://www.toadsoft.com/toadsqlserve..._sqlserver.htm
You can also find a list of third party products at:
http://www.aspfaq.com/show.asp?id=2442
-Sue
On Wed, 19 Jan 2005 13:09:37 +0800, "xfile"
<cou-cou@.remove.nospam.com> wrote:
>Hi:
>Thanks so much, and I am currently studying the page and will test the tool.
>I have posted many places, but you are the first and only one replies.
>Thanks so much.
>We were thinking to change ISP and maybe move to mySQL platform if we cannot
>find such a tool.
>Many thanks again.
>
>"David Gugick" <davidg-nospam@.imceda.com>
>??:%23xr4mDe$EHA.3700@.tk2msftngp13.phx.gbl.. .
>
|||Hi:
Thanks for all the information.
Maybe I am too new to this thing, but where exactly shall I install Web Data
Administrator to?
I assume it will be under Program Files, but maybe not.
According to this article,
http://www.databasejournal.com/featu...e.php/3330301, the
installation will take care of itself and all I have to do is to type:
http://<webserver>/webadmin/default.aspx and it will show up the page.
Well, I typed localhost or the default server name of my local machine, and
it gives me an error message for files cannot be found.
On previous tries, I put the Web folders under the IIS www and give it a
name called sqlwebAdmin and made it a FP 2002 web, but then I got another
error message for the incorrect security using Windows as authentication and
needed to modify configuration file which I don't know how to.
I could not find many articles on the web talking about how to install and
configure it. Seems no one but me have the problem.
Thanks again for your information, and I will look into those
"Sue Hoegemeier" <Sue_H@.nomail.please>
??:3n0tu01pit72b5j3fa27g39jng7s6792lk@.4ax.com ...
> The Web Data Administrator is good. You can also get the
> free version of Toad for SQL Server from:
> http://www.toadsoft.com/toadsqlserve..._sqlserver.htm
> You can also find a list of third party products at:
> http://www.aspfaq.com/show.asp?id=2442
> -Sue
> On Wed, 19 Jan 2005 13:09:37 +0800, "xfile"
> <cou-cou@.remove.nospam.com> wrote:
>
2012年2月9日星期四
ANSI_NULL and ANSI_QUOTED_IDENTIFIER
I am trying to set these two options to ON for default sp creation. or at LEAST be able to set them for sp's accessing databases on remote servers.
Seems though, that no matter what I set the rekated checkboxes to in the "edit SQL Server registration properties"'s connections pane, they get created as:
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
CREATE PROCEDURE [dbo].[sp_yada_yada_yada]
AS
DECLARE @.YoMama float
DECLARE @.YoDaddy float
DECLARE @.YoSista float
SET @.YoSista = @.YoDadd + @.YoMama
RETURN
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
(which I assume is a previous/default setting of some type).
I also had someone tell me that I need to set those params when I initially register the server, but I can't see any option to do so when I register my server(s) *scratching head*
I even verified in the connection pane's "running values" radio button, and they ARE checked (as I expected) but creating a new SP STILL results in the incorrect option settings being auto-magically applied.
help?
Thanks!
Any SET options that affect the results generated by Transact-SQL statements must have the same settings for all operations referencing the index. There are seven SET options that affect the results stored in computed columns and returned by views. All connections using indexes on computed columns or indexed views must have the same settings for these seven options:
These six SET options must be set to ON:
ANSI_NULLS
ANSI_PADDING
ANSI_WARNINGS
ARITHABORT
CONCAT_NULL_YIELDS_NULL
QUOTED_IDENTIFIER
The NUMERIC_ROUNDABORT option must be set to OFF.
These SET options must be set correctly for any connection that creates an index on a view or computed column. Any connection executing INSERT, UPDATE or DELETE statements that change data values stored in the indexes must have the correct settings.Why are you doing this?
Leave the settings alone unless you HAVE to change them...|||Originally posted by Brett Kaiser
Why are you doing this?
Leave the settings alone unless you HAVE to change them...
It's my understanding that I need to change them to keep from getting the error I'm getting when I try to access a database on a linked server...
"Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection. This ensures consistent query semantics. Enable these options and then reissue your query."
I know of no other way around it - - currently I create my stored procedures and functions that access the linked servers though Query Analyzer - because it pays attention to my SET OPTIONS stuff outside the function/stored procedure.
If there's a way to get it to be kind to my linked server queries from the SQL Server Enterprise Manager, that would be cool...but nothing I've tried SO FAR will convince it to be nice to me.
Maybe there's a blurb in the Books Online that can help me understand more about why I shouldn't set these options to ON when doing a query to a linked server, but everything I've read so far says then need to be set ON...*shrug*|||found my answer here...but still...
http://www.dbforums.com/showthread.php?threadid=971846&highlight=Heterogeneous+queries+require+the+ANSI_N ULLS+and+ANSI_WARNINGS+options+to+be+set+for+the+c onnection
I guess it makes sense to just do it in the creation of the specific SP, rather than modifying a server option I know very little about *LOL*
Thanks for the loan of your time though :D|||Keep on truckin....
Seems though, that no matter what I set the rekated checkboxes to in the "edit SQL Server registration properties"'s connections pane, they get created as:
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
CREATE PROCEDURE [dbo].[sp_yada_yada_yada]
AS
DECLARE @.YoMama float
DECLARE @.YoDaddy float
DECLARE @.YoSista float
SET @.YoSista = @.YoDadd + @.YoMama
RETURN
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
(which I assume is a previous/default setting of some type).
I also had someone tell me that I need to set those params when I initially register the server, but I can't see any option to do so when I register my server(s) *scratching head*
I even verified in the connection pane's "running values" radio button, and they ARE checked (as I expected) but creating a new SP STILL results in the incorrect option settings being auto-magically applied.
help?
Thanks!
Any SET options that affect the results generated by Transact-SQL statements must have the same settings for all operations referencing the index. There are seven SET options that affect the results stored in computed columns and returned by views. All connections using indexes on computed columns or indexed views must have the same settings for these seven options:
These six SET options must be set to ON:
ANSI_NULLS
ANSI_PADDING
ANSI_WARNINGS
ARITHABORT
CONCAT_NULL_YIELDS_NULL
QUOTED_IDENTIFIER
The NUMERIC_ROUNDABORT option must be set to OFF.
These SET options must be set correctly for any connection that creates an index on a view or computed column. Any connection executing INSERT, UPDATE or DELETE statements that change data values stored in the indexes must have the correct settings.Why are you doing this?
Leave the settings alone unless you HAVE to change them...|||Originally posted by Brett Kaiser
Why are you doing this?
Leave the settings alone unless you HAVE to change them...
It's my understanding that I need to change them to keep from getting the error I'm getting when I try to access a database on a linked server...
"Heterogeneous queries require the ANSI_NULLS and ANSI_WARNINGS options to be set for the connection. This ensures consistent query semantics. Enable these options and then reissue your query."
I know of no other way around it - - currently I create my stored procedures and functions that access the linked servers though Query Analyzer - because it pays attention to my SET OPTIONS stuff outside the function/stored procedure.
If there's a way to get it to be kind to my linked server queries from the SQL Server Enterprise Manager, that would be cool...but nothing I've tried SO FAR will convince it to be nice to me.
Maybe there's a blurb in the Books Online that can help me understand more about why I shouldn't set these options to ON when doing a query to a linked server, but everything I've read so far says then need to be set ON...*shrug*|||found my answer here...but still...
http://www.dbforums.com/showthread.php?threadid=971846&highlight=Heterogeneous+queries+require+the+ANSI_N ULLS+and+ANSI_WARNINGS+options+to+be+set+for+the+c onnection
I guess it makes sense to just do it in the creation of the specific SP, rather than modifying a server option I know very little about *LOL*
Thanks for the loan of your time though :D|||Keep on truckin....
Ansi Nulls
I am get the following erro message when accessing the linked server table.
Any Suggetions ??
"HETROGENOUS QUERIES REQUIRE THE ANSI NULLS ON AND ASI WARNINGS TO BE SET FOR THE CONNETION. THIS ENSURES CONSISTENT QUERY SEMANTICS. ENABLE THESE OPTIONS AND THEN USE THE YOUR QUERY"
If Enable what go will go wrong because these are production servers..
Rajessentially you need to issue two statments:
set ANSI_NULLS on
set ANSI_WARNINGS on
I doubt setting either of these to on will give you any problems with the possability of NULL comparisons, see below.
as for what will go wrong, from Books Online:
ANSI_NULLS
When set to ON, all comparisons to a null value evaluate to NULL (unknown). When set to OFF, comparisons of non-Unicode values to a null value evaluate to TRUE if both values are NULL. By default, the ANSI_NULLS database option is OFF.
Connection-level settings (set using the SET statement) override the default database setting for ANSI_NULLS. By default, ODBC and OLE DB clients issue a connection-level SET statement setting ANSI_NULLS to ON for the session when connecting to SQL Server. For more information, see SET ANSI_NULLS.
SET ANSI_NULLS also must be set to ON when you create or manipulate indexes on computed columns or indexed views.
The status of this option can be determined by examining the IsAnsiNullsEnabled property of the DATABASEPROPERTYEX function.
and
ANSI_WARNINGS
When set to ON, errors or warnings are issued when conditions such as "divide by zero" occur or null values appear in aggregate functions. When set to OFF, no warnings are raised when null values appear in aggregate functions, and null values are returned when conditions such as "divide by zero" occur. By default, ANSI_WARNINGS is OFF.
SET ANSI_WARNINGS must be set to ON when you create or manipulate indexes on computed columns or indexed views.
Connection-level settings (set using the SET statement) override the default database setting for ANSI_WARNINGS. By default, ODBC and OLE DB clients issue a connection-level SET statement setting ANSI_WARNINGS to ON for the session when connecting to SQL Server. For more information, see SET ANSI_WARNINGS.
The status of this option can be determined by examining the IsAnsiWarningsEnabled property of the DATABASEPROPERTYEX function.
Any Suggetions ??
"HETROGENOUS QUERIES REQUIRE THE ANSI NULLS ON AND ASI WARNINGS TO BE SET FOR THE CONNETION. THIS ENSURES CONSISTENT QUERY SEMANTICS. ENABLE THESE OPTIONS AND THEN USE THE YOUR QUERY"
If Enable what go will go wrong because these are production servers..
Rajessentially you need to issue two statments:
set ANSI_NULLS on
set ANSI_WARNINGS on
I doubt setting either of these to on will give you any problems with the possability of NULL comparisons, see below.
as for what will go wrong, from Books Online:
ANSI_NULLS
When set to ON, all comparisons to a null value evaluate to NULL (unknown). When set to OFF, comparisons of non-Unicode values to a null value evaluate to TRUE if both values are NULL. By default, the ANSI_NULLS database option is OFF.
Connection-level settings (set using the SET statement) override the default database setting for ANSI_NULLS. By default, ODBC and OLE DB clients issue a connection-level SET statement setting ANSI_NULLS to ON for the session when connecting to SQL Server. For more information, see SET ANSI_NULLS.
SET ANSI_NULLS also must be set to ON when you create or manipulate indexes on computed columns or indexed views.
The status of this option can be determined by examining the IsAnsiNullsEnabled property of the DATABASEPROPERTYEX function.
and
ANSI_WARNINGS
When set to ON, errors or warnings are issued when conditions such as "divide by zero" occur or null values appear in aggregate functions. When set to OFF, no warnings are raised when null values appear in aggregate functions, and null values are returned when conditions such as "divide by zero" occur. By default, ANSI_WARNINGS is OFF.
SET ANSI_WARNINGS must be set to ON when you create or manipulate indexes on computed columns or indexed views.
Connection-level settings (set using the SET statement) override the default database setting for ANSI_WARNINGS. By default, ODBC and OLE DB clients issue a connection-level SET statement setting ANSI_WARNINGS to ON for the session when connecting to SQL Server. For more information, see SET ANSI_WARNINGS.
The status of this option can be determined by examining the IsAnsiWarningsEnabled property of the DATABASEPROPERTYEX function.
订阅：
评论 (Atom)