reset report parameters back to defaults

I am running SQL 2005 Reporting Services and designing reports via Visual
Studio.
Is there an easy way to reset/clear the report parameters back to the
defaults while viewing the report in IE.
Right now I have create a hyperlink which will re-direct to the URL of the
report which thus sets the paramaters back to their defaults, but it seems
that there must be a better way to do this.Hello,
Reporting Services did not provide the method to reset the parameters back
to the default.
Your solution is the best way I think to achieve your requirement.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.sql

Requirement to use Management Studio

What are the requirements to use Management Studio/Management Studio Express for local instances? Are the requirements same for both studios and same for all OS?

Based on my own testings:
Remote connection is required for Management Studio in Windows XP SP2.
But it is not required in Management Studio Express in Windows XP SP2.

For Windows 2003 and 2000, remote connection is not required for Management Studio. Have not tried Management Studio Express yet.

Peter

This is additional info to clarify the issues:

I'm testing the following in a Windows XP SP2 with SQL Server 2005 Developer Edition SP1:

Scenario #1
1. Checked Local connections only in SSSAC for a SQL Server 2005 local instance
2. Restarted that instance in SSCM (Note: only Shared Memory enabled for Network Configuration)
3. Tried to connect to that instance in SSMS and get this error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (Microsoft SQL Server, Error: -1)

Scenario #2
1. Checked Local and remote connections and Using named pipes only in SSSAC for a SQL Server 2005 local instance
2. Restarted that instance in SSCM (Note: Shared Memory and Named Pipes enabled for Network Configuration)
3. Tried to connect to that instance in SSMS and get this error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (.Net SqlClient Data Provider)

Scenario #3
1. Checked Local and remote connections and Using TCP/IP only in SSSAC for a SQL Server 2005 local instance
2. Restarted that instance in SSCM (Note: Shared Memory and TCP/IP enabled for Network Configuration)
3. Tried to connect to that instance in SSMS and was able to connect
4. The following is fromt the SQL Server Logs:

Server is listening on [ 127.0.0.1 <ipv4> 4906].
Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL2005\sql\query ].
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL2005].
Server is listening on [ 'any' <ipv4> 2464].

What do the log mean?

Why I cannot connect to the local instance in Scenario #1 and #2?

Thanks for any help,

Peter

|||

SQL Server supports connections using shared memory (which can only work with applications on the same machine), named pipes (an inter-machine communication technology that is mostly used by older applications running on Windows machines - it lets the client communicate with SQL Server as if it were reading or writing to a file), or TCP/IP connections, which can work for any network client on any machine (including, say, Java clients on Unix machines).

In scenario #1 you've disabled remote connections, so only applications running on your server machine can access the server. In #1, you are only allowing connections via shared memory, and in #2 you are allowing shared memory or named pipes connections. It seems likely that in #1 and #2 SSMS is trying to create a TCP/IP connection to your server, but your server isn't accepting those connection types. You can configure how Management Studio connects to your server in the Connection Dialog by clicking the "Options >>" button. In the "Network protocol" dropdown, just pick one of the connection types your server is allowing. In #1, that would be "Shared Memory."

In scenario #3, the log is saying that SQL Server is accepting

TCP/IP connections from the TCP local loopback adapter (the reserved IP address 127.0.0.1, used by network applications to talk to the local machine) on port 4906. If you type "(local)" or "." as the name of the server, SSMS uses 127.0.0.1 as the address of the server.|||

Hi Steve,

Thanks for your post.

I'm not sure what do you mean by "in #2 you are allowing shared memory or named pipes from local clients". If I understand correctly, the #2 scenario is allowing shared memory from local clients and named pipes from remote clients.

If I don't click the Options button in the Connection Dialog, which protocol will be used by default or how can I find out? If I click the Options button in the Connection Dialog and then select <default>, is it same as not clicking the Options button?

Is there any webcast from technet/msdn/microsoft regarding Connection in SQL Server 2005 and/or SQL Server Browser Service?

Peter

|||

