Showing posts with label access. Show all posts
Showing posts with label access. Show all posts

Friday, March 30, 2012

Remove header using URL access

I have a report that has parameters. The report is called from a webpage using URL access. I know how to remove the toolbar or parameters with "&rc:Toolbar=false or &rcStick out tonguearameters=false". I want to remove only the header which displays SQL Server Report Services, the folder it is found in, the report name, Home | My Subscription | Help , Search for box, and the tabs (View, Properties, History, and Subscriptions). I cannot find an URL access parameter that will only remove this header information. I want to keep the parameter box and the toolbar. Does anyone have any ideas on the subject?

Fred

For this type of customization of report manager, you will probably need to create your own application in Visual Studio 2005 and use a report viewer.

Report manager is not very customizable.

|||

How difficult would it be to write a program to display the parameters like Reporting Services does and to use the selected parameter to refresh the report like Reporting Services does? Any samples?

Fred

|||

You can do this by linking to the report via the reportserver virtual directory rather than the report manager.

Try navigating to http://<your_server>/reportserver and then click through to your report. You will see that the report parameters and toolbar are still visible. Copy the URL and get your application to link to that instead.

|||

Adam,

Yes, this displays the parameters and toolbar, but it also displays the header information which is above the parameter section. I do not want my endusers to see this information ( as mentioned in the first post in this series). This information allows the user to navigate Report Manager which will confuse them. I only want them to see the report with the parameters and toolbar.

Fred

|||

Fred,

Can I suggest that you actually try the solution or read the post properly before commenting!

My suggestetion is based on a live system and I assure you it delivers exactly what you have desribed.

When I navigate to my report using the following URL https://servername/reportserver?%2fReports%2fReport+1&rs:Command=Render

I see this:

If I add &rc: parameters=collapsed to the URL I get this:

I popup my window from a piece of javascript where I use the following code:

Code Snippet

function openReport(name, parameters)

{

if(typeof(parameters) == "undefined") parameters = "";

var encodedName = name;

while(encodedName.indexOf(" ") != -1)

{

encodedName = encodedName.replace(" ", "+");

}

encodedName = escape(encodedName);

var URL = "/reportserver?%2fReports%2f"
+ encodedName
+ "&rs:Command=Render&rc:parameters=collapsed"
+ parameters;

var features = "resizable=yes"
+ ",location=no"
+ ",menubar=no"
+ ",status=no"
+ ",toolbar=no"
+ ",width=" + screen.width
+ ",height=" + screen.height
+ ",top=0"
+ ",left=0";


window.open(URL, "", features).focus();

return true;

}

|||

Adam,

I apologize. I did not read your post correctly. I was using Report Manager and navigated to my report from the home page. Once I used the ReportServer directory I saw that it was exactly what I wanted.

Thank you,

Fred

Remove header using URL access

I have a report that has parameters. The report is called from a webpage using URL access. I know how to remove the toolbar or parameters with "&rc:Toolbar=false or &rcStick out tonguearameters=false". I want to remove only the header which displays SQL Server Report Services, the folder it is found in, the report name, Home | My Subscription | Help , Search for box, and the tabs (View, Properties, History, and Subscriptions). I cannot find an URL access parameter that will only remove this header information. I want to keep the parameter box and the toolbar. Does anyone have any ideas on the subject?

Fred

For this type of customization of report manager, you will probably need to create your own application in Visual Studio 2005 and use a report viewer.

Report manager is not very customizable.

|||

How difficult would it be to write a program to display the parameters like Reporting Services does and to use the selected parameter to refresh the report like Reporting Services does? Any samples?

Fred

|||

You can do this by linking to the report via the reportserver virtual directory rather than the report manager.

Try navigating to http://<your_server>/reportserver and then click through to your report. You will see that the report parameters and toolbar are still visible. Copy the URL and get your application to link to that instead.

|||

Adam,

Yes, this displays the parameters and toolbar, but it also displays the header information which is above the parameter section. I do not want my endusers to see this information ( as mentioned in the first post in this series). This information allows the user to navigate Report Manager which will confuse them. I only want them to see the report with the parameters and toolbar.

Fred

|||

Fred,

Can I suggest that you actually try the solution or read the post properly before commenting!

My suggestetion is based on a live system and I assure you it delivers exactly what you have desribed.

When I navigate to my report using the following URL https://servername/reportserver?%2fReports%2fReport+1&rs:Command=Render

I see this:

If I add &rc: parameters=collapsed to the URL I get this:

I popup my window from a piece of javascript where I use the following code:

Code Snippet

function openReport(name, parameters)

{

if(typeof(parameters) == "undefined") parameters = "";

var encodedName = name;

while(encodedName.indexOf(" ") != -1)

{

encodedName = encodedName.replace(" ", "+");

}

encodedName = escape(encodedName);

var URL = "/reportserver?%2fReports%2f"
+ encodedName
+ "&rs:Command=Render&rc:parameters=collapsed"
+ parameters;

var features = "resizable=yes"
+ ",location=no"
+ ",menubar=no"
+ ",status=no"
+ ",toolbar=no"
+ ",width=" + screen.width
+ ",height=" + screen.height
+ ",top=0"
+ ",left=0";


window.open(URL, "", features).focus();

return true;

}

