Link with parameters

Hi,
is it possible to start a Report via Link (from Desktop) with start
parameter like an
ASP-Script
For example:
...report.rdl?Year=2007&Month=6...
Thank you
HansThat's what URL access in RS is for.
Amarnath
"Hans" wrote:
> Hi,
> is it possible to start a Report via Link (from Desktop) with start
> parameter like an
> ASP-Script
> For example:
>
> ...report.rdl?Year=2007&Month=6...
>
> Thank you
> Hans
>|||That what I mean ist to start the report from Desktop inclusive
parameters.
Hans|||ok,
so this is a sample you can use to see how it works if you have implemented
the samples and hosted the reports on localserver. copy this url from
desktop.. also you can write asp.net to mask this url and give just a
hyperlink from the page.. see the parameters also passed.
http://server/reportserver?/Sales/Northwest/Employee Sales
Report&rs:Command=Render&EmployeeID=1234
Amarnath
"Hans" wrote:
> That what I mean ist to start the report from Desktop inclusive
> parameters.
> Hans
>|||I tried this, but it doesn=B4t work. The report opens, but there=B4s not
selected parameter value.
Thanks,
Hans|||Hans,
Have you pasted my sample link as a whole URL because it is wraped in the
post.
Incase you have done this pl ignore, you said there is no parameter value,
so I thought you have not pasted the whole URL.
Amarnath, MCTS
"Hans" wrote:
> I tried this, but it doesn´t work. The report opens, but there´s not
> selected parameter value.
>
> Thanks,
> Hans
>

Limits

Is there a database size limitation with the desktop SQL edition'SQL Server Express is designed to meet the needs of simple applications. It
is limited to using 1 CPU and up to 1GB RAM, with a 4GB maximum database
size.
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Richard Douglass" wrote:
| Is there a database size limitation with the desktop SQL edition'
|
|
||||The size of a database cannot exceed 2 GB when using the SQL Server
2000 Desktop Engine or the Microsoft Data Engine (MSDE) 1.0
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Richard Douglass wrote:
> Is there a database size limitation with the desktop SQL edition'

Limits

Is there a database size limitation with the desktop SQL edition'The size of a database cannot exceed 2 GB when using the SQL Server
2000 Desktop Engine or the Microsoft Data Engine (MSDE) 1.0
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Richard Douglass wrote:
> Is there a database size limitation with the desktop SQL edition'|||SQL Server Express is designed to meet the needs of simple applications. It
is limited to using 1 CPU and up to 1GB RAM, with a 4GB maximum database
size.
--
Regards,
Dave Patrick ...Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"Richard Douglass" wrote:
| Is there a database size limitation with the desktop SQL edition'
|
|
|

Limited Remote Login db access

I have connected my desktop and laptop computer at home, on my desktop I have a series of db's under my default named instance <computername>/sqlexpress and I have created access logins using windows auth. When I connect to the desktop from the laptop using tcp:<computername>\sqlexpress\userid I can only see the system db's...I am trying to view adventure works, which I can see on the desktop fine using the same login...any ideas?

Thanks,

Rob

Do you have a domain controller and home network?

If not, then you must create use SQL logins -you cannot use Windows authentication without an Active Directory (domain controller).

|||

I don't even know what those things mean.

How would I go about doing this with SQL logins?

Rob

|||

I suggest you follow the steps under "To configure AdventureWorks to work with Web server controls" on the following page from the Books Online.

http://msdn2.microsoft.com/en-us/library/ms310325(vs.80).aspx

Hopefully this helps,

John

|||

So I read over the link provided...

I have completed the first part and added it to the server. I can access the database on my desktop machine, when I login from the laptop however (using the same windows login) I can't access to database...do I need to also add something to make it accessible remotely? I don't really understand what "configure AdventureWorks to work with Web server controls
" means..

Rob

|||

These resources might help.

Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx

|||

I have done this...as I stated before I can connect fine its just that I can't see anything other than system db's...I imagine I'm missing something stupid, like perhaps I didn't configure the login correctly?

Rob

|||

The login needs to be provided permission to access the databases.

Add the login to the appropriate database role.

|||

Ok first...I am running XP home on both the desktop and laptop...and the logins are windows auth.

if I want full access from the remote connection, where do I change the role of the login? is it in the login menu or the databases menu?

Rob

|||

Look back at the first response given to your problem.

Windows authentication will not work in your situation -you do not have a domain controller.

You will need to establish SQL Logins in each server, and assign permissions accordingly.

Look in Books Online about creating SQL Logins.

Limited Remote Login access

Hello all,

I'm very new to this so excuse my naiveity...I have connected my desktop and laptop computer at home, on my desktop I have a series of db's under my default named instance <computername>/sqlexpress and I have created access logins using windows auth. When I connect to the desktop from the laptop using tcp:<computername>\sqlexpress\userid I can only see the systemdb's...I am trying to view adventure works, just to see how this remote connection stuff works...any ideas?

