can not download service pack 2 for xp home after computor restore

i have been trying to re install SP2 for xp home since my computor had to be restored to factory settings,but for some reason it is not being found in automatic updates,it finds 87security updates for xp home but thats it . can anyone help plz

what the tool you used to find the pending updates. use Microsoft Baseline Security Analyzer.. ...otherwise you can directly install sp2 , if select @.@.Version is not showing sp2 ..

http://www.microsoft.com/technet/security/tools/mbsahome.mspx

Madhu

Can not access Excel file using OpenRowset

I am using SQLServer 2005 SP2. I enabled the Ad Hoc Distributed Queries and DisallowAdhocAccess registry option is explicitly set to 0. Query is working fine when I remote desk to the server and execute when I run same query from my workstation I am getting following error

Msg 7399, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" reported an error. The provider did not give any information about the error.

Msg 7303, Level 16, State 1, Line 1

Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)".

Any help is appreciated.

Thanks

--

Farhan

Can you post the text of your query?|||

Here you go ...

Select * FROM OPENDATASOURCE('Microsoft.Jet.OLEDB.4.0',

'Data Source=C:\inventory.xls;Extended Properties=Excel 8.0')...[Laptop$]

|||Can we clarify your original statement?
You wrote that when you execute the statement from the server itself it works.
In that case how do you exactly execute the query? And how do you do it from your workstation?|||

Hello Anton,

I ran the query using SQLServer Management Studio both on Server and Workstation.

Thanks.

|||Connecting to the same server with the same credentials?|||

I think this is a point of view issue. Remember that when you perform OpenRowset, it is looking for that location from the server's point of view. If you create a file on the client at C:\file and try to link to it from the server, it will naturally not find C:\file. You have to specify where the server would find that file, not where it is on the client. This is the same kind of issue that would come up if you try to load a CLR assembly on the server that is built on the client. The file is not within the scope of the server's view and definitely not in the same place so it fails to find it and fails to load, but if you perform the exact same operation on the server, it succeeds. This is because, when performing this operation on the server, the client and server are the same machine and have the same filesystem view. You can work around this issue in a few ways if you need to dynamically link the server to a client file. I suggest either: 1.) upload the file through TCP or an extended stored procedure and link to it from the directory path in the server's view, 2.) create a share and place files on the share that you want to push over to the server, specifying the share should give you a uniform location across client and server and effectively abstract out this detail.

Hope that helps,

John

sql

Can not access Excel file using OpenRowset

I am using SQLServer 2005 SP2. I enabled the Ad Hoc Distributed Queries and DisallowAdhocAccess registry option is explicitly set to 0. Query is working fine when I remote desk to the server and execute when I run same query from my workstation I am getting following error

Msg 7399, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" reported an error. The provider did not give any information about the error.

Msg 7303, Level 16, State 1, Line 1

Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)".

Any help is appreciated.

Thanks

--

Farhan

Can you post the text of your query?|||

Here you go ...

Select * FROM OPENDATASOURCE('Microsoft.Jet.OLEDB.4.0',

'Data Source=C:\inventory.xls;Extended Properties=Excel 8.0')...[Laptop$]

|||Can we clarify your original statement?
You wrote that when you execute the statement from the server itself it works.
In that case how do you exactly execute the query? And how do you do it from your workstation?|||

Hello Anton,

I ran the query using SQLServer Management Studio both on Server and Workstation.

Thanks.

|||Connecting to the same server with the same credentials?|||

I think this is a point of view issue. Remember that when you perform OpenRowset, it is looking for that location from the server's point of view. If you create a file on the client at C:\file and try to link to it from the server, it will naturally not find C:\file. You have to specify where the server would find that file, not where it is on the client. This is the same kind of issue that would come up if you try to load a CLR assembly on the server that is built on the client. The file is not within the scope of the server's view and definitely not in the same place so it fails to find it and fails to load, but if you perform the exact same operation on the server, it succeeds. This is because, when performing this operation on the server, the client and server are the same machine and have the same filesystem view. You can work around this issue in a few ways if you need to dynamically link the server to a client file. I suggest either: 1.) upload the file through TCP or an extended stored procedure and link to it from the directory path in the server's view, 2.) create a share and place files on the share that you want to push over to the server, specifying the share should give you a uniform location across client and server and effectively abstract out this detail.

Hope that helps,

John

Can not access Excel file using OpenRowset

I am using SQLServer 2005 SP2. I enabled the Ad Hoc Distributed Queries and DisallowAdhocAccess registry option is explicitly set to 0. Query is working fine when I remote desk to the server and execute when I run same query from my workstation I am getting following error

Msg 7399, Level 16, State 1, Line 1

The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" reported an error. The provider did not give any information about the error.

Msg 7303, Level 16, State 1, Line 1

Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)".

Any help is appreciated.

Thanks

--

Farhan

Can you post the text of your query?|||

Here you go ...

Select * FROM OPENDATASOURCE('Microsoft.Jet.OLEDB.4.0',

'Data Source=C:\inventory.xls;Extended Properties=Excel 8.0')...[Laptop$]

|||Can we clarify your original statement?
You wrote that when you execute the statement from the server itself it works.
In that case how do you exactly execute the query? And how do you do it from your workstation?|||