|||

Adam,

I apologize. I did not read your post correctly. I was using Report Manager and navigated to my report from the home page. Once I used the ReportServer directory I saw that it was exactly what I wanted.

Thank you,

Fred

sql

Wednesday, March 28, 2012

Remove domain admins access to SQL 2005 DBs

Hello,
Could you please advise how can I remove domain admins' access to SQL
databases on SQL Server 2005? Is there any only SQL Authentication mode ?OzzY
There is BUILTIN\Administrators group undfer Security folder. You can deny
access to database engine for this group
"OzzY" <apexgore@.yahoo.com> wrote in message
news:uKGdYUt1HHA.3400@.TK2MSFTNGP03.phx.gbl...
> Hello,
> Could you please advise how can I remove domain admins' access to SQL
> databases on SQL Server 2005? Is there any only SQL Authentication mode ?
>|||Before removing the BUILTIN\Administrators, make sure you
have another account that is a sysadmin that you can use to
get into SQL Server.
There isn't a SQL Authentication only mode - mostly because
Windows authentication is more secure. But you can remove
the BUILTIN\Administrators group. That is how the domain
admins inherit access to SQL Server - the
BUILTIN\Administrators group is the local admins group on
the box. Domain admins are members of the local admins group
on the box. And that's how they get access - all through
windows group membership and the BUILTIN\Administrators or
local admins group being setup as sysadmins on SQL Server.
-Sue
On Sat, 4 Aug 2007 23:21:50 +0300, "OzzY"
<apexgore@.yahoo.com> wrote:

>Hello,
>Could you please advise how can I remove domain admins' access to SQL
>databases on SQL Server 2005? Is there any only SQL Authentication mode ?
>

remove cascade update and delete from table

hello, once upon a time when i created my db (originally in access then used the conversion tool, which i now know is wrong!) i thought it would be an amazing idea to have cascading updates and deletes, however it turns out now this is exactly not what i want! if i leave them in then it throws errors when i delete records out of my stock table as related records are in the order_line table here is the code (well i think so, im not the best at sqlserver as you probably can tell already) that im using if anyone can help or point me in the right direction that would be great, thanks

USE [nashdfDB1]GO/****** Object: Table [dbo].[tbl_stock] Script Date: 07/13/2007 02:52:14 ******/SET ANSI_NULLS ONGOSET QUOTED_IDENTIFIER ONGOSET ANSI_PADDING ONGOCREATE TABLE [dbo].[tbl_stock]( [Stock_ID] [int] IDENTITY(1,1) NOT NULL, [cat_id] [int] NOT NULL CONSTRAINT [DF__tbl_stock__cat_i__15502E78] DEFAULT ((0)), [sub_cat_id] [int] NULL CONSTRAINT [DF__tbl_stock__sub_c__164452B1] DEFAULT ((0)), [location] [int] NULL CONSTRAINT [DF__tbl_stock__locat__173876EA] DEFAULT ((0)), [n_or_sh] [varchar](50) NULL, [title] [varchar](255) NULL, [description] [varchar](255) NULL, [size] [varchar](50) NULL, [colour] [varchar](50) NULL, [cost_price] [decimal](9, 2) NULL CONSTRAINT [DF__tbl_stock__cost___182C9B23] DEFAULT ((0)), [selling_price] [decimal](9, 2) NULL CONSTRAINT [DF__tbl_stock__selli__1920BF5C] DEFAULT ((0)), [qty] [varchar](50) NULL, [date] [datetime] NULL CONSTRAINT [DF__tbl_stock__date__1A14E395] DEFAULT (getdate()), [condition] [varchar](255) NULL, [notes] [varchar](255) NULL, [visible] [bit] NULL CONSTRAINT [DF__tbl_stock__visib__1B0907CE] DEFAULT ((1)), [picture1] [varchar](50) NULL, [picture1_thumb] [varchar](50) NULL, [picture2] [varchar](50) NULL, [picture2_thumb] [varchar](50) NULL, [picture3] [varchar](50) NULL, [picture3_thumb] [varchar](50) NULL, [picture4] [varchar](50) NULL, [picture4_thumb] [varchar](50) NULL, [display_price] [varchar](50) NULL, [created_by] [varchar](50) NULL, [buying_in_recipt] [varchar](255) NULL, CONSTRAINT [tbl_stock$PrimaryKey] PRIMARY KEY CLUSTERED( [Stock_ID] ASC)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]) ON [PRIMARY] GO

SET ANSI_PADDING OFF

Regards

Jez

It's hard to read all that DDL but here's the syntax:

ALTER TABLE <table_name>
DROP FOREIGN KEY <foreignkey_name>

See eghttp://www.infogoal.com/sql/sql-drop-foreignkey.htm

You can read more about constraints athttp://www.mssqlcity.com/Articles/General/using_constraints.htm and you can get the full alter table syntax athttp://msdn2.microsoft.com/en-us/library/aa275462(SQL.80).aspx

Monday, March 26, 2012

remove 10 000 records limit

Hi,
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted afte
r
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
ThanksHere's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.

> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutc
h)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
--
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:

> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted af
ter
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
[vbcol=seagreen]
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in du
tch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:
>