You're right, #2 allows remote connections via named pipes. I wasn't reading your description correctly.

<default> means that the connection dialog doesn't specify a network protocol in the connection string used to connect to the server. Under ADO.net 2.0, I believe this results in a TCP/IP connection. If ADO.net changes this default in a future release, <default> would use it. The Options button just exposes additional connection options and doesn't change anything itself, so clicking <default> shouldn't have an effect if that was the setting initially.

I don't know the answer to your question about upcoming webcasts.

Hope this helps,
Steve

Required help on sql 2005 Server Management Studio.

Have installed sql 2005 successfully on windows2003 server. But when I
opened
server management studio I found duplicate entries in menu toolbar.
Tried to delete the
duplicate entries from tools > customise > commands > rearrange
commands but in vain.
After restarting the application again it is showing duplicate option
in menu toolbar.
Suggest what needs to be done to fix this permanantely
Regds,
Kiran.Hi Kiran, what happens when you completely un-install and re-install SQL
Server 2005 workstation components? Do you still see duplicate entries?
Thank you,
Saleem Hakani
WWW.SQLCOMMUNITY.COM (World Wide Microsoft SQL server Community)
SQLTips, SQL Articles, SQL Forums, SQL Automation Tools/Scripts, SQL Blogs
and much more..
"Mendon" wrote:
> Have installed sql 2005 successfully on windows2003 server. But when I
> opened
> server management studio I found duplicate entries in menu toolbar.
> Tried to delete the
> duplicate entries from tools > customise > commands > rearrange
> commands but in vain.
> After restarting the application again it is showing duplicate option
> in menu toolbar.
> Suggest what needs to be done to fix this permanantely
> Regds,
> Kiran.
>

Request Length Exceeded