Hello Anton,

I ran the query using SQLServer Management Studio both on Server and Workstation.

Thanks.

|||Connecting to the same server with the same credentials?|||

I think this is a point of view issue. Remember that when you perform OpenRowset, it is looking for that location from the server's point of view. If you create a file on the client at C:\file and try to link to it from the server, it will naturally not find C:\file. You have to specify where the server would find that file, not where it is on the client. This is the same kind of issue that would come up if you try to load a CLR assembly on the server that is built on the client. The file is not within the scope of the server's view and definitely not in the same place so it fails to find it and fails to load, but if you perform the exact same operation on the server, it succeeds. This is because, when performing this operation on the server, the client and server are the same machine and have the same filesystem view. You can work around this issue in a few ways if you need to dynamically link the server to a client file. I suggest either: 1.) upload the file through TCP or an extended stored procedure and link to it from the directory path in the server's view, 2.) create a share and place files on the share that you want to push over to the server, specifying the share should give you a uniform location across client and server and effectively abstract out this detail.

Hope that helps,

John

Can no longer connect to SQL Server 2000 using ADO after XP SP2

I can no longer connect to SQL Server 2000 using ADO after installing XP SP2.
I receive authentication error. I have even turned off all firewalls.
I also installed SQL Server Service Pack 4.
I also added the SQL Server data source(ODBC). I am using Windows
Authentication. When I test the ODBC data source it connects successfully.
I just can not access it via ADO.
The receive the error message when I try to open the connection in my program.
Conn.Open
"SQL Server does not exist or access denied."
Can anyone tell me what else I need to do?
RonRon wrote:
> I can no longer connect to SQL Server 2000 using ADO after installing
> XP SP2. I receive authentication error. I have even turned off all
> firewalls.
> I also installed SQL Server Service Pack 4.
> I also added the SQL Server data source(ODBC). I am using Windows
> Authentication. When I test the ODBC data source it connects
> successfully.
> I just can not access it via ADO.
> The receive the error message when I try to open the connection in my
> program. Conn.Open
> "SQL Server does not exist or access denied."
> Can anyone tell me what else I need to do?
> Ron
Can you tell us what your server name is and what connection string you
are passing to the ADO connection object?
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||The server name is: S002542194
Conn.Provider = "SQLOLEDB"
Conn.Properties("Data Source").Value = "S002542194"
Conn.Properties("Initial Catalog").Value = dbstring
Conn.Properties("User ID").Value = user
Conn.Properties("Password").Value = pswd
"David Gugick" wrote:
> Ron wrote:
> > I can no longer connect to SQL Server 2000 using ADO after installing
> > XP SP2. I receive authentication error. I have even turned off all
> > firewalls.
> > I also installed SQL Server Service Pack 4.
> > I also added the SQL Server data source(ODBC). I am using Windows
> > Authentication. When I test the ODBC data source it connects
> > successfully.
> > I just can not access it via ADO.
> > The receive the error message when I try to open the connection in my
> > program. Conn.Open
> > "SQL Server does not exist or access denied."
> > Can anyone tell me what else I need to do?
> > Ron
> Can you tell us what your server name is and what connection string you
> are passing to the ADO connection object?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||FAQ: How Windows XP Service Pack 2 (SP2) Affects SQL Server and MSDE
http://www.microsoft.com/sql/techinfo/administration/2000/security/winxpsp2faq.asp
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:E8DD2341-1928-4D7E-975A-A53294AA05E8@.microsoft.com...
>I can no longer connect to SQL Server 2000 using ADO after installing XP
>SP2.
> I receive authentication error. I have even turned off all firewalls.
> I also installed SQL Server Service Pack 4.
> I also added the SQL Server data source(ODBC). I am using Windows
> Authentication. When I test the ODBC data source it connects
> successfully.
> I just can not access it via ADO.
> The receive the error message when I try to open the connection in my
> program.
> Conn.Open
> "SQL Server does not exist or access denied."
> Can anyone tell me what else I need to do?
> Ron
>
>|||These are the links I have already been to and told me to install SQL Server
SP4.
I did that and it still doesn't work.
What else can I do?
"Mike Epprecht (SQL MVP)" wrote:
> FAQ: How Windows XP Service Pack 2 (SP2) Affects SQL Server and MSDE
> http://www.microsoft.com/sql/techinfo/administration/2000/security/winxpsp2faq.asp
>
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Ron" <Ron@.discussions.microsoft.com> wrote in message
> news:E8DD2341-1928-4D7E-975A-A53294AA05E8@.microsoft.com...
> >I can no longer connect to SQL Server 2000 using ADO after installing XP
> >SP2.
> > I receive authentication error. I have even turned off all firewalls.
> > I also installed SQL Server Service Pack 4.
> > I also added the SQL Server data source(ODBC). I am using Windows
> > Authentication. When I test the ODBC data source it connects
> > successfully.
> > I just can not access it via ADO.
> > The receive the error message when I try to open the connection in my
> > program.
> > Conn.Open
> > "SQL Server does not exist or access denied."
> > Can anyone tell me what else I need to do?
> > Ron
> >
> >
> >
>
>|||Ron wrote:
> The server name is: S002542194
> Conn.Provider = "SQLOLEDB"
> Conn.Properties("Data Source").Value = "S002542194"
> Conn.Properties("Initial Catalog").Value = dbstring
> Conn.Properties("User ID").Value = user
> Conn.Properties("Password").Value = pswd
Make sure there isn't an ODBC data source on the PC with the same name.
If all else fails, try and create an alias from the SQL Server Client
Network Utility using the desire protocol and see if that helps.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||David
There is no other ODBC data source on the PC with the same name.
Can you explain how to create an alias from the SQL Server Client
Network Utility using the desire protocol?
"David Gugick" wrote:
> Ron wrote:
> > The server name is: S002542194
> > Conn.Provider = "SQLOLEDB"
> > Conn.Properties("Data Source").Value = "S002542194"
> > Conn.Properties("Initial Catalog").Value = dbstring
> > Conn.Properties("User ID").Value = user
> > Conn.Properties("Password").Value = pswd
> Make sure there isn't an ODBC data source on the PC with the same name.
> If all else fails, try and create an alias from the SQL Server Client
> Network Utility using the desire protocol and see if that helps.
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>|||Ron wrote:
> David
> There is no other ODBC data source on the PC with the same name.
> Can you explain how to create an alias from the SQL Server Client
> Network Utility using the desire protocol?
Sure. Try both named piped and tcp-ip and use the alias name in the
connection string to see if that works. If it does, it won't address the
problem, but will let you know that you can see the server from that
client.
Snipped from the Coefficient online help...
1.. Run the SQL Server Client Network Utility. You should find this
item under your Start Menu and then under the SQL Server program group.
2.. Click the Alias tab
3.. Click the Add button to add a new alias
4.. Select the Network Library you want to use with the alias. We
recommend you use TCP/IP whenever possible.
5.. Type in the name for the alias in the Server Alias entry field.
This can be any name, but it should not conflict with the real name of
any server or any other alias defined on the client.
6.. Enter the real server name in the Server Name entry field. For a
default instance of SQL Server, specify the server name as it is defined
by the server. For a named instance of SQL Server 2000+, use the
SERVER_NAME\INSTANCE_NAME format.
7.. For TCP/IP, you should elect to Dynamically Determine Port if your
SQL Server is defined on the default port (normally 1433). For a custom
port number, uncheck this option and enter the correct TCP/IP port
number.
8.. For Named Pipes, you will see the default pipe name, which is
normally the correct one. For custom pipe names, enter the correct name
in the Pipe Name entry field.
9.. Press OK twice to exit the Client Network Utility
10.. When you register the server in Coefficient, use the alias name
instead of the real server name.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Can no longer connect to SQL Server 2000 using ADO after XP SP2