remove 10 000 records limit

Hi,
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted after
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
ThanksHere's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutch)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
--
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in dutch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:
> > Hi,
> >
> > Our users that connect to a MSSQL db via MS-Access cannot access more than
> > 10 000 records. In other words, all the records that have been inserted after
> > the 10 000th record cannot be access nor from the table, nor from a query.
> >
> > Is there any way to overcome the problem?
> >
> > Thanks

remove 10 000 records limit

Hi,
Our users that connect to a MSSQL db via MS-Access cannot access more than
10 000 records. In other words, all the records that have been inserted after
the 10 000th record cannot be access nor from the table, nor from a query.
Is there any way to overcome the problem?
Thanks
Here's a not so awesome way:
Create all your tables without data. When they need data you create a
connection in code and snapshot the data out of SQL into your Access
tables.
Frankly, that just sux. I've not heard of a 10,000 record limit in Access.
Can you point me to an MSDN are similar article that talks about this. I
would be interested in looking into this a little more.

> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after the 10 000th record cannot be access nor from the table, nor from a
> query.
|||We have users using linked tables in Access to connect to SQL Server and
there is no such limit.
Ben Nevarez
"DexterV" <DexterV@.discussions.microsoft.com> wrote in message
news:CA155716-7F98-4D64-9318-EF816ADA42BB@.microsoft.com...
> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted
> after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks
|||Dexter,
This is an option in the ms-access settings, probably to avoid long lists
being sent accross the network,
to augment the limit: I'll try to guide you (my ms-access version is in dutch)
go to the ms-access menu tools / options, the option dialog box opens.
There is a tab called edit/find and in there is there is text box with the
limit number like 10000
Hope this helps
Jan D''Hondt
<Toto, I''ve got a feeling we''re not in Kansas anymore.>
SQL database and .NET solutions
"DexterV" wrote:

> Hi,
> Our users that connect to a MSSQL db via MS-Access cannot access more than
> 10 000 records. In other words, all the records that have been inserted after
> the 10 000th record cannot be access nor from the table, nor from a query.
> Is there any way to overcome the problem?
> Thanks
|||Thanks Jan,
Actually, I found the max. record limit parameter on the advanced tab.
I should have explored Ms-access options first.
"Jan D''Hondt" wrote:
[vbcol=seagreen]
> Dexter,
> This is an option in the ms-access settings, probably to avoid long lists
> being sent accross the network,
> to augment the limit: I'll try to guide you (my ms-access version is in dutch)
> go to the ms-access menu tools / options, the option dialog box opens.
> There is a tab called edit/find and in there is there is text box with the
> limit number like 10000
> Hope this helps
> --
> Jan D''Hondt
> <Toto, I''ve got a feeling we''re not in Kansas anymore.>
> SQL database and .NET solutions
>
> "DexterV" wrote:

Friday, March 23, 2012

Remote Web Report timing out