I'm re-posting under an updated subscriber ID so Microsoft techs will answer...
I am working in Visual Studio 2005. I have a Report Model project with a
data source, a data source view which contains all of the tables in my
database (SQL Server 2005), and a Report Model that contains the items that I
want the users to be able to work with.
When I deploy the project, I get the following error:
Error 2 System.Web.Services.Protocols.SoapException: There was an exception
running the extensions specified in the config file. -->
System.Web.HttpException: Maximum request length exceeded. at
System.Web.HttpRequest.GetEntireRawContent() at
System.Web.HttpRequest.get_InputStream() at
System.Web.Services.Protocols.SoapServerProtocol.Initialize() -- End of
inner exception stack trace -- at
System.Web.Services.Protocols.SoapServerProtocol.Initialize() at
System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type,
HttpContext context, HttpRequest request, HttpResponse response, Boolean&
abortProcessing) c:\crimson\wmsdev\vbapps2005\desktopweb\wmsreportmodels\CrimsonWMS.smdl 0 0
How do I fix it?
Thank you,
Mark LauserI second that. Ran into the same problem today.
Don Olsen
"Mark Lauser" wrote:
> I'm re-posting under an updated subscriber ID so Microsoft techs will answer...
>
> I am working in Visual Studio 2005. I have a Report Model project with a
> data source, a data source view which contains all of the tables in my
> database (SQL Server 2005), and a Report Model that contains the items that I
> want the users to be able to work with.
> When I deploy the project, I get the following error:
> Error 2 System.Web.Services.Protocols.SoapException: There was an exception
> running the extensions specified in the config file. -->
> System.Web.HttpException: Maximum request length exceeded. at
> System.Web.HttpRequest.GetEntireRawContent() at
> System.Web.HttpRequest.get_InputStream() at
> System.Web.Services.Protocols.SoapServerProtocol.Initialize() -- End of
> inner exception stack trace -- at
> System.Web.Services.Protocols.SoapServerProtocol.Initialize() at
> System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type,
> HttpContext context, HttpRequest request, HttpResponse response, Boolean&
> abortProcessing) c:\crimson\wmsdev\vbapps2005\desktopweb\wmsreportmodels\CrimsonWMS.smdl 0 0
> How do I fix it?
> Thank you,
> Mark Lauser
>|||After re-reading this error and looking at the smdl file I suspected that the
problem was the XML being sent to the SOAP service was too long. Started
deleting some unused tables and viola it worked after deleting about 6
tables. Your milage may vary.
Hope that helps.
-Don
"Mark Lauser" wrote:
> I'm re-posting under an updated subscriber ID so Microsoft techs will answer...
>
> I am working in Visual Studio 2005. I have a Report Model project with a
> data source, a data source view which contains all of the tables in my
> database (SQL Server 2005), and a Report Model that contains the items that I
> want the users to be able to work with.
> When I deploy the project, I get the following error:
> Error 2 System.Web.Services.Protocols.SoapException: There was an exception
> running the extensions specified in the config file. -->
> System.Web.HttpException: Maximum request length exceeded. at
> System.Web.HttpRequest.GetEntireRawContent() at
> System.Web.HttpRequest.get_InputStream() at
> System.Web.Services.Protocols.SoapServerProtocol.Initialize() -- End of
> inner exception stack trace -- at
> System.Web.Services.Protocols.SoapServerProtocol.Initialize() at
> System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type,
> HttpContext context, HttpRequest request, HttpResponse response, Boolean&
> abortProcessing) c:\crimson\wmsdev\vbapps2005\desktopweb\wmsreportmodels\CrimsonWMS.smdl 0 0
> How do I fix it?
> Thank you,
> Mark Lauser
>|||Thanks for your input Don. I tried deleting all I could stand to, but the
problem persisted. I'm hoping for a different solution that will allow a
larger request length.
Best Regards,
Mark Lauser
"Don Olsen" wrote:
> After re-reading this error and looking at the smdl file I suspected that the
> problem was the XML being sent to the SOAP service was too long. Started
> deleting some unused tables and viola it worked after deleting about 6
> tables. Your milage may vary.
> Hope that helps.
> -Don
> "Mark Lauser" wrote:
> > I'm re-posting under an updated subscriber ID so Microsoft techs will answer...
> >
> >
> > I am working in Visual Studio 2005. I have a Report Model project with a
> > data source, a data source view which contains all of the tables in my
> > database (SQL Server 2005), and a Report Model that contains the items that I
> > want the users to be able to work with.
> >
> > When I deploy the project, I get the following error:
> >
> > Error 2 System.Web.Services.Protocols.SoapException: There was an exception
> > running the extensions specified in the config file. -->
> > System.Web.HttpException: Maximum request length exceeded. at
> > System.Web.HttpRequest.GetEntireRawContent() at
> > System.Web.HttpRequest.get_InputStream() at
> > System.Web.Services.Protocols.SoapServerProtocol.Initialize() -- End of
> > inner exception stack trace -- at
> > System.Web.Services.Protocols.SoapServerProtocol.Initialize() at
> > System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type,
> > HttpContext context, HttpRequest request, HttpResponse response, Boolean&
> > abortProcessing) c:\crimson\wmsdev\vbapps2005\desktopweb\wmsreportmodels\CrimsonWMS.smdl 0 0
> >
> > How do I fix it?
> >
> > Thank you,
> > Mark Lauser
> >|||Hey, Mark
I think I just replied to your original post, so see if you can dig back a
couple of posts and read the answer...but it has to do with the <httpRuntime
maxRequestLength="" /> element in the web.config file of the ReportServer and
Report Manager apps.
--
Regards,
Thiago Silva
"Mark Lauser" wrote:
> Thanks for your input Don. I tried deleting all I could stand to, but the
> problem persisted. I'm hoping for a different solution that will allow a
> larger request length.
> Best Regards,
> Mark Lauser
>
> "Don Olsen" wrote:
> > After re-reading this error and looking at the smdl file I suspected that the
> > problem was the XML being sent to the SOAP service was too long. Started
> > deleting some unused tables and viola it worked after deleting about 6
> > tables. Your milage may vary.
> >
> > Hope that helps.
> >
> > -Don
> >
> > "Mark Lauser" wrote:
> >
> > > I'm re-posting under an updated subscriber ID so Microsoft techs will answer...
> > >
> > >
> > > I am working in Visual Studio 2005. I have a Report Model project with a
> > > data source, a data source view which contains all of the tables in my
> > > database (SQL Server 2005), and a Report Model that contains the items that I
> > > want the users to be able to work with.
> > >
> > > When I deploy the project, I get the following error:
> > >
> > > Error 2 System.Web.Services.Protocols.SoapException: There was an exception
> > > running the extensions specified in the config file. -->
> > > System.Web.HttpException: Maximum request length exceeded. at
> > > System.Web.HttpRequest.GetEntireRawContent() at
> > > System.Web.HttpRequest.get_InputStream() at
> > > System.Web.Services.Protocols.SoapServerProtocol.Initialize() -- End of
> > > inner exception stack trace -- at
> > > System.Web.Services.Protocols.SoapServerProtocol.Initialize() at
> > > System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type,
> > > HttpContext context, HttpRequest request, HttpResponse response, Boolean&
> > > abortProcessing) c:\crimson\wmsdev\vbapps2005\desktopweb\wmsreportmodels\CrimsonWMS.smdl 0 0
> > >
> > > How do I fix it?
> > >
> > > Thank you,
> > > Mark Lauser
> > >