I can no longer connect to SQL Server 2000 using ADO after installing XP SP2
.
I receive authentication error. I have even turned off all firewalls.
I also installed SQL Server Service Pack 4.
I also added the SQL Server data source(ODBC). I am using Windows
Authentication. When I test the ODBC data source it connects successfully.
I just can not access it via ADO.
The receive the error message when I try to open the connection in my progra
m.
Conn.Open
"SQL Server does not exist or access denied."
Can anyone tell me what else I need to do?
RonRon wrote:
> I can no longer connect to SQL Server 2000 using ADO after installing
> XP SP2. I receive authentication error. I have even turned off all
> firewalls.
> I also installed SQL Server Service Pack 4.
> I also added the SQL Server data source(ODBC). I am using Windows
> Authentication. When I test the ODBC data source it connects
> successfully.
> I just can not access it via ADO.
> The receive the error message when I try to open the connection in my
> program. Conn.Open
> "SQL Server does not exist or access denied."
> Can anyone tell me what else I need to do?
> Ron
Can you tell us what your server name is and what connection string you
are passing to the ADO connection object?
David Gugick
Quest Software
www.imceda.com
www.quest.com|||FAQ: How Windows XP Service Pack 2 (SP2) Affects SQL Server and MSDE
http://www.microsoft.com/sql/techin...faq.asp

--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:E8DD2341-1928-4D7E-975A-A53294AA05E8@.microsoft.com...
>I can no longer connect to SQL Server 2000 using ADO after installing XP
>SP2.
> I receive authentication error. I have even turned off all firewalls.
> I also installed SQL Server Service Pack 4.
> I also added the SQL Server data source(ODBC). I am using Windows
> Authentication. When I test the ODBC data source it connects
> successfully.
> I just can not access it via ADO.
> The receive the error message when I try to open the connection in my
> program.
> Conn.Open
> "SQL Server does not exist or access denied."
> Can anyone tell me what else I need to do?
> Ron
>
>

Can no longer connect to SQL Server 2000 using ADO after XP SP2