I've got an internal Reporting Server and I can access the reports directly
there with no problem.
I can generate a report with the WinForm without a problem as well.
What I'm trying to do is to use a second, public web server that has an ASPX
page containing the reportviewer control that connects to the internal web
server so we can implment the seucurity system used by the rest of the web
site.
I can open the report, which has an input parameter without a problem. When
I enter a parameter and attempt to generate the report, it connects to the
Report Server without a problem but then sits there, spinning the little
green arrow until it times out.
With profiler turned on I can see the exact same set of data calls being
made when the report is run on the report server, in the WinForm and in the
WebForm, the only difference being that it appears the WebForm never gets the
data back.
Any ideas?
--
Josef
http://www.reluctantdba.comOn Sep 13, 9:54 am, Josef Finsel
<JosefFin...@.discussions.microsoft.com> wrote:
> I've got an internal Reporting Server and I can access the reports directly
> there with no problem.
> I can generate a report with the WinForm without a problem as well.
> What I'm trying to do is to use a second, public web server that has an ASPX
> page containing the reportviewer control that connects to the internal web
> server so we can implment the seucurity system used by the rest of the web
> site.
> I can open the report, which has an input parameter without a problem. When
> I enter a parameter and attempt to generate the report, it connects to the
> Report Server without a problem but then sits there, spinning the little
> green arrow until it times out.
> With profiler turned on I can see the exact same set of data calls being
> made when the report is run on the report server, in the WinForm and in the
> WebForm, the only difference being that it appears the WebForm never gets the
> data back.
> Any ideas?
> --
> Josefhttp://www.reluctantdba.com
Normally hitting the web server will be slower if it is on another
machine/server. Also, communicating through IIS and a network takes
extra time. The only suggestion I have is to tune the query/stored
procedure that sources the report via the Database Engine Tuning
Advisor. This might give you a little performance improvement. Hope
this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Those are all good and valid points but it turns out that it was actually a
permissions issue.
I got it resolved and it works fine.
Thanks
--
Josef
http://www.reluctantdba.com
"EMartinez" wrote:
> On Sep 13, 9:54 am, Josef Finsel
> <JosefFin...@.discussions.microsoft.com> wrote:
> > I've got an internal Reporting Server and I can access the reports directly
> > there with no problem.
> >
> > I can generate a report with the WinForm without a problem as well.
> >
> > What I'm trying to do is to use a second, public web server that has an ASPX
> > page containing the reportviewer control that connects to the internal web
> > server so we can implment the seucurity system used by the rest of the web
> > site.
> >
> > I can open the report, which has an input parameter without a problem. When
> > I enter a parameter and attempt to generate the report, it connects to the
> > Report Server without a problem but then sits there, spinning the little
> > green arrow until it times out.
> >
> > With profiler turned on I can see the exact same set of data calls being
> > made when the report is run on the report server, in the WinForm and in the
> > WebForm, the only difference being that it appears the WebForm never gets the
> > data back.
> >
> > Any ideas?
> > --
> > Josefhttp://www.reluctantdba.com
>
> Normally hitting the web server will be slower if it is on another
> machine/server. Also, communicating through IIS and a network takes
> extra time. The only suggestion I have is to tune the query/stored
> procedure that sources the report via the Database Engine Tuning
> Advisor. This might give you a little performance improvement. Hope
> this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Sep 14, 4:02 pm, Josef Finsel
<JosefFin...@.discussions.microsoft.com> wrote:
> Those are all good and valid points but it turns out that it was actually a
> permissions issue.
> I got it resolved and it works fine.
> Thanks
> --
> Josefhttp://www.reluctantdba.com
> "EMartinez" wrote:
> > On Sep 13, 9:54 am, Josef Finsel
> > <JosefFin...@.discussions.microsoft.com> wrote:
> > > I've got an internal Reporting Server and I can access the reports directly
> > > there with no problem.
> > > I can generate a report with the WinForm without a problem as well.
> > > What I'm trying to do is to use a second, public web server that has an ASPX
> > > page containing the reportviewer control that connects to the internal web
> > > server so we can implment the seucurity system used by the rest of the web
> > > site.
> > > I can open the report, which has an input parameter without a problem. When
> > > I enter a parameter and attempt to generate the report, it connects to the
> > > Report Server without a problem but then sits there, spinning the little
> > > green arrow until it times out.
> > > With profiler turned on I can see the exact same set of data calls being
> > > made when the report is run on the report server, in the WinForm and in the
> > > WebForm, the only difference being that it appears the WebForm never gets the
> > > data back.
> > > Any ideas?
> > > --
> > > Josefhttp://www.reluctantdba.com
> > Normally hitting the web server will be slower if it is on another
> > machine/server. Also, communicating through IIS and a network takes
> > extra time. The only suggestion I have is to tune the query/stored
> > procedure that sources the report via the Database Engine Tuning
> > Advisor. This might give you a little performance improvement. Hope
> > this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
Glad you resolved the issue. Let me know if I can be of further
assistance.
Regards,
Enrique Martinez
Sr. Software Consultant

Remote tools install error

I am trying to install SQL server 2000 client tools on to a Win 2000 server.
I get an install error
' installation of MS data access components failed (-).
My server is service pack 3. I understand that that Win 2 K service pack 3
installs MDAC 2.5 SP3.
My MDAC version is 2.53.6200.1
Has anyone seen this error before and is there a fix for getting the client
tools install to work?
Thanks.
JTThanks for your replies. My struggle continues.
I was able to run sqlsetup in debug mode and installed all other client tool
components other than mdac.
I ran mdac component checker to confirm that I am running mdac version 2.5
SP3 - no conflicts seen with the component checker.
I tried to install mdac 6 from the SQL server disk, but the install appeared
to do nothing.
I downloaded mdac 2.6 SP1 and tried to install it but it failed.
I tried to uninstall the sql tools install but it fails with msg ' internal
error - unable to load or call an external .dll
I have tried to reinstall the tools through the setup maintenance mode. It
appears to install a few files and then finishes, but I can't get in to
Enterprise Mgr or any of the other tools.
I deleted the ExceptionComponents reg key, and attempted to reinstall, but I
am getting nowhere with that.
I am trying to install this on a W2K server w/ terminal services running. I
stopped the terminal services service and tried again to install, but I am
not making any progress with that either.
So how does one uninstall these client tools and start over?
Thanks.
"Dinesh.T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:ugUwZspZDHA.2032@.TK2MSFTNGP10.phx.gbl...
> Jane,
> I have listed some options in..
> Q: "Installation of the Microsoft Data Access Components package failed.
> (-1)"-- Error occurs during setup ?
> http://www.tkdinesh.com/faq/ans/MDACerr.html
>
> --
> Dinesh.
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane Tunnicliff" <jtunn@.uwpn.org> wrote in message
> news:O41l$opZDHA.2548@.TK2MSFTNGP09.phx.gbl...
> > I am trying to install SQL server 2000 client tools on to a Win 2000
> server.
> > I get an install error
> > ' installation of MS data access components failed (-).
> >
> > My server is service pack 3. I understand that that Win 2 K service
pack
> 3
> > installs MDAC 2.5 SP3.
> > My MDAC version is 2.53.6200.1
> >
> > Has anyone seen this error before and is there a fix for getting the
> client
> > tools install to work?
> >
> > Thanks.
> >
> > JT
> >
> >
>

Wednesday, March 21, 2012

Remote synchronization