Request Length Exceeded

I am working in Visual Studio 2005. I have a Report Model project with a
data source, a data source view which contains all of the tables in my
database (SQL Server 2005), and a Report Model that contains the items that I
want the users to be able to work with.
When I deploy the project, I get the following error:
Error 2 System.Web.Services.Protocols.SoapException: There was an exception
running the extensions specified in the config file. -->
System.Web.HttpException: Maximum request length exceeded. at
System.Web.HttpRequest.GetEntireRawContent() at
System.Web.HttpRequest.get_InputStream() at
System.Web.Services.Protocols.SoapServerProtocol.Initialize() -- End of
inner exception stack trace -- at
System.Web.Services.Protocols.SoapServerProtocol.Initialize() at
System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type,
HttpContext context, HttpRequest request, HttpResponse response, Boolean&
abortProcessing) c:\crimson\wmsdev\vbapps2005\desktopweb\wmsreportmodels\CrimsonWMS.smdl 0 0
How do I fix it?
Thank you,
Mark LauserHi, Mark
It sounds like your report model file is kinda large so when you
upload/deploy it to the server, the asp.net http request times out before the
file is fully uploaded (it uses the web service).
You are gonna have to change the value in the maxRequestLength attribute of
the httpRuntime element in the web.config file of your ReportServer and
Report Manager so it doesn't time out. The default size is 4096 KB (4 MB),
but I bet your file is much larger, so change it to something like:
<httpRuntime ... maxRequestLength="151200" .../>
Hope this helps you!
--
Regards,
Thiago Silva
"Mark Lauser" wrote:
> I am working in Visual Studio 2005. I have a Report Model project with a
> data source, a data source view which contains all of the tables in my
> database (SQL Server 2005), and a Report Model that contains the items that I
> want the users to be able to work with.
> When I deploy the project, I get the following error:
> Error 2 System.Web.Services.Protocols.SoapException: There was an exception
> running the extensions specified in the config file. -->
> System.Web.HttpException: Maximum request length exceeded. at
> System.Web.HttpRequest.GetEntireRawContent() at
> System.Web.HttpRequest.get_InputStream() at
> System.Web.Services.Protocols.SoapServerProtocol.Initialize() -- End of
> inner exception stack trace -- at
> System.Web.Services.Protocols.SoapServerProtocol.Initialize() at
> System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type,
> HttpContext context, HttpRequest request, HttpResponse response, Boolean&
> abortProcessing) c:\crimson\wmsdev\vbapps2005\desktopweb\wmsreportmodels\CrimsonWMS.smdl 0 0
> How do I fix it?
> Thank you,
> Mark Lauser|||Thanks, that worked. My problem was that my web.config file didn't have a
maxRequestLength attribute for the httpRuntime element, so my 'Find' didn't
find anything. Now that I know where it is supposed to be, I added the
attribute and it worked fine.
There must be a default that is used when the attribute is not present.
Thanks again!
Mark Lauser
"HC" wrote:
> Hi, Mark
> It sounds like your report model file is kinda large so when you
> upload/deploy it to the server, the asp.net http request times out before the
> file is fully uploaded (it uses the web service).
> You are gonna have to change the value in the maxRequestLength attribute of
> the httpRuntime element in the web.config file of your ReportServer and
> Report Manager so it doesn't time out. The default size is 4096 KB (4 MB),
> but I bet your file is much larger, so change it to something like:
> <httpRuntime ... maxRequestLength="151200" .../>
> Hope this helps you!
> --
> Regards,
> Thiago Silva
> "Mark Lauser" wrote:
> > I am working in Visual Studio 2005. I have a Report Model project with a
> > data source, a data source view which contains all of the tables in my
> > database (SQL Server 2005), and a Report Model that contains the items that I
> > want the users to be able to work with.
> >
> > When I deploy the project, I get the following error:
> >
> > Error 2 System.Web.Services.Protocols.SoapException: There was an exception
> > running the extensions specified in the config file. -->
> > System.Web.HttpException: Maximum request length exceeded. at
> > System.Web.HttpRequest.GetEntireRawContent() at
> > System.Web.HttpRequest.get_InputStream() at
> > System.Web.Services.Protocols.SoapServerProtocol.Initialize() -- End of
> > inner exception stack trace -- at
> > System.Web.Services.Protocols.SoapServerProtocol.Initialize() at
> > System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type,
> > HttpContext context, HttpRequest request, HttpResponse response, Boolean&
> > abortProcessing) c:\crimson\wmsdev\vbapps2005\desktopweb\wmsreportmodels\CrimsonWMS.smdl 0 0
> >
> > How do I fix it?
> >
> > Thank you,
> > Mark Lauser|||Yeah, the default is in the machine.config file
(C:\WINDOWS\Microsoft.NET\Framework\[VERSION_NUMBER]\CONFIG).
The aspnet engine follows a hierarchy of config files. If it doesn't
find a setting in the inner-most config, it will keep searching up the
hierarchy until it finds it.
Most settings are defined with a default in the machine.config file.
So if you don't override a setting in your application folder's
web.config, it will use whatever is defined in the machine.config file.
Regards,
Thiago Silva|||Thanks, that makes sense.
My problem was further complicated by the fact that there was no
maxRequestLength in my machine.config for the version of the .net framework
that I am working in. It must have defaulted all the way up the hierarchy.
I noticed that the notes in the file say to only include a setting if you
want to override the default (for better performance).
Best Regards,
Mark Lauser
"tafs7" wrote:
> Yeah, the default is in the machine.config file
> (C:\WINDOWS\Microsoft.NET\Framework\[VERSION_NUMBER]\CONFIG).
> The aspnet engine follows a hierarchy of config files. If it doesn't
> find a setting in the inner-most config, it will keep searching up the
> hierarchy until it finds it.
> Most settings are defined with a default in the machine.config file.
> So if you don't override a setting in your application folder's
> web.config, it will use whatever is defined in the machine.config file.
> Regards,
> Thiago Silva
>

