Ok I have been through all the help and newsgroups that I can find and I can
not find the answer to my problem.
I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
local accounts to a doamin account.
One one SQL server it worked fine and I am able to run my query with no
problem but when I try to run the same query on the second SQL server I get:
Server: Msg 7320, Level 16, State 2, Line 1
Could not execute query against OLE DB provider 'ADsDSOObject'.
OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
returned 0x80040e22].
Here is the select command that I am using:
SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft Office
2003 Standard001,OU=USA,DC=Domain,DC=com''')
Like I said this works on one SQL server but not the other. Both SQL servers
are part of the same doamin and I am trying to qury information form that
domain.
Any ideas would be great.
Did you check the MSDN article ?
http://msdn.microsoft.com/library/de...uted_query.asp
You might have a look on the error output and send it here:
http://groups.google.de/groups?hl=de...a09%26rnum%3D1
HTH, Jens Suessmeyer.
"Jesse" <Jesse@.discussions.microsoft.com> schrieb im Newsbeitrag
news:75491BB5-A8F9-4C00-A385-8836F517F641@.microsoft.com...
> Ok I have been through all the help and newsgroups that I can find and I
> can
> not find the answer to my problem.
> I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
> servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
> local accounts to a doamin account.
> One one SQL server it worked fine and I am able to run my query with no
> problem but when I try to run the same query on the second SQL server I
> get:
> Server: Msg 7320, Level 16, State 2, Line 1
> Could not execute query against OLE DB provider 'ADsDSOObject'.
> OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
> returned 0x80040e22].
> Here is the select command that I am using:
> SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
> ''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft
> Office
> 2003 Standard001,OU=USA,DC=Domain,DC=com''')
> Like I said this works on one SQL server but not the other. Both SQL
> servers
> are part of the same doamin and I am trying to qury information form that
> domain.
> Any ideas would be great.
|||Jens,
Yes I saw that article and that is what I used to create my link and server
logon information.
"Jens Sü?meyer" wrote:
> Did you check the MSDN article ?
> http://msdn.microsoft.com/library/de...uted_query.asp
> You might have a look on the error output and send it here:
> http://groups.google.de/groups?hl=de...a09%26rnum%3D1
> HTH, Jens Suessmeyer.
>
> "Jesse" <Jesse@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:75491BB5-A8F9-4C00-A385-8836F517F641@.microsoft.com...
>
>
Showing posts with label via. Show all posts
Showing posts with label via. Show all posts
Thursday, March 8, 2012
ADSI Via Linked Server
Ok I have been through all the help and newsgroups that I can find and I can
not find the answer to my problem.
I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
local accounts to a doamin account.
One one SQL server it worked fine and I am able to run my query with no
problem but when I try to run the same query on the second SQL server I get:
Server: Msg 7320, Level 16, State 2, Line 1
Could not execute query against OLE DB provider 'ADsDSOObject'.
OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
returned 0x80040e22].
Here is the select command that I am using:
SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft Office
2003 Standard001,OU=USA,DC=Domain,DC=com''')
Like I said this works on one SQL server but not the other. Both SQL servers
are part of the same doamin and I am trying to qury information form that
domain.
Any ideas would be great.Did you check the MSDN article ?
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/distributed_query.asp
You might have a look on the error output and send it here:
http://groups.google.de/groups?hl=de&lr=&threadm=pa5ReRhvBHA.2164%40cpmsftngxa09&rnum=1&prev=/groups%3Fq%3Dsql%2Bserver%2Badsi%2Blinked%2Bserver%2B7320%26hl%3Dde%26lr%3D%26selm%3Dpa5ReRhvBHA.2164%2540cpmsftngxa09%26rnum%3D1
HTH, Jens Suessmeyer.
"Jesse" <Jesse@.discussions.microsoft.com> schrieb im Newsbeitrag
news:75491BB5-A8F9-4C00-A385-8836F517F641@.microsoft.com...
> Ok I have been through all the help and newsgroups that I can find and I
> can
> not find the answer to my problem.
> I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
> servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
> local accounts to a doamin account.
> One one SQL server it worked fine and I am able to run my query with no
> problem but when I try to run the same query on the second SQL server I
> get:
> Server: Msg 7320, Level 16, State 2, Line 1
> Could not execute query against OLE DB provider 'ADsDSOObject'.
> OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
> returned 0x80040e22].
> Here is the select command that I am using:
> SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
> ''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft
> Office
> 2003 Standard001,OU=USA,DC=Domain,DC=com''')
> Like I said this works on one SQL server but not the other. Both SQL
> servers
> are part of the same doamin and I am trying to qury information form that
> domain.
> Any ideas would be great.|||Jens,
Yes I saw that article and that is what I used to create my link and server
logon information.
"Jens Sü�meyer" wrote:
> Did you check the MSDN article ?
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/distributed_query.asp
> You might have a look on the error output and send it here:
> http://groups.google.de/groups?hl=de&lr=&threadm=pa5ReRhvBHA.2164%40cpmsftngxa09&rnum=1&prev=/groups%3Fq%3Dsql%2Bserver%2Badsi%2Blinked%2Bserver%2B7320%26hl%3Dde%26lr%3D%26selm%3Dpa5ReRhvBHA.2164%2540cpmsftngxa09%26rnum%3D1
> HTH, Jens Suessmeyer.
>
> "Jesse" <Jesse@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:75491BB5-A8F9-4C00-A385-8836F517F641@.microsoft.com...
> > Ok I have been through all the help and newsgroups that I can find and I
> > can
> > not find the answer to my problem.
> >
> > I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
> > servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
> > local accounts to a doamin account.
> >
> > One one SQL server it worked fine and I am able to run my query with no
> > problem but when I try to run the same query on the second SQL server I
> > get:
> >
> > Server: Msg 7320, Level 16, State 2, Line 1
> > Could not execute query against OLE DB provider 'ADsDSOObject'.
> > OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
> > returned 0x80040e22].
> >
> > Here is the select command that I am using:
> >
> > SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
> > ''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft
> > Office
> > 2003 Standard001,OU=USA,DC=Domain,DC=com''')
> >
> > Like I said this works on one SQL server but not the other. Both SQL
> > servers
> > are part of the same doamin and I am trying to qury information form that
> > domain.
> >
> > Any ideas would be great.
>
>
not find the answer to my problem.
I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
local accounts to a doamin account.
One one SQL server it worked fine and I am able to run my query with no
problem but when I try to run the same query on the second SQL server I get:
Server: Msg 7320, Level 16, State 2, Line 1
Could not execute query against OLE DB provider 'ADsDSOObject'.
OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
returned 0x80040e22].
Here is the select command that I am using:
SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft Office
2003 Standard001,OU=USA,DC=Domain,DC=com''')
Like I said this works on one SQL server but not the other. Both SQL servers
are part of the same doamin and I am trying to qury information form that
domain.
Any ideas would be great.Did you check the MSDN article ?
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/distributed_query.asp
You might have a look on the error output and send it here:
http://groups.google.de/groups?hl=de&lr=&threadm=pa5ReRhvBHA.2164%40cpmsftngxa09&rnum=1&prev=/groups%3Fq%3Dsql%2Bserver%2Badsi%2Blinked%2Bserver%2B7320%26hl%3Dde%26lr%3D%26selm%3Dpa5ReRhvBHA.2164%2540cpmsftngxa09%26rnum%3D1
HTH, Jens Suessmeyer.
"Jesse" <Jesse@.discussions.microsoft.com> schrieb im Newsbeitrag
news:75491BB5-A8F9-4C00-A385-8836F517F641@.microsoft.com...
> Ok I have been through all the help and newsgroups that I can find and I
> can
> not find the answer to my problem.
> I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
> servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
> local accounts to a doamin account.
> One one SQL server it worked fine and I am able to run my query with no
> problem but when I try to run the same query on the second SQL server I
> get:
> Server: Msg 7320, Level 16, State 2, Line 1
> Could not execute query against OLE DB provider 'ADsDSOObject'.
> OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
> returned 0x80040e22].
> Here is the select command that I am using:
> SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
> ''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft
> Office
> 2003 Standard001,OU=USA,DC=Domain,DC=com''')
> Like I said this works on one SQL server but not the other. Both SQL
> servers
> are part of the same doamin and I am trying to qury information form that
> domain.
> Any ideas would be great.|||Jens,
Yes I saw that article and that is what I used to create my link and server
logon information.
"Jens Sü�meyer" wrote:
> Did you check the MSDN article ?
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/distributed_query.asp
> You might have a look on the error output and send it here:
> http://groups.google.de/groups?hl=de&lr=&threadm=pa5ReRhvBHA.2164%40cpmsftngxa09&rnum=1&prev=/groups%3Fq%3Dsql%2Bserver%2Badsi%2Blinked%2Bserver%2B7320%26hl%3Dde%26lr%3D%26selm%3Dpa5ReRhvBHA.2164%2540cpmsftngxa09%26rnum%3D1
> HTH, Jens Suessmeyer.
>
> "Jesse" <Jesse@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:75491BB5-A8F9-4C00-A385-8836F517F641@.microsoft.com...
> > Ok I have been through all the help and newsgroups that I can find and I
> > can
> > not find the answer to my problem.
> >
> > I have two SQL 2000 SP3 servers and 3 doamin controllers. On both SQL
> > servers I did the AD_addlinkedserver and the sp_addlinkedsrvlogin for all
> > local accounts to a doamin account.
> >
> > One one SQL server it worked fine and I am able to run my query with no
> > problem but when I try to run the same query on the second SQL server I
> > get:
> >
> > Server: Msg 7320, Level 16, State 2, Line 1
> > Could not execute query against OLE DB provider 'ADsDSOObject'.
> > OLE DB error trace [OLE/DB Provider 'ADsDSOObject' ICommandText::Execute
> > returned 0x80040e22].
> >
> > Here is the select command that I am using:
> >
> > SELECT * FROM OPENQUERY( ADSI,'SELECT Name, CN FROM
> > ''LDAP://ou=Users,DC=Domain,DC=com'' Where memberof = ''CN=Microsoft
> > Office
> > 2003 Standard001,OU=USA,DC=Domain,DC=com''')
> >
> > Like I said this works on one SQL server but not the other. Both SQL
> > servers
> > are part of the same doamin and I am trying to qury information form that
> > domain.
> >
> > Any ideas would be great.
>
>
Tuesday, March 6, 2012
AdomdConnection via a UDL file
To connect to a database engine by using types such as OleDbConnection, I can create a UDL file to connect to the database, then just use that UDL file by a connection string like "File Name = \\My Documents\\my.udl".
It seems that I cannot use this way to connect to SSAS. I can create a UDL file to connect to a local SSAS without any problem. However, when I use connection string like "File Name = \\My Documents\\myssas.udl" for AdomdConnection, I get the following error:
"The 'File Name' property name is not formatted correctly."
Could anyone tell me what is the correct format?
Thanks,
hz
hello,
right now supplying conneciton information for an AdomdConnection in a UDL file is not supported in Adomd.Net.
hope this clarifies.
|||Thanks, Mary.
It is good to have this confirmed.
hz
AdomdClient: Which sequence belongs to which cluster?
Hi,
We are using Microsoft Sequence Clustering both "manually" via Visual Studio (SQL Server Business Intelligence Development Studio) and "programatically" via AMO and ADOMD.NET (using C#). We use AMO to build and process the MiningModel, and ADOMD.NET (Microsoft.AnalysisServices.AdomdClient) to browse through results.
Everything is working fine except for a very important detail: we can't find where the MiningModel stores cluster membership. The MiningModel.Content contains a column NODE_SUPPORT which shows how many sequences there are in each cluster, but we can't find which sequence belongs to which cluster.
In Visual Studio, the Microsoft Sequence Cluster Viewer is able to show this in Cluster Profiles (a right-click on a cluster followed by Show Legend lists the sequences that belong to that cluster).
Question is: where does the Viewer get this information, and how can we get it via ADOMD? Or via AMO, if that's the case?
Would appreciate your assistance.
Kind Regards,
Diogo
You can use the Cluster() function in a prediction query to get this information. As you probably know by now, you should construct the query and set it as the CommandText of an AdomdCommand object.
Alternatively, you may find it easier to navigate the results by using Cluster() as a column reference in PredictHistogram() and flatten the result set:
SELECT FLATTENED (PredictHistogram(Cluster() ...)
|||It seems that in order to determine cluster membership we must write a prediction query over the same data that served as training input. Is it easy to write such a query? Can you provide us with an example? Or the general form of such query?
Also while creating the mining model I haven't marked any column as "predictable". I guess I should do that, right?
Thanks!
|||The query is indeed very simple, here is the general form:
SELECT Cluster(), t.caseid FROM MyMiningModel
NATURAL PREDICTION JOIN (SELECT * FROM MyMiningModel.CASES) as t
ORDER BY Cluster()
The posts from Jamie in this thread were particularly useful:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1035151&SiteID=1
Problem solved! Thanks for the hint!
Adomd.net and ClickOnce
We need to install ADOMD.NET on client workstations and would like to install it via ClickOnce. Has anyone built a ClickOnce Bootstrapper Prerequisite Package for SQLServer2005_ADOMD.MSI?
Also, when running SQLServer2005_ADOMD.MSI on a client workstation manually, we receive an error stating that an updated version of MSXML 6.0 must be installed as a prerequisite. We run the MSXML6.MSI (11/7/2005) found in the SS05 November 2005 Feature Pack and then run SQLServer2005_ADOMD.MSI and everything is fine. This workstation already has Version 2.0 of the .NET Framework installed on it. Isn't MSXML 6.0 a prerequisite for installing V 2.0 of the .NET framework?
If we need to install the updated version of MSXML 6.0 prior to installing ADOMD.NET, has anyone built a ClickOnce Bootstrapper Prerequisite Package for the updated version of MSXML 6.0?
We realize these components might be part of the SQL Server 2005 Express Edition Prerequisite Package that is available, but would like to avoid an additional 35 mg download if at all possible.
Thanks in advance for your help.
Dont know much about ClickOnce.
Some answers for you:
You are right ADOMD.NET requires MSXML6 to be present. If it is not installed the setup will prompt you.
.NET framework does not include the MSXML 6 component.
I doubt ADOMD.NET is part of SQL Express installation package.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Saturday, February 25, 2012
Adobe Acrobat 8 vs. RS 2005 PDF Rendering
For the last two years I've had an application running in production which would generate and display its reports as PDF via RS 2005. It would take user parameters, render the report, and my application would take the PDF bytestream from RS and save it to a file on disk, then request Windows to open the file. This has worked very smoothly.
I've passed this on to our tech support guys and will be doing a test later today myself on one of our spare workstations. I should be able to replicate the issue our users have seen - at which point I'll play with the Acrobat update options and determine whether they are the cause. I'll post a follow-up comment to this thread with the results.
Recently there has been a push in my company to get Adobe Acrobat 8 deployed, and apparently the same PDFs which have been working all this time will cause Acrobat 8 to choke. By choke, I mean that Acrobat will load into memory but have some sort of problem with the PDFs, and never show up. The users, not realizing what is going on, will then ask for the same report again, causing two stalled instances of Acrobat to be opened now, etc.
Removing the new acrobat and replacing it with Acrobat 7 solves the problem. Long term, this is not a good solution however... Has anyone else had a similar experience? I've googled around and have come up empty.
I've seen Acrobat 8 act that when it cannot communicate properly with the Adobe updater. On a client that is experiencing that behavior, can you launch Acrobat 8 and manually ensure it is up-to-date?
Thanks.
|||Thanks Donovan,I've passed this on to our tech support guys and will be doing a test later today myself on one of our spare workstations. I should be able to replicate the issue our users have seen - at which point I'll play with the Acrobat update options and determine whether they are the cause. I'll post a follow-up comment to this thread with the results.
Friday, February 24, 2012
ADO Timeout & SP
Hi,
Can someone please tell me the expected behavior of a stored procedure
when called via an ADO command object.
My question is, if ADO hits a timeout, will the SP (updates a table)
rollback what it was doing?
Thanks in advance,
Dan.It will either rollback or commit, it won't leave the transaction
hanging, if that's what you're asking. Usually when ADO times out it's
when it's trying to connect, at which time none of your stored
procedures will be in call. If you want to examine what's going on on
the server, open a Profiler trace and step through your code a line at
a time.
-- Mary
MCW Technologies
http://www.mcwtech.com
On 21 Jan 2004 03:43:53 -0800, danielcoates@.yahoo.com (Dan Coates)
wrote:
Can someone please tell me the expected behavior of a stored procedure
when called via an ADO command object.
My question is, if ADO hits a timeout, will the SP (updates a table)
rollback what it was doing?
Thanks in advance,
Dan.It will either rollback or commit, it won't leave the transaction
hanging, if that's what you're asking. Usually when ADO times out it's
when it's trying to connect, at which time none of your stored
procedures will be in call. If you want to examine what's going on on
the server, open a Profiler trace and step through your code a line at
a time.
-- Mary
MCW Technologies
http://www.mcwtech.com
On 21 Jan 2004 03:43:53 -0800, danielcoates@.yahoo.com (Dan Coates)
wrote:
quote:
>Hi,
>Can someone please tell me the expected behavior of a stored procedure
>when called via an ADO command object.
>My question is, if ADO hits a timeout, will the SP (updates a table)
>rollback what it was doing?
>Thanks in advance,
>Dan.
ADO Timeout & SP
Hi,
Can someone please tell me the expected behavior of a stored procedure
when called via an ADO command object.
My question is, if ADO hits a timeout, will the SP (updates a table)
rollback what it was doing?
Thanks in advance,
Dan.It will either rollback or commit, it won't leave the transaction
hanging, if that's what you're asking. Usually when ADO times out it's
when it's trying to connect, at which time none of your stored
procedures will be in call. If you want to examine what's going on on
the server, open a Profiler trace and step through your code a line at
a time.
-- Mary
MCW Technologies
http://www.mcwtech.com
On 21 Jan 2004 03:43:53 -0800, danielcoates@.yahoo.com (Dan Coates)
wrote:
>Hi,
>Can someone please tell me the expected behavior of a stored procedure
>when called via an ADO command object.
>My question is, if ADO hits a timeout, will the SP (updates a table)
>rollback what it was doing?
>Thanks in advance,
>Dan.
Can someone please tell me the expected behavior of a stored procedure
when called via an ADO command object.
My question is, if ADO hits a timeout, will the SP (updates a table)
rollback what it was doing?
Thanks in advance,
Dan.It will either rollback or commit, it won't leave the transaction
hanging, if that's what you're asking. Usually when ADO times out it's
when it's trying to connect, at which time none of your stored
procedures will be in call. If you want to examine what's going on on
the server, open a Profiler trace and step through your code a line at
a time.
-- Mary
MCW Technologies
http://www.mcwtech.com
On 21 Jan 2004 03:43:53 -0800, danielcoates@.yahoo.com (Dan Coates)
wrote:
>Hi,
>Can someone please tell me the expected behavior of a stored procedure
>when called via an ADO command object.
>My question is, if ADO hits a timeout, will the SP (updates a table)
>rollback what it was doing?
>Thanks in advance,
>Dan.
Sunday, February 19, 2012
ADO Recordset result cannot display Chinese
Hi all,
I have created an application that get Chinese data from SQL Server 2000.
I am using ActiveX Data Object 2.5 via ODBC as connection. Most PC work
perfectly. However, there is 1 client PC that cannot display Chinese. It
always show ?. Can anyone give me some tips?
Regards,
Edward HuiIs this a unicode capable client (what version of windows?) with recent
versions of ODBC drivers?
"Edward Hui" <edhui@.asl.com.hk> wrote in message
news:OaUWhmz2DHA.1760@.TK2MSFTNGP10.phx.gbl...
2000.
I have created an application that get Chinese data from SQL Server 2000.
I am using ActiveX Data Object 2.5 via ODBC as connection. Most PC work
perfectly. However, there is 1 client PC that cannot display Chinese. It
always show ?. Can anyone give me some tips?
Regards,
Edward HuiIs this a unicode capable client (what version of windows?) with recent
versions of ODBC drivers?
"Edward Hui" <edhui@.asl.com.hk> wrote in message
news:OaUWhmz2DHA.1760@.TK2MSFTNGP10.phx.gbl...
quote:
> Hi all,
> I have created an application that get Chinese data from SQL Server
2000.
quote:
> I am using ActiveX Data Object 2.5 via ODBC as connection. Most PC work
> perfectly. However, there is 1 client PC that cannot display Chinese. It
> always show ?. Can anyone give me some tips?
> Regards,
> Edward Hui
>
ADO InfoMessage doesn't return all messages
I would like to return messages from a 3 'action' stored procedure to
the user of an Access front end via ADO. I've tried looping through
MyConnection.Errors within the InfoMessage event and this returns the
message I see in QA for each action if the user has only changed 1
record. However if the user first updates more than 1 record in Access
and then executes this stored procedure (via a command object) I still
get back only 1 message per action as opposed to 1 message per action
per record as I do in QA. MyConnection.Errors.Count always stays at 3
no matter how many records are updated, though in QA I get 3 * the
number of records messages. I can also reproduce this with print. QA
will display say 9 print messages for 3 records but ADO will only
display 3 messages, those for the first record in the batch.
I can load all the info into an output parameter but would like to use
InfoMessages to build 1 complete string for Msgbox.You might try adding SET NOCOUNT ON to the beginning of your procs. This
will suppress DONE_IN_PROC (including rowcounts) that can cause problems
with ADO application processing of resultsets and messages.
Hope this helps.
Dan Guzman
SQL Server MVP
"Steve" <morriszone@.hotmail.com> wrote in message
news:1110927775.827057.213060@.o13g2000cwo.googlegroups.com...
>I would like to return messages from a 3 'action' stored procedure to
> the user of an Access front end via ADO. I've tried looping through
> MyConnection.Errors within the InfoMessage event and this returns the
> message I see in QA for each action if the user has only changed 1
> record. However if the user first updates more than 1 record in Access
> and then executes this stored procedure (via a command object) I still
> get back only 1 message per action as opposed to 1 message per action
> per record as I do in QA. MyConnection.Errors.Count always stays at 3
> no matter how many records are updated, though in QA I get 3 * the
> number of records messages. I can also reproduce this with print. QA
> will display say 9 print messages for 3 records but ADO will only
> display 3 messages, those for the first record in the batch.
> I can load all the info into an output parameter but would like to use
> InfoMessages to build 1 complete string for Msgbox.
>
the user of an Access front end via ADO. I've tried looping through
MyConnection.Errors within the InfoMessage event and this returns the
message I see in QA for each action if the user has only changed 1
record. However if the user first updates more than 1 record in Access
and then executes this stored procedure (via a command object) I still
get back only 1 message per action as opposed to 1 message per action
per record as I do in QA. MyConnection.Errors.Count always stays at 3
no matter how many records are updated, though in QA I get 3 * the
number of records messages. I can also reproduce this with print. QA
will display say 9 print messages for 3 records but ADO will only
display 3 messages, those for the first record in the batch.
I can load all the info into an output parameter but would like to use
InfoMessages to build 1 complete string for Msgbox.You might try adding SET NOCOUNT ON to the beginning of your procs. This
will suppress DONE_IN_PROC (including rowcounts) that can cause problems
with ADO application processing of resultsets and messages.
Hope this helps.
Dan Guzman
SQL Server MVP
"Steve" <morriszone@.hotmail.com> wrote in message
news:1110927775.827057.213060@.o13g2000cwo.googlegroups.com...
>I would like to return messages from a 3 'action' stored procedure to
> the user of an Access front end via ADO. I've tried looping through
> MyConnection.Errors within the InfoMessage event and this returns the
> message I see in QA for each action if the user has only changed 1
> record. However if the user first updates more than 1 record in Access
> and then executes this stored procedure (via a command object) I still
> get back only 1 message per action as opposed to 1 message per action
> per record as I do in QA. MyConnection.Errors.Count always stays at 3
> no matter how many records are updated, though in QA I get 3 * the
> number of records messages. I can also reproduce this with print. QA
> will display say 9 print messages for 3 records but ADO will only
> display 3 messages, those for the first record in the batch.
> I can load all the info into an output parameter but would like to use
> InfoMessages to build 1 complete string for Msgbox.
>
Thursday, February 16, 2012
ADO Error Code:0x80040e4d
Hello all,
I use Crystal Report v9, SQL server 2000.
When I try to connect to a Database via ADO, I got the following error.
Login failed.
Details :ADO Error Code:0x80040e4d
Source:Microsoft OLE DB Provider for SQL Server
Description:Login failed for usexxxxxxx
SQL State: 42000
Native Error:18456
Is there anyone how has this problem?
How can I fix this?
Thanks in advance,
Do.
--
Message posted via http://www.sqlmonster.com"Do Park via SQLMonster.com" <forum@.nospam.SQLMonster.com> wrote in message
news:9caa7e6d6eff41c1984f7334221dc753@.SQLMonster.c om...
> Hello all,
>
> I use Crystal Report v9, SQL server 2000.
> When I try to connect to a Database via ADO, I got the following error.
> Login failed.
> Details :ADO Error Code:0x80040e4d
> Source:Microsoft OLE DB Provider for SQL Server
> Description:Login failed for use'xxxxxxx'
> SQL State: 42000
> Native Error:18456
> Is there anyone how has this problem?
> How can I fix this?
> Thanks in advance,
> Do.
> --
> Message posted via http://www.sqlmonster.com
"Login failed" suggests that you need to check the login you're using to
connect with - is it a SQL login, or a Windows account; are you using a DSN
or a connection string; can you connect from osql.exe or Query Analyzer
using the same account (or another account) etc.
Simon|||I use Windows authentication. I can access other databases via the same way
(Crystal Report). I connected this database via ADO successfully two or
three days ago. There was no change in my environment and SQL Server.
Best regards,
Do.
--
Message posted via http://www.sqlmonster.com|||Do Park via SQLMonster.com (forum@.SQLMonster.com) writes:
> I use Windows authentication. I can access other databases via the same
> way (Crystal Report). I connected this database via ADO successfully two
> or three days ago. There was no change in my environment and SQL
> Server.
Probably there was. Unfortunately, it is impossible for us who don't
have access to your environment to tell what is going on. You will
have to see your local admin to sort it out.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
ADO does not add to Errors collection after the second FETCH NEXT in a SP
I'm having trouble obtaining errors raised in a stored
procedure via the ADO Errors collection after the second
FETCH NEXT statement from within that stored procedure.
Consider the following table created in a SQL Server
database:
CREATE TABLE TestTable
(
TestInt int
)
go
INSERT TestTable(TestInt) values(1)
INSERT TestTable(TestInt) values(2)
INSERT TestTable(TestInt) values(3)
This is a very simple table with one column, and three
rows containing the values 1, 2 and 3.
Consider this stored procedure:
CREATE PROCEDURE TestStoredProc
as
BEGIN
set rowcount 0
Set NoCount ON
declare @.TestInt int
declare @.ErrMsg char(7)
declare TestCursor cursor forward_only for
select * from TestTable
open TestCursor
Fetch next from TestCursor into @.TestInt
While @.@.fetch_status<>-1
Begin
select @.ErrMsg = 'Error ' + convert(char, @.testint)
raiserror(@.ErrMsg, 16, 1)
raiserror(@.ErrMsg, 16, 1)
Fetch next from TestCursor into @.TestInt
end
Close TestCursor
DeAllocate TestCursor
return
END
This stored procedure simply defines a cursor on all rows
in TestTable. For each row fetched from the cursor, the
error message 'Error n' is raised twice, where n is the
integer that had just been fetched from the cursor.
Finally, consider this VB code using ADO to execute the
above stored procedure. After the stored procedure is
executed, the code loops through the errors collection,
and creates a message box for each error in the collection:
Private Sub Form_Load()
Dim cn As Connection
Dim cm As Command
Dim oErr As Error
On Error Resume Next
Set cn = CreateObject("ADODB.Connection")
cn.Open "Data Source=<Some SQL Server>; Initial
Catalog=<Some Database Name>; Provider=SQLOLEDB; Persist
Security Info=False; Integrated Security=SSPI"
Set cm = CreateObject("ADODB.Command")
Set cm.ActiveConnection = cn
cm.CommandType = adCmdStoredProc
cm.CommandText = "TestStoredProc"
cm.Execute
For Each oErr In cn.Errors
MsgBox oErr.Description
Next
End
End Sub
When this code is executed, only two message boxes appear
with the message "Error 1".
Any help on this matter would be greatly appreciated :)Does anybody has any suggestions?|||Hi Ivan
You can bet your bottom dollar the focus of any replies will be on the use of the cursor rather than the ADO errors collection.
I know this is just an example - is this curiosity about a quirk you have spotted or a serious problem for you? If the latter, would you mind briefly explaining what your production cursor does as there are limited instances where it is as efficient as a set based solution. It may be that your sproc can be made more effective and your ADO errors issue made irrelevent.|||Of course, it is a serious problem for me. SP where this mechanism is used is a part of the big accounting system. Thus I can’t change it logic.
procedure via the ADO Errors collection after the second
FETCH NEXT statement from within that stored procedure.
Consider the following table created in a SQL Server
database:
CREATE TABLE TestTable
(
TestInt int
)
go
INSERT TestTable(TestInt) values(1)
INSERT TestTable(TestInt) values(2)
INSERT TestTable(TestInt) values(3)
This is a very simple table with one column, and three
rows containing the values 1, 2 and 3.
Consider this stored procedure:
CREATE PROCEDURE TestStoredProc
as
BEGIN
set rowcount 0
Set NoCount ON
declare @.TestInt int
declare @.ErrMsg char(7)
declare TestCursor cursor forward_only for
select * from TestTable
open TestCursor
Fetch next from TestCursor into @.TestInt
While @.@.fetch_status<>-1
Begin
select @.ErrMsg = 'Error ' + convert(char, @.testint)
raiserror(@.ErrMsg, 16, 1)
raiserror(@.ErrMsg, 16, 1)
Fetch next from TestCursor into @.TestInt
end
Close TestCursor
DeAllocate TestCursor
return
END
This stored procedure simply defines a cursor on all rows
in TestTable. For each row fetched from the cursor, the
error message 'Error n' is raised twice, where n is the
integer that had just been fetched from the cursor.
Finally, consider this VB code using ADO to execute the
above stored procedure. After the stored procedure is
executed, the code loops through the errors collection,
and creates a message box for each error in the collection:
Private Sub Form_Load()
Dim cn As Connection
Dim cm As Command
Dim oErr As Error
On Error Resume Next
Set cn = CreateObject("ADODB.Connection")
cn.Open "Data Source=<Some SQL Server>; Initial
Catalog=<Some Database Name>; Provider=SQLOLEDB; Persist
Security Info=False; Integrated Security=SSPI"
Set cm = CreateObject("ADODB.Command")
Set cm.ActiveConnection = cn
cm.CommandType = adCmdStoredProc
cm.CommandText = "TestStoredProc"
cm.Execute
For Each oErr In cn.Errors
MsgBox oErr.Description
Next
End
End Sub
When this code is executed, only two message boxes appear
with the message "Error 1".
Any help on this matter would be greatly appreciated :)Does anybody has any suggestions?|||Hi Ivan
You can bet your bottom dollar the focus of any replies will be on the use of the cursor rather than the ADO errors collection.
I know this is just an example - is this curiosity about a quirk you have spotted or a serious problem for you? If the latter, would you mind briefly explaining what your production cursor does as there are limited instances where it is as efficient as a set based solution. It may be that your sproc can be made more effective and your ADO errors issue made irrelevent.|||Of course, it is a serious problem for me. SP where this mechanism is used is a part of the big accounting system. Thus I can’t change it logic.
Sunday, February 12, 2012
Administering via SQL Mgmt Studio
Are BUILTIN\Administrators (local admins on the server) the only persons
allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
Services (SSRS)? Can others who may have the Content Manager Role on a
folder or that have the System Administrator Role use SSMS? So far my
experience is only BUILTIN\Admins can use SSMS. Anyting special that must be
done to open up the SSMS to Reporting Services for non BUILTIN\Admins?Why do you want someone, who is not DB admin, to use SSMS to "manage"
reporting services' meta database? Even a db manager has few need to manage
reporting services' database directly. Reporting Services is a web
application and it is managed through a web interfaccce (report manager -
http://serverName/reports).
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> Are BUILTIN\Administrators (local admins on the server) the only persons
> allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
> Services (SSRS)? Can others who may have the Content Manager Role on a
> folder or that have the System Administrator Role use SSMS? So far my
> experience is only BUILTIN\Admins can use SSMS. Anyting special that must
> be
> done to open up the SSMS to Reporting Services for non BUILTIN\Admins?|||I have taken 2 Microsoft Reporting Services (webcast) courses, which have
shown all the administration of SSRS taking place in SQL Server Management
Studio. I use SSMS to conduct other database and A.S. work and consider it
convenient to use SSMS to work SSRS issues, as well. At our location, DBAs
are not allowed to be local admins (except for temporary circumstances) as a
Sarbanes-Oxley design result. I think it is interesting that no one answers
my question, but are very willing to question the circumstances.
"Norman Yuan" wrote:
> Why do you want someone, who is not DB admin, to use SSMS to "manage"
> reporting services' meta database? Even a db manager has few need to manage
> reporting services' database directly. Reporting Services is a web
> application and it is managed through a web interfaccce (report manager -
> http://serverName/reports).
>
> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> > Are BUILTIN\Administrators (local admins on the server) the only persons
> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
> > Services (SSRS)? Can others who may have the Content Manager Role on a
> > folder or that have the System Administrator Role use SSMS? So far my
> > experience is only BUILTIN\Admins can use SSMS. Anyting special that must
> > be
> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
>
>|||>>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
>> shown all the administration of SSRS taking place in SQL Server
>> Management
>> Studio. [..]
>>I think it is interesting that no one answers my question, but are very
>>willing to question the circumstances.
It *is* interesting, but it's also interesting that this is how the courses
recommended that you work, IMHO, since it may not be a viable strategy,
long-term.
Please read below, from Brian Welcker's Weblog
(http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
feedback.
Which parts of administering RS were you particularly interested in doing
via SSMS versus Report Manager (just curious)?
(snip) ---
Watusi (SSRS Management Tools Changes for Katmai)
For Katmai we are considering the removal of namespace management (folders,
reports, data sources, models) from the Reporting Services Add-in for SQL
Server Management Studio (SSMS). In other words, we are considering removing
the 'Home' folder under the Reporting Server node in SSMS.
Why the change?
Customer feedback and usage data indicates that Report Manager and/or
SharePoint are the tools of choice for managing the Report Server namespace,
rather than the SSMS add-in. The design constraints of SSMS mean that any
new namespace functionality is significantly expensive to implement,
specifically adding support for the namespace in SharePoint integrated mode.
For Katmai we want to invest in SharePoint and Report Manager for namespace
management and focus on SSMS as a server-level management tool.
This means that the namespace management functions that are not available in
Report Manager (Model ClickThrough and Model Item Security) will be added to
Report Manager (they are already in SharePoint). Job Management, configuring
System properties, and administering Roles will be moved to SSMS. In
addition, SSMS will be updated to work in SharePoint mode.
If you have feedback about these changes, please feel free to comment.
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> shown all the administration of SSRS taking place in SQL Server Management
> Studio. I use SSMS to conduct other database and A.S. work and consider
> it
> convenient to use SSMS to work SSRS issues, as well. At our location,
> DBAs
> are not allowed to be local admins (except for temporary circumstances) as
> a
> Sarbanes-Oxley design result. I think it is interesting that no one
> answers
> my question, but are very willing to question the circumstances.
> "Norman Yuan" wrote:
>> Why do you want someone, who is not DB admin, to use SSMS to "manage"
>> reporting services' meta database? Even a db manager has few need to
>> manage
>> reporting services' database directly. Reporting Services is a web
>> application and it is managed through a web interfaccce (report manager -
>> http://serverName/reports).
>>
>> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
>> > Are BUILTIN\Administrators (local admins on the server) the only
>> > persons
>> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
>> > Reporting
>> > Services (SSRS)? Can others who may have the Content Manager Role on a
>> > folder or that have the System Administrator Role use SSMS? So far my
>> > experience is only BUILTIN\Admins can use SSMS. Anyting special that
>> > must
>> > be
>> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
>>|||Appreciate your feedback and the insight into Katmai. Looks like it is best
to focus on the Report Manager tool. I am responsible for creating new
folders and assigning new accounts / roles. Most other work is done by the
report developers / folder content managers. I am a previous DBA whose work
has been outsourced. I, currently, provide a role of 'moving' the corp. into
new (DBMS, etc. ) software, then working out the details of handing the
support over to the service provider. I am not yet to the point of moving
the support of SSRS to the service providers, due to budgets, and other
administrative hurdles, so I am the current administrator, beyond the
installation of the product.
"Lisa Slater Nicholls" wrote:
> >>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> >> shown all the administration of SSRS taking place in SQL Server
> >> Management
> >> Studio. [..]
> >>I think it is interesting that no one answers my question, but are very
> >>willing to question the circumstances.
> It *is* interesting, but it's also interesting that this is how the courses
> recommended that you work, IMHO, since it may not be a viable strategy,
> long-term.
> Please read below, from Brian Welcker's Weblog
> (http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
> feedback.
> Which parts of administering RS were you particularly interested in doing
> via SSMS versus Report Manager (just curious)?
> (snip) ---
> Watusi (SSRS Management Tools Changes for Katmai)
> For Katmai we are considering the removal of namespace management (folders,
> reports, data sources, models) from the Reporting Services Add-in for SQL
> Server Management Studio (SSMS). In other words, we are considering removing
> the 'Home' folder under the Reporting Server node in SSMS.
> Why the change?
> Customer feedback and usage data indicates that Report Manager and/or
> SharePoint are the tools of choice for managing the Report Server namespace,
> rather than the SSMS add-in. The design constraints of SSMS mean that any
> new namespace functionality is significantly expensive to implement,
> specifically adding support for the namespace in SharePoint integrated mode.
> For Katmai we want to invest in SharePoint and Report Manager for namespace
> management and focus on SSMS as a server-level management tool.
> This means that the namespace management functions that are not available in
> Report Manager (Model ClickThrough and Model Item Security) will be added to
> Report Manager (they are already in SharePoint). Job Management, configuring
> System properties, and administering Roles will be moved to SSMS. In
> addition, SSMS will be updated to work in SharePoint mode.
> If you have feedback about these changes, please feel free to comment.
> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
> >I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> > shown all the administration of SSRS taking place in SQL Server Management
> > Studio. I use SSMS to conduct other database and A.S. work and consider
> > it
> > convenient to use SSMS to work SSRS issues, as well. At our location,
> > DBAs
> > are not allowed to be local admins (except for temporary circumstances) as
> > a
> > Sarbanes-Oxley design result. I think it is interesting that no one
> > answers
> > my question, but are very willing to question the circumstances.
> >
> > "Norman Yuan" wrote:
> >
> >> Why do you want someone, who is not DB admin, to use SSMS to "manage"
> >> reporting services' meta database? Even a db manager has few need to
> >> manage
> >> reporting services' database directly. Reporting Services is a web
> >> application and it is managed through a web interfaccce (report manager -
> >> http://serverName/reports).
> >>
> >>
> >> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> >> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> >> > Are BUILTIN\Administrators (local admins on the server) the only
> >> > persons
> >> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
> >> > Reporting
> >> > Services (SSRS)? Can others who may have the Content Manager Role on a
> >> > folder or that have the System Administrator Role use SSMS? So far my
> >> > experience is only BUILTIN\Admins can use SSMS. Anyting special that
> >> > must
> >> > be
> >> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
> >>
> >>
> >>
>|||>>Looks like it is best to focus on the Report Manager tool.
I didn't actually mean to say that! I meant to say: if you have cogent
reasons why the work you need to do is better done in Management Studio
rather than Report Manager... then MS deserves to hear your reasons <s>.
OTOH... reading that post closely, it seemed clear to me that the RS team
found the required heirarchical arrangement of functionality in Studio
limiting and not really suited to their purposes. They were probably tired
of shoe-horning features into it. In the Report Manager, they have a much
free-er hand and it was probably not necessary for them to split their
effort between implementation of upcoming features in both UIs.
Going forward, I guess we should be happy if they can focus their energy on
one management UI and we get more new features as a result <s>.
Cheers,
>L<
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:D6726064-25F3-45C6-A9DB-C54CD3778868@.microsoft.com...
> Appreciate your feedback and the insight into Katmai. Looks like it is
> best
> to focus on the Report Manager tool. I am responsible for creating new
> folders and assigning new accounts / roles. Most other work is done by
> the
> report developers / folder content managers. I am a previous DBA whose
> work
> has been outsourced. I, currently, provide a role of 'moving' the corp.
> into
> new (DBMS, etc. ) software, then working out the details of handing the
> support over to the service provider. I am not yet to the point of moving
> the support of SSRS to the service providers, due to budgets, and other
> administrative hurdles, so I am the current administrator, beyond the
> installation of the product.
> "Lisa Slater Nicholls" wrote:
>> >>I have taken 2 Microsoft Reporting Services (webcast) courses, which
>> >>have
>> >> shown all the administration of SSRS taking place in SQL Server
>> >> Management
>> >> Studio. [..]
>> >>I think it is interesting that no one answers my question, but are
>> >>very
>> >>willing to question the circumstances.
>> It *is* interesting, but it's also interesting that this is how the
>> courses
>> recommended that you work, IMHO, since it may not be a viable strategy,
>> long-term.
>> Please read below, from Brian Welcker's Weblog
>> (http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
>> feedback.
>> Which parts of administering RS were you particularly interested in doing
>> via SSMS versus Report Manager (just curious)?
>> (snip) ---
>> Watusi (SSRS Management Tools Changes for Katmai)
>> For Katmai we are considering the removal of namespace management
>> (folders,
>> reports, data sources, models) from the Reporting Services Add-in for SQL
>> Server Management Studio (SSMS). In other words, we are considering
>> removing
>> the 'Home' folder under the Reporting Server node in SSMS.
>> Why the change?
>> Customer feedback and usage data indicates that Report Manager and/or
>> SharePoint are the tools of choice for managing the Report Server
>> namespace,
>> rather than the SSMS add-in. The design constraints of SSMS mean that any
>> new namespace functionality is significantly expensive to implement,
>> specifically adding support for the namespace in SharePoint integrated
>> mode.
>> For Katmai we want to invest in SharePoint and Report Manager for
>> namespace
>> management and focus on SSMS as a server-level management tool.
>> This means that the namespace management functions that are not available
>> in
>> Report Manager (Model ClickThrough and Model Item Security) will be added
>> to
>> Report Manager (they are already in SharePoint). Job Management,
>> configuring
>> System properties, and administering Roles will be moved to SSMS. In
>> addition, SSMS will be updated to work in SharePoint mode.
>> If you have feedback about these changes, please feel free to comment.
>> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
>> >I have taken 2 Microsoft Reporting Services (webcast) courses, which
>> >have
>> > shown all the administration of SSRS taking place in SQL Server
>> > Management
>> > Studio. I use SSMS to conduct other database and A.S. work and
>> > consider
>> > it
>> > convenient to use SSMS to work SSRS issues, as well. At our location,
>> > DBAs
>> > are not allowed to be local admins (except for temporary circumstances)
>> > as
>> > a
>> > Sarbanes-Oxley design result. I think it is interesting that no one
>> > answers
>> > my question, but are very willing to question the circumstances.
>> >
>> > "Norman Yuan" wrote:
>> >
>> >> Why do you want someone, who is not DB admin, to use SSMS to "manage"
>> >> reporting services' meta database? Even a db manager has few need to
>> >> manage
>> >> reporting services' database directly. Reporting Services is a web
>> >> application and it is managed through a web interfaccce (report
>> >> manager -
>> >> http://serverName/reports).
>> >>
>> >>
>> >> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> >> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
>> >> > Are BUILTIN\Administrators (local admins on the server) the only
>> >> > persons
>> >> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
>> >> > Reporting
>> >> > Services (SSRS)? Can others who may have the Content Manager Role
>> >> > on a
>> >> > folder or that have the System Administrator Role use SSMS? So far
>> >> > my
>> >> > experience is only BUILTIN\Admins can use SSMS. Anyting special
>> >> > that
>> >> > must
>> >> > be
>> >> > done to open up the SSMS to Reporting Services for non
>> >> > BUILTIN\Admins?
>> >>
>> >>
>> >>
>>
allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
Services (SSRS)? Can others who may have the Content Manager Role on a
folder or that have the System Administrator Role use SSMS? So far my
experience is only BUILTIN\Admins can use SSMS. Anyting special that must be
done to open up the SSMS to Reporting Services for non BUILTIN\Admins?Why do you want someone, who is not DB admin, to use SSMS to "manage"
reporting services' meta database? Even a db manager has few need to manage
reporting services' database directly. Reporting Services is a web
application and it is managed through a web interfaccce (report manager -
http://serverName/reports).
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> Are BUILTIN\Administrators (local admins on the server) the only persons
> allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
> Services (SSRS)? Can others who may have the Content Manager Role on a
> folder or that have the System Administrator Role use SSMS? So far my
> experience is only BUILTIN\Admins can use SSMS. Anyting special that must
> be
> done to open up the SSMS to Reporting Services for non BUILTIN\Admins?|||I have taken 2 Microsoft Reporting Services (webcast) courses, which have
shown all the administration of SSRS taking place in SQL Server Management
Studio. I use SSMS to conduct other database and A.S. work and consider it
convenient to use SSMS to work SSRS issues, as well. At our location, DBAs
are not allowed to be local admins (except for temporary circumstances) as a
Sarbanes-Oxley design result. I think it is interesting that no one answers
my question, but are very willing to question the circumstances.
"Norman Yuan" wrote:
> Why do you want someone, who is not DB admin, to use SSMS to "manage"
> reporting services' meta database? Even a db manager has few need to manage
> reporting services' database directly. Reporting Services is a web
> application and it is managed through a web interfaccce (report manager -
> http://serverName/reports).
>
> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> > Are BUILTIN\Administrators (local admins on the server) the only persons
> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer Reporting
> > Services (SSRS)? Can others who may have the Content Manager Role on a
> > folder or that have the System Administrator Role use SSMS? So far my
> > experience is only BUILTIN\Admins can use SSMS. Anyting special that must
> > be
> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
>
>|||>>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
>> shown all the administration of SSRS taking place in SQL Server
>> Management
>> Studio. [..]
>>I think it is interesting that no one answers my question, but are very
>>willing to question the circumstances.
It *is* interesting, but it's also interesting that this is how the courses
recommended that you work, IMHO, since it may not be a viable strategy,
long-term.
Please read below, from Brian Welcker's Weblog
(http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
feedback.
Which parts of administering RS were you particularly interested in doing
via SSMS versus Report Manager (just curious)?
(snip) ---
Watusi (SSRS Management Tools Changes for Katmai)
For Katmai we are considering the removal of namespace management (folders,
reports, data sources, models) from the Reporting Services Add-in for SQL
Server Management Studio (SSMS). In other words, we are considering removing
the 'Home' folder under the Reporting Server node in SSMS.
Why the change?
Customer feedback and usage data indicates that Report Manager and/or
SharePoint are the tools of choice for managing the Report Server namespace,
rather than the SSMS add-in. The design constraints of SSMS mean that any
new namespace functionality is significantly expensive to implement,
specifically adding support for the namespace in SharePoint integrated mode.
For Katmai we want to invest in SharePoint and Report Manager for namespace
management and focus on SSMS as a server-level management tool.
This means that the namespace management functions that are not available in
Report Manager (Model ClickThrough and Model Item Security) will be added to
Report Manager (they are already in SharePoint). Job Management, configuring
System properties, and administering Roles will be moved to SSMS. In
addition, SSMS will be updated to work in SharePoint mode.
If you have feedback about these changes, please feel free to comment.
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> shown all the administration of SSRS taking place in SQL Server Management
> Studio. I use SSMS to conduct other database and A.S. work and consider
> it
> convenient to use SSMS to work SSRS issues, as well. At our location,
> DBAs
> are not allowed to be local admins (except for temporary circumstances) as
> a
> Sarbanes-Oxley design result. I think it is interesting that no one
> answers
> my question, but are very willing to question the circumstances.
> "Norman Yuan" wrote:
>> Why do you want someone, who is not DB admin, to use SSMS to "manage"
>> reporting services' meta database? Even a db manager has few need to
>> manage
>> reporting services' database directly. Reporting Services is a web
>> application and it is managed through a web interfaccce (report manager -
>> http://serverName/reports).
>>
>> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
>> > Are BUILTIN\Administrators (local admins on the server) the only
>> > persons
>> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
>> > Reporting
>> > Services (SSRS)? Can others who may have the Content Manager Role on a
>> > folder or that have the System Administrator Role use SSMS? So far my
>> > experience is only BUILTIN\Admins can use SSMS. Anyting special that
>> > must
>> > be
>> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
>>|||Appreciate your feedback and the insight into Katmai. Looks like it is best
to focus on the Report Manager tool. I am responsible for creating new
folders and assigning new accounts / roles. Most other work is done by the
report developers / folder content managers. I am a previous DBA whose work
has been outsourced. I, currently, provide a role of 'moving' the corp. into
new (DBMS, etc. ) software, then working out the details of handing the
support over to the service provider. I am not yet to the point of moving
the support of SSRS to the service providers, due to budgets, and other
administrative hurdles, so I am the current administrator, beyond the
installation of the product.
"Lisa Slater Nicholls" wrote:
> >>I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> >> shown all the administration of SSRS taking place in SQL Server
> >> Management
> >> Studio. [..]
> >>I think it is interesting that no one answers my question, but are very
> >>willing to question the circumstances.
> It *is* interesting, but it's also interesting that this is how the courses
> recommended that you work, IMHO, since it may not be a viable strategy,
> long-term.
> Please read below, from Brian Welcker's Weblog
> (http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
> feedback.
> Which parts of administering RS were you particularly interested in doing
> via SSMS versus Report Manager (just curious)?
> (snip) ---
> Watusi (SSRS Management Tools Changes for Katmai)
> For Katmai we are considering the removal of namespace management (folders,
> reports, data sources, models) from the Reporting Services Add-in for SQL
> Server Management Studio (SSMS). In other words, we are considering removing
> the 'Home' folder under the Reporting Server node in SSMS.
> Why the change?
> Customer feedback and usage data indicates that Report Manager and/or
> SharePoint are the tools of choice for managing the Report Server namespace,
> rather than the SSMS add-in. The design constraints of SSMS mean that any
> new namespace functionality is significantly expensive to implement,
> specifically adding support for the namespace in SharePoint integrated mode.
> For Katmai we want to invest in SharePoint and Report Manager for namespace
> management and focus on SSMS as a server-level management tool.
> This means that the namespace management functions that are not available in
> Report Manager (Model ClickThrough and Model Item Security) will be added to
> Report Manager (they are already in SharePoint). Job Management, configuring
> System properties, and administering Roles will be moved to SSMS. In
> addition, SSMS will be updated to work in SharePoint mode.
> If you have feedback about these changes, please feel free to comment.
> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
> >I have taken 2 Microsoft Reporting Services (webcast) courses, which have
> > shown all the administration of SSRS taking place in SQL Server Management
> > Studio. I use SSMS to conduct other database and A.S. work and consider
> > it
> > convenient to use SSMS to work SSRS issues, as well. At our location,
> > DBAs
> > are not allowed to be local admins (except for temporary circumstances) as
> > a
> > Sarbanes-Oxley design result. I think it is interesting that no one
> > answers
> > my question, but are very willing to question the circumstances.
> >
> > "Norman Yuan" wrote:
> >
> >> Why do you want someone, who is not DB admin, to use SSMS to "manage"
> >> reporting services' meta database? Even a db manager has few need to
> >> manage
> >> reporting services' database directly. Reporting Services is a web
> >> application and it is managed through a web interfaccce (report manager -
> >> http://serverName/reports).
> >>
> >>
> >> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> >> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
> >> > Are BUILTIN\Administrators (local admins on the server) the only
> >> > persons
> >> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
> >> > Reporting
> >> > Services (SSRS)? Can others who may have the Content Manager Role on a
> >> > folder or that have the System Administrator Role use SSMS? So far my
> >> > experience is only BUILTIN\Admins can use SSMS. Anyting special that
> >> > must
> >> > be
> >> > done to open up the SSMS to Reporting Services for non BUILTIN\Admins?
> >>
> >>
> >>
>|||>>Looks like it is best to focus on the Report Manager tool.
I didn't actually mean to say that! I meant to say: if you have cogent
reasons why the work you need to do is better done in Management Studio
rather than Report Manager... then MS deserves to hear your reasons <s>.
OTOH... reading that post closely, it seemed clear to me that the RS team
found the required heirarchical arrangement of functionality in Studio
limiting and not really suited to their purposes. They were probably tired
of shoe-horning features into it. In the Report Manager, they have a much
free-er hand and it was probably not necessary for them to split their
effort between implementation of upcoming features in both UIs.
Going forward, I guess we should be happy if they can focus their energy on
one management UI and we get more new features as a result <s>.
Cheers,
>L<
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:D6726064-25F3-45C6-A9DB-C54CD3778868@.microsoft.com...
> Appreciate your feedback and the insight into Katmai. Looks like it is
> best
> to focus on the Report Manager tool. I am responsible for creating new
> folders and assigning new accounts / roles. Most other work is done by
> the
> report developers / folder content managers. I am a previous DBA whose
> work
> has been outsourced. I, currently, provide a role of 'moving' the corp.
> into
> new (DBMS, etc. ) software, then working out the details of handing the
> support over to the service provider. I am not yet to the point of moving
> the support of SSRS to the service providers, due to budgets, and other
> administrative hurdles, so I am the current administrator, beyond the
> installation of the product.
> "Lisa Slater Nicholls" wrote:
>> >>I have taken 2 Microsoft Reporting Services (webcast) courses, which
>> >>have
>> >> shown all the administration of SSRS taking place in SQL Server
>> >> Management
>> >> Studio. [..]
>> >>I think it is interesting that no one answers my question, but are
>> >>very
>> >>willing to question the circumstances.
>> It *is* interesting, but it's also interesting that this is how the
>> courses
>> recommended that you work, IMHO, since it may not be a viable strategy,
>> long-term.
>> Please read below, from Brian Welcker's Weblog
>> (http://blogs.msdn.com/bwelcker/ ) -- you may want to give him some
>> feedback.
>> Which parts of administering RS were you particularly interested in doing
>> via SSMS versus Report Manager (just curious)?
>> (snip) ---
>> Watusi (SSRS Management Tools Changes for Katmai)
>> For Katmai we are considering the removal of namespace management
>> (folders,
>> reports, data sources, models) from the Reporting Services Add-in for SQL
>> Server Management Studio (SSMS). In other words, we are considering
>> removing
>> the 'Home' folder under the Reporting Server node in SSMS.
>> Why the change?
>> Customer feedback and usage data indicates that Report Manager and/or
>> SharePoint are the tools of choice for managing the Report Server
>> namespace,
>> rather than the SSMS add-in. The design constraints of SSMS mean that any
>> new namespace functionality is significantly expensive to implement,
>> specifically adding support for the namespace in SharePoint integrated
>> mode.
>> For Katmai we want to invest in SharePoint and Report Manager for
>> namespace
>> management and focus on SSMS as a server-level management tool.
>> This means that the namespace management functions that are not available
>> in
>> Report Manager (Model ClickThrough and Model Item Security) will be added
>> to
>> Report Manager (they are already in SharePoint). Job Management,
>> configuring
>> System properties, and administering Roles will be moved to SSMS. In
>> addition, SSMS will be updated to work in SharePoint mode.
>> If you have feedback about these changes, please feel free to comment.
>> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> news:14C6CEB9-CA50-4BED-AADF-E3990A6C5B19@.microsoft.com...
>> >I have taken 2 Microsoft Reporting Services (webcast) courses, which
>> >have
>> > shown all the administration of SSRS taking place in SQL Server
>> > Management
>> > Studio. I use SSMS to conduct other database and A.S. work and
>> > consider
>> > it
>> > convenient to use SSMS to work SSRS issues, as well. At our location,
>> > DBAs
>> > are not allowed to be local admins (except for temporary circumstances)
>> > as
>> > a
>> > Sarbanes-Oxley design result. I think it is interesting that no one
>> > answers
>> > my question, but are very willing to question the circumstances.
>> >
>> > "Norman Yuan" wrote:
>> >
>> >> Why do you want someone, who is not DB admin, to use SSMS to "manage"
>> >> reporting services' meta database? Even a db manager has few need to
>> >> manage
>> >> reporting services' database directly. Reporting Services is a web
>> >> application and it is managed through a web interfaccce (report
>> >> manager -
>> >> http://serverName/reports).
>> >>
>> >>
>> >> "LTC" <LTC@.discussions.microsoft.com> wrote in message
>> >> news:3DD2B3EE-6637-476A-BC60-AAF6A9E31D75@.microsoft.com...
>> >> > Are BUILTIN\Administrators (local admins on the server) the only
>> >> > persons
>> >> > allowed to use the SQL Server Mgmt Studio (SSMS) to administer
>> >> > Reporting
>> >> > Services (SSRS)? Can others who may have the Content Manager Role
>> >> > on a
>> >> > folder or that have the System Administrator Role use SSMS? So far
>> >> > my
>> >> > experience is only BUILTIN\Admins can use SSMS. Anyting special
>> >> > that
>> >> > must
>> >> > be
>> >> > done to open up the SSMS to Reporting Services for non
>> >> > BUILTIN\Admins?
>> >>
>> >>
>> >>
>>
Thursday, February 9, 2012
Admin. of SSRS via SQL Server Mgmt Studio
I would like to be able to administer SQL Server Reporting Services (SSRS)
via the SQL Server Management Studio (SSMS). It appears, in our setup at
least, that the only individuals who are able to use the SSMS are those who
are included in the BUILTIN\Administrators group (admins on the server). Our
setup calls for a separation of roles between those who setup/manage the
servers (setup apps on the servers - local admins on the server) and those
who will administer the application after it is installed. I am setup with
the System Administrator Role and with Content Manager in the HOME folder. I
am not able to connect to the SSRS instance via SSMS, where the local admins
(BUILTIN\Administrators) are able to manage SSRS via the SSMS. Is there a
way for the non local admins to use SSMS to administer SSRS?What is it that you are trying to do. Most of the type of admin type work to
do with RS is done via Report Manager (the protal that ships with RS).
Subscriptions, assigning roles, etc. What are you trying to do that you need
to use SSMS to do?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:A4AEDC9B-D588-4DDB-9729-F1A309EDCA39@.microsoft.com...
>I would like to be able to administer SQL Server Reporting Services (SSRS)
> via the SQL Server Management Studio (SSMS). It appears, in our setup at
> least, that the only individuals who are able to use the SSMS are those
> who
> are included in the BUILTIN\Administrators group (admins on the server).
> Our
> setup calls for a separation of roles between those who setup/manage the
> servers (setup apps on the servers - local admins on the server) and those
> who will administer the application after it is installed. I am setup
> with
> the System Administrator Role and with Content Manager in the HOME folder.
> I
> am not able to connect to the SSRS instance via SSMS, where the local
> admins
> (BUILTIN\Administrators) are able to manage SSRS via the SSMS. Is there a
> way for the non local admins to use SSMS to administer SSRS?|||I have been using Report Manager portal for RS, however I use the SSMS to
administer SS DBMS and SSAS. It would be more convenient to work all within
one tool.
"Bruce L-C [MVP]" wrote:
> What is it that you are trying to do. Most of the type of admin type work to
> do with RS is done via Report Manager (the protal that ships with RS).
> Subscriptions, assigning roles, etc. What are you trying to do that you need
> to use SSMS to do?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> news:A4AEDC9B-D588-4DDB-9729-F1A309EDCA39@.microsoft.com...
> >I would like to be able to administer SQL Server Reporting Services (SSRS)
> > via the SQL Server Management Studio (SSMS). It appears, in our setup at
> > least, that the only individuals who are able to use the SSMS are those
> > who
> > are included in the BUILTIN\Administrators group (admins on the server).
> > Our
> > setup calls for a separation of roles between those who setup/manage the
> > servers (setup apps on the servers - local admins on the server) and those
> > who will administer the application after it is installed. I am setup
> > with
> > the System Administrator Role and with Content Manager in the HOME folder.
> > I
> > am not able to connect to the SSRS instance via SSMS, where the local
> > admins
> > (BUILTIN\Administrators) are able to manage SSRS via the SSMS. Is there a
> > way for the non local admins to use SSMS to administer SSRS?
>
>
via the SQL Server Management Studio (SSMS). It appears, in our setup at
least, that the only individuals who are able to use the SSMS are those who
are included in the BUILTIN\Administrators group (admins on the server). Our
setup calls for a separation of roles between those who setup/manage the
servers (setup apps on the servers - local admins on the server) and those
who will administer the application after it is installed. I am setup with
the System Administrator Role and with Content Manager in the HOME folder. I
am not able to connect to the SSRS instance via SSMS, where the local admins
(BUILTIN\Administrators) are able to manage SSRS via the SSMS. Is there a
way for the non local admins to use SSMS to administer SSRS?What is it that you are trying to do. Most of the type of admin type work to
do with RS is done via Report Manager (the protal that ships with RS).
Subscriptions, assigning roles, etc. What are you trying to do that you need
to use SSMS to do?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"LTC" <LTC@.discussions.microsoft.com> wrote in message
news:A4AEDC9B-D588-4DDB-9729-F1A309EDCA39@.microsoft.com...
>I would like to be able to administer SQL Server Reporting Services (SSRS)
> via the SQL Server Management Studio (SSMS). It appears, in our setup at
> least, that the only individuals who are able to use the SSMS are those
> who
> are included in the BUILTIN\Administrators group (admins on the server).
> Our
> setup calls for a separation of roles between those who setup/manage the
> servers (setup apps on the servers - local admins on the server) and those
> who will administer the application after it is installed. I am setup
> with
> the System Administrator Role and with Content Manager in the HOME folder.
> I
> am not able to connect to the SSRS instance via SSMS, where the local
> admins
> (BUILTIN\Administrators) are able to manage SSRS via the SSMS. Is there a
> way for the non local admins to use SSMS to administer SSRS?|||I have been using Report Manager portal for RS, however I use the SSMS to
administer SS DBMS and SSAS. It would be more convenient to work all within
one tool.
"Bruce L-C [MVP]" wrote:
> What is it that you are trying to do. Most of the type of admin type work to
> do with RS is done via Report Manager (the protal that ships with RS).
> Subscriptions, assigning roles, etc. What are you trying to do that you need
> to use SSMS to do?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "LTC" <LTC@.discussions.microsoft.com> wrote in message
> news:A4AEDC9B-D588-4DDB-9729-F1A309EDCA39@.microsoft.com...
> >I would like to be able to administer SQL Server Reporting Services (SSRS)
> > via the SQL Server Management Studio (SSMS). It appears, in our setup at
> > least, that the only individuals who are able to use the SSMS are those
> > who
> > are included in the BUILTIN\Administrators group (admins on the server).
> > Our
> > setup calls for a separation of roles between those who setup/manage the
> > servers (setup apps on the servers - local admins on the server) and those
> > who will administer the application after it is installed. I am setup
> > with
> > the System Administrator Role and with Content Manager in the HOME folder.
> > I
> > am not able to connect to the SSRS instance via SSMS, where the local
> > admins
> > (BUILTIN\Administrators) are able to manage SSRS via the SSMS. Is there a
> > way for the non local admins to use SSMS to administer SSRS?
>
>
Subscribe to:
Posts (Atom)