I can no longer connect to SQL Server 2000 using ADO after installing XP SP2.
I receive authentication error. I have even turned off all firewalls.
I also installed SQL Server Service Pack 4.
I also added the SQL Server data source(ODBC). I am using Windows
Authentication. When I test the ODBC data source it connects successfully.
I just can not access it via ADO.
The receive the error message when I try to open the connection in my program.
Conn.Open
"SQL Server does not exist or access denied."
Can anyone tell me what else I need to do?
Ron
Ron wrote:
> I can no longer connect to SQL Server 2000 using ADO after installing
> XP SP2. I receive authentication error. I have even turned off all
> firewalls.
> I also installed SQL Server Service Pack 4.
> I also added the SQL Server data source(ODBC). I am using Windows
> Authentication. When I test the ODBC data source it connects
> successfully.
> I just can not access it via ADO.
> The receive the error message when I try to open the connection in my
> program. Conn.Open
> "SQL Server does not exist or access denied."
> Can anyone tell me what else I need to do?
> Ron
Can you tell us what your server name is and what connection string you
are passing to the ADO connection object?
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||FAQ: How Windows XP Service Pack 2 (SP2) Affects SQL Server and MSDE
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:E8DD2341-1928-4D7E-975A-A53294AA05E8@.microsoft.com...
>I can no longer connect to SQL Server 2000 using ADO after installing XP
>SP2.
> I receive authentication error. I have even turned off all firewalls.
> I also installed SQL Server Service Pack 4.
> I also added the SQL Server data source(ODBC). I am using Windows
> Authentication. When I test the ODBC data source it connects
> successfully.
> I just can not access it via ADO.
> The receive the error message when I try to open the connection in my
> program.
> Conn.Open
> "SQL Server does not exist or access denied."
> Can anyone tell me what else I need to do?
> Ron
>
>

Can I use SQL Server security with reporting services?