request a nonadmin resource grant

I granted a db_datareader role for a user (on user db, master and msdb), and he doesn't see the files of the user db int the management studio (properties\files). What have i add him ?

is this a domain account.

if it is. check to see if he is not a

member of any restricted domain group.

Representation of Relationships in 2005

We're currently developing on SQL Server 2005 and I have a question about ho
w
SQL Management Studio represents the relationships when creating a diagram.
First off, when creating the relationship, there's no place to designate
whether the relationship is a 1-1 or a 1-M relationship. Secondly, they all
end up being shown as 1-M, with a key on the 1 side and the infinity symbol
on the M side.
I can't find anything in the documentation about how to designate it as a
1-1 relationship instead of a 1-M.
Any ideas?
Thanks for the help.
DougHi Doug,
This is probably better asked in the SQL Server 2005 newsgroups
(http://communities.microsoft.com/ne...lcid=u
s).
Have you looked at the topic How to: Create Relationships Between Tables
(Visual Database Tools) in SQL Server Books Online? I just glanced at it,
but it looks like it might answer your question.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Doug" <Doug@.discussions.microsoft.com> wrote in message
news:180D9D97-5E55-42B6-A9BF-986B7FD62E4F@.microsoft.com...
> We're currently developing on SQL Server 2005 and I have a question about
> how
> SQL Management Studio represents the relationships when creating a
> diagram.
> First off, when creating the relationship, there's no place to designate
> whether the relationship is a 1-1 or a 1-M relationship. Secondly, they
> all
> end up being shown as 1-M, with a key on the 1 side and the infinity
> symbol
> on the M side.
> I can't find anything in the documentation about how to designate it as a
> 1-1 relationship instead of a 1-M.
> Any ideas?
> Thanks for the help.
> Doug