Hi
We are considering an access front end app with back end tables on sql
server in our office. Is there a way to have a copy this app on a laptop
for a tele-worker and have it synchronised from time to time using either a
3G data connection, or the office LAN when the tele-worker is in the office?
I presume we will have to make copies of both access front end and sql
server backend on the laptop and then the laptop sql server will synchronise
with the office sql server. Is there a better way to handle this?
Thanks
Regards
have a look at DB Ghost - http://www.dbghost.com - I use it to synchronize my
laptop with the production database when I'm online so I have a database at
all times to run reports on.
"John" wrote:

> Hi
> We are considering an access front end app with back end tables on sql
> server in our office. Is there a way to have a copy this app on a laptop
> for a tele-worker and have it synchronised from time to time using either a
> 3G data connection, or the office LAN when the tele-worker is in the office?
> I presume we will have to make copies of both access front end and sql
> server backend on the laptop and then the laptop sql server will synchronise
> with the office sql server. Is there a better way to handle this?
> Thanks
> Regards
>
>
|||For occasional testing... I simply backup/restore or attach/detach... Mostly
I use backup/restore because the production database does not have to come
down ( and the backups are already made).
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"John" <John@.nospam.infovis.co.uk> wrote in message
news:eZjXQQABFHA.4004@.tk2msftngp13.phx.gbl...
> Hi
> We are considering an access front end app with back end tables on sql
> server in our office. Is there a way to have a copy this app on a laptop
> for a tele-worker and have it synchronised from time to time using either
a
> 3G data connection, or the office LAN when the tele-worker is in the
office?
> I presume we will have to make copies of both access front end and sql
> server backend on the laptop and then the laptop sql server will
synchronise
> with the office sql server. Is there a better way to handle this?
> Thanks
> Regards
>
|||I was under the impression that sql server supports synchronisation...or is
replication something different?
Thanks
Regards
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:uzGwBYHBFHA.3140@.TK2MSFTNGP15.phx.gbl...
> For occasional testing... I simply backup/restore or attach/detach...
Mostly[vbcol=seagreen]
> I use backup/restore because the production database does not have to come
> down ( and the backups are already made).
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "John" <John@.nospam.infovis.co.uk> wrote in message
> news:eZjXQQABFHA.4004@.tk2msftngp13.phx.gbl...
laptop[vbcol=seagreen]
either
> a
> office?
> synchronise
>

Remote synchronization

Hi
We are considering an access front end app with back end tables on sql
server in our office. Is there a way to have a copy this app on a laptop
for a tele-worker and have it synchronised from time to time using either a
3G data connection, or the office LAN when the tele-worker is in the office?
I presume we will have to make copies of both access front end and sql
server backend on the laptop and then the laptop sql server will synchronise
with the office sql server. Is there a better way to handle this?
Thanks
Regardshave a look at DB Ghost - http://www.dbghost.com - I use it to synchronize m
y
laptop with the production database when I'm online so I have a database at
all times to run reports on.
"John" wrote:

> Hi
> We are considering an access front end app with back end tables on sql
> server in our office. Is there a way to have a copy this app on a laptop
> for a tele-worker and have it synchronised from time to time using either
a
> 3G data connection, or the office LAN when the tele-worker is in the offic
e?
> I presume we will have to make copies of both access front end and sql
> server backend on the laptop and then the laptop sql server will synchroni
se
> with the office sql server. Is there a better way to handle this?
> Thanks
> Regards
>
>|||For occasional testing... I simply backup/restore or attach/detach... Mostly
I use backup/restore because the production database does not have to come
down ( and the backups are already made).
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"John" <John@.nospam.infovis.co.uk> wrote in message
news:eZjXQQABFHA.4004@.tk2msftngp13.phx.gbl...
> Hi
> We are considering an access front end app with back end tables on sql
> server in our office. Is there a way to have a copy this app on a laptop
> for a tele-worker and have it synchronised from time to time using either
a
> 3G data connection, or the office LAN when the tele-worker is in the
office?
> I presume we will have to make copies of both access front end and sql
> server backend on the laptop and then the laptop sql server will
synchronise
> with the office sql server. Is there a better way to handle this?
> Thanks
> Regards
>|||I was under the impression that sql server supports synchronisation...or is
replication something different?
Thanks
Regards
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:uzGwBYHBFHA.3140@.TK2MSFTNGP15.phx.gbl...
> For occasional testing... I simply backup/restore or attach/detach...
Mostly
> I use backup/restore because the production database does not have to come
> down ( and the backups are already made).
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "John" <John@.nospam.infovis.co.uk> wrote in message
> news:eZjXQQABFHA.4004@.tk2msftngp13.phx.gbl...
laptop[vbcol=seagreen]
either[vbcol=seagreen]
> a
> office?
> synchronise
>

Remote synchronization