Thanks,

Rob

See my response to your post in the 'Data Access' forum.

Limitations of SQL7 desktop DBMS?

what are the limitations of the DBMS?The following are the limitations (from what I can remember - some of these might apply to the personal edition for 2000):

2 CPU
2 Gb RAM
4 Gb per database
No publishing for transaction replication
No Distributed Partitioned Views
No Log Shipping
No Parallel DBCC
No Parallel index creation
No Failover clustering

Limit remote connections

Hi,
We use SQL server 2000 on windows 2003. We usually use remote desktop to
connect to the SQL server. For security reasons, only 2 concurrent remote
desktop connections are allowed. I just noticed I'm able to use 'osql'
command to open as many connections to the SQL server as I want. Should I be
concerned? How other people deal with remote connections?
Thanks in advance,
Bing
Hello, Bing
In my opinion, the limit of 2 concurrent remote desktop connections on
Windows 2003 is for licensing reasons, not for security reasons.
Having an unlimited number of connections to SQL Server is no cause of
concern for security reasons, as long as each connection is properly
authentificated and comes from an authorised user and/or computer.
Razvan
|||On Jun 2, 1:33 pm, Razvan Socol <rso...@.gmail.com> wrote:
> Hello, Bing
> In my opinion, the limit of 2 concurrent remote desktop connections on
> Windows 2003 is for licensing reasons, not for security reasons.
> Having an unlimited number of connections to SQL Server is no cause of
> concern for security reasons, as long as each connection is properly
> authentificated and comes from an authorised user and/or computer.
> Razvan
However, you can limit the number of connections on an instance of SQL
Server, by using the "user connections" option. By default, SQL Server
allows a maximum of 32,767 user connections, but the actual number of
user connections allowed also depends on the limits of your
applications and hardware. Using the "user connections" option, you
can limit the number of connections to any desired number (less than
32,767), but this is done for performance reasons, not for security
reasons.
Razvan

Limit remote connections

Hi,
We use SQL server 2000 on windows 2003. We usually use remote desktop to
connect to the SQL server. For security reasons, only 2 concurrent remote
desktop connections are allowed. I just noticed I'm able to use 'osql'
command to open as many connections to the SQL server as I want. Should I b
e
concerned? How other people deal with remote connections?
Thanks in advance,
BingHello, Bing
In my opinion, the limit of 2 concurrent remote desktop connections on
Windows 2003 is for licensing reasons, not for security reasons.
Having an unlimited number of connections to SQL Server is no cause of
concern for security reasons, as long as each connection is properly
authentificated and comes from an authorised user and/or computer.
Razvan|||On Jun 2, 1:33 pm, Razvan Socol <rso...@.gmail.com> wrote:
> Hello, Bing
> In my opinion, the limit of 2 concurrent remote desktop connections on
> Windows 2003 is for licensing reasons, not for security reasons.
> Having an unlimited number of connections to SQL Server is no cause of
> concern for security reasons, as long as each connection is properly
> authentificated and comes from an authorised user and/or computer.
> Razvan
However, you can limit the number of connections on an instance of SQL
Server, by using the "user connections" option. By default, SQL Server
allows a maximum of 32,767 user connections, but the actual number of
user connections allowed also depends on the limits of your
applications and hardware. Using the "user connections" option, you
can limit the number of connections to any desired number (less than
32,767), but this is done for performance reasons, not for security
reasons.
Razvan

Limit remote connections

Hi,
We use SQL server 2000 on windows 2003. We usually use remote desktop to
connect to the SQL server. For security reasons, only 2 concurrent remote
desktop connections are allowed. I just noticed I'm able to use 'osql'
command to open as many connections to the SQL server as I want. Should I be
concerned? How other people deal with remote connections?
Thanks in advance,
BingHello, Bing
In my opinion, the limit of 2 concurrent remote desktop connections on
Windows 2003 is for licensing reasons, not for security reasons.
Having an unlimited number of connections to SQL Server is no cause of
concern for security reasons, as long as each connection is properly
authentificated and comes from an authorised user and/or computer.
Razvan|||On Jun 2, 1:33 pm, Razvan Socol <rso...@.gmail.com> wrote:
> Hello, Bing
> In my opinion, the limit of 2 concurrent remote desktop connections on
> Windows 2003 is for licensing reasons, not for security reasons.
> Having an unlimited number of connections to SQL Server is no cause of
> concern for security reasons, as long as each connection is properly
> authentificated and comes from an authorised user and/or computer.
> Razvan
However, you can limit the number of connections on an instance of SQL
Server, by using the "user connections" option. By default, SQL Server
allows a maximum of 32,767 user connections, but the actual number of
user connections allowed also depends on the limits of your
applications and hardware. Using the "user connections" option, you
can limit the number of connections to any desired number (less than
32,767), but this is done for performance reasons, not for security
reasons.
Razvan