Representation of Relationships in 2005

We're currently developing on SQL Server 2005 and I have a question about how
SQL Management Studio represents the relationships when creating a diagram.
First off, when creating the relationship, there's no place to designate
whether the relationship is a 1-1 or a 1-M relationship. Secondly, they all
end up being shown as 1-M, with a key on the 1 side and the infinity symbol
on the M side.
I can't find anything in the documentation about how to designate it as a
1-1 relationship instead of a 1-M.
Any ideas?
Thanks for the help.
Doug
Hi Doug,
This is probably better asked in the SQL Server 2005 newsgroups
(http://communities.microsoft.com/new...r2005&slcid=us).
Have you looked at the topic How to: Create Relationships Between Tables
(Visual Database Tools) in SQL Server Books Online? I just glanced at it,
but it looks like it might answer your question.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Doug" <Doug@.discussions.microsoft.com> wrote in message
news:180D9D97-5E55-42B6-A9BF-986B7FD62E4F@.microsoft.com...
> We're currently developing on SQL Server 2005 and I have a question about
> how
> SQL Management Studio represents the relationships when creating a
> diagram.
> First off, when creating the relationship, there's no place to designate
> whether the relationship is a 1-1 or a 1-M relationship. Secondly, they
> all
> end up being shown as 1-M, with a key on the 1 side and the infinity
> symbol
> on the M side.
> I can't find anything in the documentation about how to designate it as a
> 1-1 relationship instead of a 1-M.
> Any ideas?
> Thanks for the help.
> Doug

Representation of Relationships in 2005

We're currently developing on SQL Server 2005 and I have a question about how
SQL Management Studio represents the relationships when creating a diagram.
First off, when creating the relationship, there's no place to designate
whether the relationship is a 1-1 or a 1-M relationship. Secondly, they all
end up being shown as 1-M, with a key on the 1 side and the infinity symbol
on the M side.
I can't find anything in the documentation about how to designate it as a
1-1 relationship instead of a 1-M.
Any ideas?
Thanks for the help.
DougHi Doug,
This is probably better asked in the SQL Server 2005 newsgroups
(http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005&slcid=us).
Have you looked at the topic How to: Create Relationships Between Tables
(Visual Database Tools) in SQL Server Books Online? I just glanced at it,
but it looks like it might answer your question.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
"Doug" <Doug@.discussions.microsoft.com> wrote in message
news:180D9D97-5E55-42B6-A9BF-986B7FD62E4F@.microsoft.com...
> We're currently developing on SQL Server 2005 and I have a question about
> how
> SQL Management Studio represents the relationships when creating a
> diagram.
> First off, when creating the relationship, there's no place to designate
> whether the relationship is a 1-1 or a 1-M relationship. Secondly, they
> all
> end up being shown as 1-M, with a key on the 1 side and the infinity
> symbol
> on the M side.
> I can't find anything in the documentation about how to designate it as a
> 1-1 relationship instead of a 1-M.
> Any ideas?
> Thanks for the help.
> Doug