Hi
We are considering an access front end app with back end tables on sql
server in our office. Is there a way to have a copy this app on a laptop
for a tele-worker and have it synchronised from time to time using either a
3G data connection, or the office LAN when the tele-worker is in the office?
I presume we will have to make copies of both access front end and sql
server backend on the laptop and then the laptop sql server will synchronise
with the office sql server. Is there a better way to handle this?
Thanks
Regardshave a look at DB Ghost - http://www.dbghost.com - I use it to synchronize my
laptop with the production database when I'm online so I have a database at
all times to run reports on.
"John" wrote:
> Hi
> We are considering an access front end app with back end tables on sql
> server in our office. Is there a way to have a copy this app on a laptop
> for a tele-worker and have it synchronised from time to time using either a
> 3G data connection, or the office LAN when the tele-worker is in the office?
> I presume we will have to make copies of both access front end and sql
> server backend on the laptop and then the laptop sql server will synchronise
> with the office sql server. Is there a better way to handle this?
> Thanks
> Regards
>
>|||For occasional testing... I simply backup/restore or attach/detach... Mostly
I use backup/restore because the production database does not have to come
down ( and the backups are already made).
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"John" <John@.nospam.infovis.co.uk> wrote in message
news:eZjXQQABFHA.4004@.tk2msftngp13.phx.gbl...
> Hi
> We are considering an access front end app with back end tables on sql
> server in our office. Is there a way to have a copy this app on a laptop
> for a tele-worker and have it synchronised from time to time using either
a
> 3G data connection, or the office LAN when the tele-worker is in the
office?
> I presume we will have to make copies of both access front end and sql
> server backend on the laptop and then the laptop sql server will
synchronise
> with the office sql server. Is there a better way to handle this?
> Thanks
> Regards
>|||I was under the impression that sql server supports synchronisation...or is
replication something different?
Thanks
Regards
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:uzGwBYHBFHA.3140@.TK2MSFTNGP15.phx.gbl...
> For occasional testing... I simply backup/restore or attach/detach...
Mostly
> I use backup/restore because the production database does not have to come
> down ( and the backups are already made).
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "John" <John@.nospam.infovis.co.uk> wrote in message
> news:eZjXQQABFHA.4004@.tk2msftngp13.phx.gbl...
> > Hi
> >
> > We are considering an access front end app with back end tables on sql
> > server in our office. Is there a way to have a copy this app on a
laptop
> > for a tele-worker and have it synchronised from time to time using
either
> a
> > 3G data connection, or the office LAN when the tele-worker is in the
> office?
> > I presume we will have to make copies of both access front end and sql
> > server backend on the laptop and then the laptop sql server will
> synchronise
> > with the office sql server. Is there a better way to handle this?
> >
> > Thanks
> >
> > Regards
> >
> >
>

Remote SSIS vs Domain\User: Access is Denied (0x80070005)

What OS permissions do I need to give a domain user to effectively connect to a remote instance of Integration Services?

I keep getting the following message:

Cannot connect to SQLDEV01
Failed to retreive data for this request.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (Microsoft.SqlServer.ManagedDTS)

I have already performed the Windows 2003 steps outlined in the "Eliminating the Access is Denied" error located at http://msdn2.microsoft.com/en-us/library/aa337083.aspx

I have no problem if the user is a local Administrator (go figure).

The MSDN page lacks another steps needed on W2K3 (not sure about XP) - add the account to Distributed COM Users group. (The page is being updated).|||

Yes, I have done this, and gave the Domain\User the DCOM permissions upon the MsDtsSvr object. The Distributed COM Users step is actually included on ths webpage.

Thanks for responding. Perhaps there is another step missing?

|||

JFoushee wrote:

The Distributed COM Users step is actually included on ths webpage.