I'm using SQL Server 2000 SP3 Reporting Services SP2
Currently my reports are configured to use a shared data source reference.
The credentials for the data source are configured to use the same specified
user name and password, which is a login I created for the purpose of
generating the reports.
Is there a way to pass a SQL Server account user name and password to the
data source instead of using a shared account?
I've tried creating a Data Source Credentials object, but it didn't work:
dim dsc as new DataSourceCredentials
dsc.DataSourceName = "dsn"
dsc.UserName = "unm"
dsc.Password = "pwd"
...
result = rs.Render (...,dsc,...)
...
Unfortunately, I am prevented from using integrated security.
The report renders fine using the data source reference pre-configured with
the shared username and password.
Thanks!
BillHere is what I do and I think is the best thing to do. Create a readonly SQL
Server user account. Use that for your shared datasource. Limit your access
to reports using the built in security model (based on roles). If a user has
rights to run the report they they see the data. They don't need to use
their SQL Server login to do so. This will prevent you from having to manage
SQL Server accounts as much. And, it is better for performance.
By using a single, read only account it means that all database access is
happening through that account which allows connection pooling to do its
magic. Connection pooling only works if the connection string is identical.
Establishing connections is expensive. If you go the route you are
suggesting (which is not possible out of the box, you would have to write
your own forms based authentication and integrate it) then every time a new
user requests a report there will be a new connection being established to
the server.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"BillE" <belgie@.datamti.com> wrote in message
news:ercHCCmCHHA.3924@.TK2MSFTNGP02.phx.gbl...
> I'm using SQL Server 2000 SP3 Reporting Services SP2
> Currently my reports are configured to use a shared data source reference.
> The credentials for the data source are configured to use the same
> specified user name and password, which is a login I created for the
> purpose of generating the reports.
> Is there a way to pass a SQL Server account user name and password to the
> data source instead of using a shared account?
> I've tried creating a Data Source Credentials object, but it didn't work:
> dim dsc as new DataSourceCredentials
> dsc.DataSourceName = "dsn"
> dsc.UserName = "unm"
> dsc.Password = "pwd"
> ...
> result = rs.Render (...,dsc,...)
> ...
> Unfortunately, I am prevented from using integrated security.
> The report renders fine using the data source reference pre-configured
> with the shared username and password.
> Thanks!
> Bill
>
>|||Thanks for your response. This is a grey area for me, and I'm having some
trouble with it.
In the model I'm using, the user selects parameters in a web forms
interface, which builds a URL and submits it to the report server. The
report is rendered in the browser.
If the user bookmarks the report, it can be retrieved at any time from the
report server by opening the bookmark. No login is necessary, since the
report uses the shared login.
I don't see a security context to prevent a user without the appropriate
role membership from accessing a report. Perhaps my entire model is flawed.
Thanks
Bill
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:OhCo0bmCHHA.4892@.TK2MSFTNGP04.phx.gbl...
> Here is what I do and I think is the best thing to do. Create a readonly
> SQL Server user account. Use that for your shared datasource. Limit your
> access to reports using the built in security model (based on roles). If a
> user has rights to run the report they they see the data. They don't need
> to use their SQL Server login to do so. This will prevent you from having
> to manage SQL Server accounts as much. And, it is better for performance.
> By using a single, read only account it means that all database access is
> happening through that account which allows connection pooling to do its
> magic. Connection pooling only works if the connection string is
> identical. Establishing connections is expensive. If you go the route you
> are suggesting (which is not possible out of the box, you would have to
> write your own forms based authentication and integrate it) then every
> time a new user requests a report there will be a new connection being
> established to the server.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "BillE" <belgie@.datamti.com> wrote in message
> news:ercHCCmCHHA.3924@.TK2MSFTNGP02.phx.gbl...
>> I'm using SQL Server 2000 SP3 Reporting Services SP2
>> Currently my reports are configured to use a shared data source
>> reference.
>> The credentials for the data source are configured to use the same
>> specified user name and password, which is a login I created for the
>> purpose of generating the reports.
>> Is there a way to pass a SQL Server account user name and password to the
>> data source instead of using a shared account?
>> I've tried creating a Data Source Credentials object, but it didn't work:
>> dim dsc as new DataSourceCredentials
>> dsc.DataSourceName = "dsn"
>> dsc.UserName = "unm"
>> dsc.Password = "pwd"
>> ...
>> result = rs.Render (...,dsc,...)
>> ...
>> Unfortunately, I am prevented from using integrated security.
>> The report renders fine using the data source reference pre-configured
>> with the shared username and password.
>> Thanks!
>> Bill
>>
>|||RS always has a security context. Being able to have a report rendered is
different from the security used to actually get the data. For the report to
be rendered RS has to know who the user is. It then uses its role based
security to decide whether to provide the service. Then it renders the
report using the security specified for getting the data. Two levels of
security. Rights to run/render the report, rights to get the data. You have
been thinking on the latter when really the issue is more the former.
You have three choices.
1. Create your own authentication. This allows you to have the user log to
your app using the SQL Server login and have that be the login to your app.
You have to integrate this into Reporting Services.
2. Use integrated security where the windows credentials are used to
authenticate into RS. Then integrated security is use for the data source of
the reports as well.
3. Use integrated security where the windows credentials are used to
authenticate into RS. Then, use a fixed SQL Server account (one or more) in
the credentials tab of shared data source.
I do and recommend #3. #1 is non-trivial. #2 is lower performing and in your
case you say you can't use.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"BillE" <belgie@.datamti.com> wrote in message
news:uEuGchnCHHA.3228@.TK2MSFTNGP03.phx.gbl...
> Thanks for your response. This is a grey area for me, and I'm having some
> trouble with it.
> In the model I'm using, the user selects parameters in a web forms
> interface, which builds a URL and submits it to the report server. The
> report is rendered in the browser.
> If the user bookmarks the report, it can be retrieved at any time from the
> report server by opening the bookmark. No login is necessary, since the
> report uses the shared login.
> I don't see a security context to prevent a user without the appropriate
> role membership from accessing a report. Perhaps my entire model is
> flawed.
> Thanks
> Bill
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:OhCo0bmCHHA.4892@.TK2MSFTNGP04.phx.gbl...
>> Here is what I do and I think is the best thing to do. Create a readonly
>> SQL Server user account. Use that for your shared datasource. Limit your
>> access to reports using the built in security model (based on roles). If
>> a user has rights to run the report they they see the data. They don't
>> need to use their SQL Server login to do so. This will prevent you from
>> having to manage SQL Server accounts as much. And, it is better for
>> performance.
>> By using a single, read only account it means that all database access is
>> happening through that account which allows connection pooling to do its
>> magic. Connection pooling only works if the connection string is
>> identical. Establishing connections is expensive. If you go the route you
>> are suggesting (which is not possible out of the box, you would have to
>> write your own forms based authentication and integrate it) then every
>> time a new user requests a report there will be a new connection being
>> established to the server.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "BillE" <belgie@.datamti.com> wrote in message
>> news:ercHCCmCHHA.3924@.TK2MSFTNGP02.phx.gbl...
>> I'm using SQL Server 2000 SP3 Reporting Services SP2
>> Currently my reports are configured to use a shared data source
>> reference.
>> The credentials for the data source are configured to use the same
>> specified user name and password, which is a login I created for the
>> purpose of generating the reports.
>> Is there a way to pass a SQL Server account user name and password to
>> the data source instead of using a shared account?
>> I've tried creating a Data Source Credentials object, but it didn't
>> work:
>> dim dsc as new DataSourceCredentials
>> dsc.DataSourceName = "dsn"
>> dsc.UserName = "unm"
>> dsc.Password = "pwd"
>> ...
>> result = rs.Render (...,dsc,...)
>> ...
>> Unfortunately, I am prevented from using integrated security.
>> The report renders fine using the data source reference pre-configured
>> with the shared username and password.
>> Thanks!
>> Bill
>>
>>
>|||This client has users sharing computers, and they don't want to log off and
log on each time they switch users. However, one user may have access to
some reports which another user doesn't.
I'll have to pursue option #1, or (preferably) convince the client to come
to his senses.
Thanks for your help, I have a clearer understanding of the situation now.
Bill
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%232RmlDoCHHA.4256@.TK2MSFTNGP04.phx.gbl...
> RS always has a security context. Being able to have a report rendered is
> different from the security used to actually get the data. For the report
> to be rendered RS has to know who the user is. It then uses its role based
> security to decide whether to provide the service. Then it renders the
> report using the security specified for getting the data. Two levels of
> security. Rights to run/render the report, rights to get the data. You
> have been thinking on the latter when really the issue is more the former.
> You have three choices.
> 1. Create your own authentication. This allows you to have the user log to
> your app using the SQL Server login and have that be the login to your
> app. You have to integrate this into Reporting Services.
> 2. Use integrated security where the windows credentials are used to
> authenticate into RS. Then integrated security is use for the data source
> of the reports as well.
> 3. Use integrated security where the windows credentials are used to
> authenticate into RS. Then, use a fixed SQL Server account (one or more)
> in the credentials tab of shared data source.
> I do and recommend #3. #1 is non-trivial. #2 is lower performing and in
> your case you say you can't use.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "BillE" <belgie@.datamti.com> wrote in message
> news:uEuGchnCHHA.3228@.TK2MSFTNGP03.phx.gbl...
>> Thanks for your response. This is a grey area for me, and I'm having
>> some trouble with it.
>> In the model I'm using, the user selects parameters in a web forms
>> interface, which builds a URL and submits it to the report server. The
>> report is rendered in the browser.
>> If the user bookmarks the report, it can be retrieved at any time from
>> the report server by opening the bookmark. No login is necessary, since
>> the report uses the shared login.
>> I don't see a security context to prevent a user without the appropriate
>> role membership from accessing a report. Perhaps my entire model is
>> flawed.
>> Thanks
>> Bill
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:OhCo0bmCHHA.4892@.TK2MSFTNGP04.phx.gbl...
>> Here is what I do and I think is the best thing to do. Create a readonly
>> SQL Server user account. Use that for your shared datasource. Limit your
>> access to reports using the built in security model (based on roles). If
>> a user has rights to run the report they they see the data. They don't
>> need to use their SQL Server login to do so. This will prevent you from
>> having to manage SQL Server accounts as much. And, it is better for
>> performance.
>> By using a single, read only account it means that all database access
>> is happening through that account which allows connection pooling to do
>> its magic. Connection pooling only works if the connection string is
>> identical. Establishing connections is expensive. If you go the route
>> you are suggesting (which is not possible out of the box, you would have
>> to write your own forms based authentication and integrate it) then
>> every time a new user requests a report there will be a new connection
>> being established to the server.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "BillE" <belgie@.datamti.com> wrote in message
>> news:ercHCCmCHHA.3924@.TK2MSFTNGP02.phx.gbl...
>> I'm using SQL Server 2000 SP3 Reporting Services SP2
>> Currently my reports are configured to use a shared data source
>> reference.
>> The credentials for the data source are configured to use the same
>> specified user name and password, which is a login I created for the
>> purpose of generating the reports.
>> Is there a way to pass a SQL Server account user name and password to
>> the data source instead of using a shared account?
>> I've tried creating a Data Source Credentials object, but it didn't
>> work:
>> dim dsc as new DataSourceCredentials
>> dsc.DataSourceName = "dsn"
>> dsc.UserName = "unm"
>> dsc.Password = "pwd"
>> ...
>> result = rs.Render (...,dsc,...)
>> ...
>> Unfortunately, I am prevented from using integrated security.
>> The report renders fine using the data source reference pre-configured
>> with the shared username and password.
>> Thanks!
>> Bill
>>
>>
>>
>