Not really (if we get the same copy of http://msdn2.microsoft.com/en-us/library/aa337083.aspx).

The page talks about configuring security for MsDtsServer application, but on Windows 2003 Server and 64-bit XP machine there is another global per-machine setting: in DCOMCNFG right click My Computer, select Properties, find COM Security page and inspect both Edit Limits settings: they should allow the user to access the machine. The simplest way to do it is to add user to Distributed COM Users user group.

|||

I believe I got it to work...

One the webpage http://msdn2.microsoft.com/en-us/library/aa337083.aspx, under "To configure rights for remote users on Windows Server 2003"...

replace step 9 with "Click OK to close the dialog box."

Add a step 9.1 with the following text: "On the same Security tab, under Access Permissions, select Customize, then click Edit to open the Access Permission dialog box."

Add a step 9.2 with the following text: "In the Access Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Access, and Remote Access. The easiest is to add the local DCOM Distributed Users group. "

Add a step 9.3 with the following text: "Click OK to close the dialog box. Close the MMC snap-in."

Step 10 stays as-is: "Restart the Integration Services service."

|||

Thanks a lot.

Finally I can connect to SSIS.

Remote SSIS vs Domain\User: Access is Denied (0x80070005)

What OS permissions do I need to give a domain user to effectively connect to a remote instance of Integration Services?

I keep getting the following message:

Cannot connect to SQLDEV01
Failed to retreive data for this request.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (Microsoft.SqlServer.ManagedDTS)

I have already performed the Windows 2003 steps outlined in the "Eliminating the Access is Denied" error located at http://msdn2.microsoft.com/en-us/library/aa337083.aspx

I have no problem if the user is a local Administrator (go figure).

The MSDN page lacks another steps needed on W2K3 (not sure about XP) - add the account to Distributed COM Users group. (The page is being updated).|||

Yes, I have done this, and gave the Domain\User the DCOM permissions upon the MsDtsSvr object. The Distributed COM Users step is actually included on ths webpage.

Thanks for responding. Perhaps there is another step missing?

|||

JFoushee wrote:

The Distributed COM Users step is actually included on ths webpage.

Not really (if we get the same copy of http://msdn2.microsoft.com/en-us/library/aa337083.aspx).

The page talks about configuring security for MsDtsServer application, but on Windows 2003 Server and 64-bit XP machine there is another global per-machine setting: in DCOMCNFG right click My Computer, select Properties, find COM Security page and inspect both Edit Limits settings: they should allow the user to access the machine. The simplest way to do it is to add user to Distributed COM Users user group.

|||

I believe I got it to work...

One the webpage http://msdn2.microsoft.com/en-us/library/aa337083.aspx, under "To configure rights for remote users on Windows Server 2003"...

replace step 9 with "Click OK to close the dialog box."

Add a step 9.1 with the following text: "On the same Security tab, under Access Permissions, select Customize, then click Edit to open the Access Permission dialog box."

Add a step 9.2 with the following text: "In the Access Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Access, and Remote Access. The easiest is to add the local DCOM Distributed Users group. "

Add a step 9.3 with the following text: "Click OK to close the dialog box. Close the MMC snap-in."

Step 10 stays as-is: "Restart the Integration Services service."

|||

Thanks alot.

Finally I can connect to SSIS.

Remote SSIS vs Domain\User: Access is Denied (0x80070005)

What OS permissions do I need to give a domain user to effectively connect to a remote instance of Integration Services?

I keep getting the following message:

Cannot connect to SQLDEV01
Failed to retreive data for this request.
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (Microsoft.SqlServer.ManagedDTS)

I have already performed the Windows 2003 steps outlined in the "Eliminating the Access is Denied" error located at http://msdn2.microsoft.com/en-us/library/aa337083.aspx

I have no problem if the user is a local Administrator (go figure).

The MSDN page lacks another steps needed on W2K3 (not sure about XP) - add the account to Distributed COM Users group. (The page is being updated).|||

Yes, I have done this, and gave the Domain\User the DCOM permissions upon the MsDtsSvr object. The Distributed COM Users step is actually included on ths webpage.

Thanks for responding. Perhaps there is another step missing?

|||

JFoushee wrote:

The Distributed COM Users step is actually included on ths webpage.

Not really (if we get the same copy of http://msdn2.microsoft.com/en-us/library/aa337083.aspx).

The page talks about configuring security for MsDtsServer application, but on Windows 2003 Server and 64-bit XP machine there is another global per-machine setting: in DCOMCNFG right click My Computer, select Properties, find COM Security page and inspect both Edit Limits settings: they should allow the user to access the machine. The simplest way to do it is to add user to Distributed COM Users user group.

|||

I believe I got it to work...

One the webpage http://msdn2.microsoft.com/en-us/library/aa337083.aspx, under "To configure rights for remote users on Windows Server 2003"...

replace step 9 with "Click OK to close the dialog box."

Add a step 9.1 with the following text: "On the same Security tab, under Access Permissions, select Customize, then click Edit to open the Access Permission dialog box."

Add a step 9.2 with the following text: "In the Access Permission dialog box, add or delete users, and assign the appropriate permissions to the appropriate users and groups. The available permissions are Local Access, and Remote Access. The easiest is to add the local DCOM Distributed Users group. "

Add a step 9.3 with the following text: "Click OK to close the dialog box. Close the MMC snap-in."

Step 10 stays as-is: "Restart the Integration Services service."

|||

Thanks a lot.

Finally I can connect to SSIS.

sql

Remote SSIS Access

Hello,
We have discovered that unless a user is an administrator on the MS SQL 2005
server, they cannot connect to SSIS server locally or remotely.
The SQL Junkies site has the solution. They recommend that you first add the
user to the Distributed COM Users group. Then you should run
%windir%\system32\Com\comexp.msc to launch Component Services to launch
component server. On the properties of MsDtsServer you can choose security
and from there you can set the Remote Activation permissions to allow the
user to connect the SSIS server remotely. The SSIS service should then be
restarted.
I tried it and it works. However, what are the security implications with
this solution?The implications are basically just what you set - you allow
that user to connect remotely to the process for
MsDtsServer. Not much outside of that really - you're only
changing this for SSIS and that particular user.
-Sue
On Thu, 8 Jun 2006 14:04:04 -0600, "Loren Zubis"
<Loren.Zubis@.gov.ab.ca> wrote:

>Hello,
>We have discovered that unless a user is an administrator on the MS SQL 200
5
>server, they cannot connect to SSIS server locally or remotely.
>The SQL Junkies site has the solution. They recommend that you first add th
e
>user to the Distributed COM Users group. Then you should run
>%windir%\system32\Com\comexp.msc to launch Component Services to launch
>component server. On the properties of MsDtsServer you can choose security
>and from there you can set the Remote Activation permissions to allow the
>user to connect the SSIS server remotely. The SSIS service should then be
>restarted.
>I tried it and it works. However, what are the security implications with
>this solution?
>|||The implications are basically just what you set - you allow
that user to connect remotely to the process for
MsDtsServer. Not much outside of that really - you're only
changing this for SSIS and that particular user.
-Sue
On Thu, 8 Jun 2006 14:04:04 -0600, "Loren Zubis"
<Loren.Zubis@.gov.ab.ca> wrote:

>Hello,
>We have discovered that unless a user is an administrator on the MS SQL 200
5
>server, they cannot connect to SSIS server locally or remotely.
>The SQL Junkies site has the solution. They recommend that you first add th
e
>user to the Distributed COM Users group. Then you should run
>%windir%\system32\Com\comexp.msc to launch Component Services to launch
>component server. On the properties of MsDtsServer you can choose security
>and from there you can set the Remote Activation permissions to allow the
>user to connect the SSIS server remotely. The SSIS service should then be
>restarted.
>I tried it and it works. However, what are the security implications with
>this solution?
>

Remote SQL with proxy on server

Hello
I'm connecting to DB SQL server from my Access XP using
DSN User, but on my network I have a proxy, so it's block
my connection and I'm enable de connect,
How can I depass a proxy to connect from Access to a
remote DB SQL
ThanksDoes this article help
http://support.microsoft.com/default.aspx?scid=kb;en-us;216415
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.orgsql

Remote SQL server fast access

Hi gurus,
I have sql server 2000 located in Europe which I am
accessing from Mumbai, through wan n/w but due to long
distance it's performance is very poor which tends the
user to wait for execution to complete ..I just come to
know that SQL client software (may be from Microsoft or
third party) will solve my problem. Please guide me in
this regard & let me know the software products available
for the same purpose, may be other than SQL client.So, I
can buy it.
Best Regards,
MANISH JADHAVTry using Remote Desktop or Terminal Server session instead.
This way only the keystrokes go across.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Remote SQL Server Access

I'm using SQL Server to store session state. The Sql Server is on the local network but not on the web server. I use impersonation and use account credentials for the ASPNET worker process:

<identity impersonate="true" userName="domain\user" password="pass"/
I'm able to access all resources and execute all pages without any problem.

When an object is added to session state I recieve the following error:

"Cannot open database requested in login 'ASPState'. Login fails. Login failed for user 'domain\username. "

Here is my web.config entry for using sql server (with modified connection string of course):

<sessionState mode="SQLServer" cookieless="false" timeout="30" stateConnectionString="Data Source=xxx.xxx.x.xx,1433;Network Library=DBMSSOCN;Initial Catalog=ASPState;Integrated Security=SSPI" /
I've checked and given the user i'm impersonating the ability to do everything. I've granted access on all necessary files, added them to the DB and made the user a db_owner of the ASPState table. I can log in to a machine as the user, then access sql server using the windows authentication. I granted 'act as part of the operating system', 'access this computer from a network', 'log on as a service', 'log on as a batch job' on both the remote computer hosting sql server and the web server.

The strange thing is i installed the asp session state tables on my development machine, using the same configuration file to run everything, and was able to add an object to session state without any problem. But when i specify the remote server, i'm denied.

Anybody have an idea?Have you tried switched back from integrated and supplying the said user details in the connection string? Not suggesting that as a solution but just wondering if that works.

Remote SQL server access

I'm writing a piece of software that is designed to access data from SQL server. The office's server has SQL server version 7 installed. The software works perfectly when running on a computer on the network in the office. I however am trying to work out how to use use the software from my home computer and connect to the SQL server database remotely. I've never done this before and I'm finding it hard to find the right information.

Firstly, is it easy to do this? What do I need to do with the server in the office to allow this to work? Do I need any extra hardware/software? How will my software connect to SQL server? Is it as simple as changing the connection string to something like the server's ip address and sql server name?

I'm writing the software in Visual Studio 2005 professional and programming in VB.

Many thanks.


Well, that depends.

"Firstly, is it easy to do this? "

Yes, this is not that hard. If you going through VPN or direct call connections using a dialin you don′t have to worry. Using the internet as the transport layer, you will have to consider your security archtitecture of your office as if you need to have access to your office you probably will need to open certain ports on the firewall which might protect your company from intruders.


"What do I need to do with the server in the office to allow this to work?"

Well assuming for the next questions that you will use a internet connection to connect to your office, you will need to have a (stateful) firewall configured in your office, which exposes the SQL Server Service to the outsides in some way. For security reasons you should consider locking you access to the office using certain security rules like IPSEC / Certificate bases transports etc.

"Do I need any extra hardware/software? "

That depends. using a firewall and the appropiate security mechanims, you won′t need additional stuff. Having a firewall which is able to do VPN, you will need to have a software which is able to establish a VPN tunnel. For the pure access to SQL Server you won′t need any additional software.


"How will my software connect to SQL server? Is it as simple as changing the connection string to something like the server's ip address and sql server name?"

Yes, thats right, after having a connection to your company network (either through the internet as described below or dial-ins) you can connect to your server easily by changing the servername within the connectionstring to the public name or the IPAdress (and eventually in addition the configured port)


Jens K. Suessmeyer


http://www.sqlserver2005.de|||

Thank you very much for your assistance. I will try this out in the office in the next couple of days. I'll post another message if I still have questions but hopefully it'll be fine.

Many thanks again,

Sam