Can I somehow subscribe to SQL upgrade notifications?

Well, it's happened again. An upgrade to SQL server was released without my having any idea about it. SP2 came out today and the only way I knew it was I happened to see a headline on Yahoo. Similar things have happened in the past with HotFixes or security rollups. Sometimes it's rather embarrassing, especially when your boss challenges you on the most recent security updates for SQL. Is there any way which we can be notified of new upgrades/updates to SQL Server? I need to know when there is a new hotfix, update, service pack, or whatever so that I can install it as needed. So far, the only way I've found these was by accident. I'm signed up with the Microsoft Download Notification email list, so I was able to see that SP2 CTPs were released, but I've never seen it include hotfixes or rollups.

If something like a SQL update notification service doesn't exist, then I would ask that Microsoft look at putting one together. Thank you!

The download notifications only send out once a week according to the site. http://www.microsoft.com/downloads/render.aspx?content=notifications&displaylang=en

Another good way would be to check out the SQL Server Release Services blog (http://blogs.msdn.com/sqlreleaseservices/) or the other SQL sites linked from Microsoft.com http://www.microsoft.com/sql, http://www.microsoft.com/technet/prodtechnol/sql, and http://msdn.microsoft.com/sql.

Thanks,
Sam Lester (MSFT)

Can I remove SQL Server 2005 SP2 ?

On Jun 12, 11:38 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> I have installed SP2 on a newly installed SQL Server 2005. Then I am aware
> that I have to install the Critical Update for SQL Server 2005 Service Pack
> 2.
> Unfortunately, I have tried MS Update and download the patch manually but
> the install of the critical update fails.
> I would like to know is it possible for me to remove the installed SP2 ?
> Then I will download the latest SP2 and get it installed on the server.
> Thanks
This should help!
http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
John
On Jun 14, 9:25 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> Dear John,
> Many thanks for your info. I have done a further research and found that we
> are not able to uninstall SQL Server 2005 SP2 after installation.
> I still have the same problem and most likely I have to install SQL Server
> 2005 again.
> Thanks
> Peter
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181654373.752891.267700@.r19g2000prf.googlegr oups.com...
>
>
>
>
>
> - Show quoted text -
Hi
The article describes what you should upgrade if you installed the
first release of SP2, moving up to version 3159 would probably be the
best option.
John
|||On Jun 15, 10:55 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> I attempt to uninstall SQL Server 2005 and it asks me to install .NET
> Framework 2.0. It is quite weird as it should have been installed during
> installation of SQL Server 2005.
> After installing .NET Framework 2.0, I am able to run the update
> successfully.
> Regards,
> Peter
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181821434.492775.293850@.n15g2000prd.googlegr oups.com...
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
Hi
Maybe your .NET framework installation was currupted! You should not
have been able to install SQL Server 2005 in the first place if it
wasn't there.
John

Can I remove SQL Server 2005 SP2 ?

I have installed SP2 on a newly installed SQL Server 2005. Then I am aware
that I have to install the Critical Update for SQL Server 2005 Service Pack
2.
Unfortunately, I have tried MS Update and download the patch manually but
the install of the critical update fails.
I would like to know is it possible for me to remove the installed SP2 ?
Then I will download the latest SP2 and get it installed on the server.
ThanksOn Jun 12, 11:38 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> I have installed SP2 on a newly installed SQL Server 2005. Then I am awar
e
> that I have to install the Critical Update for SQL Server 2005 Service Pac
k
> 2.
> Unfortunately, I have tried MS Update and download the patch manually but
> the install of the critical update fails.
> I would like to know is it possible for me to remove the installed SP2 ?
> Then I will download the latest SP2 and get it installed on the server.
> Thanks
This should help!
http://blogs.msdn.com/psssql/archiv...-explained.aspx
John|||Dear John,
Many thanks for your info. I have done a further research and found that we
are not able to uninstall SQL Server 2005 SP2 after installation.
I still have the same problem and most likely I have to install SQL Server
2005 again.
Thanks
Peter
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181654373.752891.267700@.r19g2000prf.googlegroups.com...
> On Jun 12, 11:38 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> This should help!
> http://blogs.msdn.com/psssql/archiv...-explained.aspx
> John
>|||On Jun 14, 9:25 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> Dear John,
> Many thanks for your info. I have done a further research and found that
we
> are not able to uninstall SQL Server 2005 SP2 after installation.
> I still have the same problem and most likely I have to install SQL Server
> 2005 again.
> Thanks
> Peter
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181654373.752891.267700@.r19g2000prf.googlegroups.com...
>
>
>
>
>
>
>
>
> - Show quoted text -
Hi
The article describes what you should upgrade if you installed the
first release of SP2, moving up to version 3159 would probably be the
best option.
John|||I attempt to uninstall SQL Server 2005 and it asks me to install .NET
Framework 2.0. It is quite weird as it should have been installed during
installation of SQL Server 2005.
After installing .NET Framework 2.0, I am able to run the update
successfully.
Regards,
Peter
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181821434.492775.293850@.n15g2000prd.googlegroups.com...
> On Jun 14, 9:25 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> Hi
> The article describes what you should upgrade if you installed the
> first release of SP2, moving up to version 3159 would probably be the
> best option.
> John
>|||On Jun 15, 10:55 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> I attempt to uninstall SQL Server 2005 and it asks me to install .NET
> Framework 2.0. It is quite weird as it should have been installed during
> installation of SQL Server 2005.
> After installing .NET Framework 2.0, I am able to run the update
> successfully.
> Regards,
> Peter
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181821434.492775.293850@.n15g2000prd.googlegroups.com...
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -
Hi
Maybe your .NET framework installation was currupted! You should not
have been able to install SQL Server 2005 in the first place if it
wasn't there.
John

Can I remove SQL Server 2005 SP2 ?

I have installed SP2 on a newly installed SQL Server 2005. Then I am aware
that I have to install the Critical Update for SQL Server 2005 Service Pack
2.
Unfortunately, I have tried MS Update and download the patch manually but
the install of the critical update fails.
I would like to know is it possible for me to remove the installed SP2 ?
Then I will download the latest SP2 and get it installed on the server.
ThanksOn Jun 12, 11:38 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> I have installed SP2 on a newly installed SQL Server 2005. Then I am aware
> that I have to install the Critical Update for SQL Server 2005 Service Pack
> 2.
> Unfortunately, I have tried MS Update and download the patch manually but
> the install of the critical update fails.
> I would like to know is it possible for me to remove the installed SP2 ?
> Then I will download the latest SP2 and get it installed on the server.
> Thanks
This should help!
http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
John|||Dear John,
Many thanks for your info. I have done a further research and found that we
are not able to uninstall SQL Server 2005 SP2 after installation.
I still have the same problem and most likely I have to install SQL Server
2005 again.
Thanks
Peter
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181654373.752891.267700@.r19g2000prf.googlegroups.com...
> On Jun 12, 11:38 am, "Peter" <P...@.discussions.microsoft.com> wrote:
>> I have installed SP2 on a newly installed SQL Server 2005. Then I am
>> aware
>> that I have to install the Critical Update for SQL Server 2005 Service
>> Pack
>> 2.
>> Unfortunately, I have tried MS Update and download the patch manually but
>> the install of the critical update fails.
>> I would like to know is it possible for me to remove the installed SP2 ?
>> Then I will download the latest SP2 and get it installed on the server.
>> Thanks
> This should help!
> http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx
> John
>|||On Jun 14, 9:25 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> Dear John,
> Many thanks for your info. I have done a further research and found that we
> are not able to uninstall SQL Server 2005 SP2 after installation.
> I still have the same problem and most likely I have to install SQL Server
> 2005 again.
> Thanks
> Peter
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181654373.752891.267700@.r19g2000prf.googlegroups.com...
>
> > On Jun 12, 11:38 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> >> I have installed SP2 on a newly installed SQL Server 2005. Then I am
> >> aware
> >> that I have to install the Critical Update for SQL Server 2005 Service
> >> Pack
> >> 2.
> >> Unfortunately, I have tried MS Update and download the patch manually but
> >> the install of the critical update fails.
> >> I would like to know is it possible for me to remove the installed SP2 ?
> >> Then I will download the latest SP2 and get it installed on the server.
> >> Thanks
> > This should help!
> >http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-...
> > John- Hide quoted text -
> - Show quoted text -
Hi
The article describes what you should upgrade if you installed the
first release of SP2, moving up to version 3159 would probably be the
best option.
John|||I attempt to uninstall SQL Server 2005 and it asks me to install .NET
Framework 2.0. It is quite weird as it should have been installed during
installation of SQL Server 2005.
After installing .NET Framework 2.0, I am able to run the update
successfully.
Regards,
Peter
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181821434.492775.293850@.n15g2000prd.googlegroups.com...
> On Jun 14, 9:25 am, "Peter" <P...@.discussions.microsoft.com> wrote:
>> Dear John,
>> Many thanks for your info. I have done a further research and found that
>> we
>> are not able to uninstall SQL Server 2005 SP2 after installation.
>> I still have the same problem and most likely I have to install SQL
>> Server
>> 2005 again.
>> Thanks
>> Peter
>> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
>> news:1181654373.752891.267700@.r19g2000prf.googlegroups.com...
>>
>> > On Jun 12, 11:38 am, "Peter" <P...@.discussions.microsoft.com> wrote:
>> >> I have installed SP2 on a newly installed SQL Server 2005. Then I am
>> >> aware
>> >> that I have to install the Critical Update for SQL Server 2005 Service
>> >> Pack
>> >> 2.
>> >> Unfortunately, I have tried MS Update and download the patch manually
>> >> but
>> >> the install of the critical update fails.
>> >> I would like to know is it possible for me to remove the installed SP2
>> >> ?
>> >> Then I will download the latest SP2 and get it installed on the
>> >> server.
>> >> Thanks
>> > This should help!
>> >http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-...
>> > John- Hide quoted text -
>> - Show quoted text -
> Hi
> The article describes what you should upgrade if you installed the
> first release of SP2, moving up to version 3159 would probably be the
> best option.
> John
>|||On Jun 15, 10:55 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> I attempt to uninstall SQL Server 2005 and it asks me to install .NET
> Framework 2.0. It is quite weird as it should have been installed during
> installation of SQL Server 2005.
> After installing .NET Framework 2.0, I am able to run the update
> successfully.
> Regards,
> Peter
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181821434.492775.293850@.n15g2000prd.googlegroups.com...
>
> > On Jun 14, 9:25 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> >> Dear John,
> >> Many thanks for your info. I have done a further research and found that
> >> we
> >> are not able to uninstall SQL Server 2005 SP2 after installation.
> >> I still have the same problem and most likely I have to install SQL
> >> Server
> >> 2005 again.
> >> Thanks
> >> Peter
> >> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> >>news:1181654373.752891.267700@.r19g2000prf.googlegroups.com...
> >> > On Jun 12, 11:38 am, "Peter" <P...@.discussions.microsoft.com> wrote:
> >> >> I have installed SP2 on a newly installed SQL Server 2005. Then I am
> >> >> aware
> >> >> that I have to install the Critical Update for SQL Server 2005 Service
> >> >> Pack
> >> >> 2.
> >> >> Unfortunately, I have tried MS Update and download the patch manually
> >> >> but
> >> >> the install of the critical update fails.
> >> >> I would like to know is it possible for me to remove the installed SP2
> >> >> ?
> >> >> Then I will download the latest SP2 and get it installed on the
> >> >> server.
> >> >> Thanks
> >> > This should help!
> >> >http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-...
> >> > John- Hide quoted text -
> >> - Show quoted text -
> > Hi
> > The article describes what you should upgrade if you installed the
> > first release of SP2, moving up to version 3159 would probably be the
> > best option.
> > John- Hide quoted text -
> - Show quoted text -
Hi
Maybe your .NET framework installation was currupted! You should not
have been able to install SQL Server 2005 in the first place if it
wasn't there.
John

Can I install SQL2005 SP2 to TFS server?

Hi!

We have a TFS server include this components:

windows standard R2 server + SP1

Microsoft SQL Server 2005 + SP1

Microsoft Visual Studio 2005 Team Foundation Server - ENU + SP1

Microsoft Windows SharePoint Services 2.0.

Can I install sql 2005 SP2 without any problem?

Best Regards,

Mihaly Demeczky

To my knowledge, there are no know issues with adding SQL Server 2005 SP2. If your SQL Sevrer is on a VHD, make a copy, otherwise, set a 'SavePoint' -just in case.