difference between table relations and foreign keys?

I've bought a book about ASP.NET with SQL Server 2000.
In one chapter, they talk about setting relations between tables, and in
another, about setting foreign keys.
But I can't understand the difference, as the purpose seems to be the same:
navigating from a parent table to a child one, and vice-versa.
Am I missing something?
Thanks!
HenriUnless you can show more detailed context, I think they are talking about
the exact same thing. A relationship is a bit more abstract; a foreign key
represents the implementation-specific way that a child row is connected to
a parent row.
http://www.aspfaq.com/
(Reverse address to reply.)
"Henri" <hmfireball@.hotmail.com> wrote in message
news:%23nSPik0TEHA.3828@.TK2MSFTNGP09.phx.gbl...
> I've bought a book about ASP.NET with SQL Server 2000.
> In one chapter, they talk about setting relations between tables, and in
> another, about setting foreign keys.
> But I can't understand the difference, as the purpose seems to be the
> same:
> navigating from a parent table to a child one, and vice-versa.
> Am I missing something?
> Thanks!
> Henri
>
>|||Actually, the first chapter is about the DataRelation class, and
DataTable.ChildRelations(String) and DataRow.GetChildRows(DataRelation).
The second chapter is about ForeignKeyConstraint Class
The only difference I see is that a foreign key allows to define cascade
update and delete rules.
Actually, ASP.NET permits to define many things like indexes, primary keys,
relations, etc. but I thought that this had to be done on SQL Server, not
from ASP.NET.
That's why I'm a bit lost :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> a crit dans le messag
e de
news:ORWb%23o0TEHA.2416@.TK2MSFTNGP12.phx.gbl...
> Unless you can show more detailed context, I think they are talking about
> the exact same thing. A relationship is a bit more abstract; a foreign
key
> represents the implementation-specific way that a child row is connected
to
> a parent row.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Henri" <hmfireball@.hotmail.com> wrote in message
> news:%23nSPik0TEHA.3828@.TK2MSFTNGP09.phx.gbl...
>
>|||What you are reading about is Data Sets in ADO.Net. The
relations and constraints you define in a data set are
different and separate from relations and constraints in the
database. In ADO.Net, you can create something similar to a
database - tables (data tables), relationships (using the
DataRelation class), constraints (such as with the
ForeignKeyConstraint class). It's not the same thing as the
database you may be accessing for the data in the data sets.
For ADO.Net, you can find more information on how relations
and constraints work together, differently in .Net Framework
documentation. Check the remarks section of the definition
of the DataRelation class.
-Sue
On Fri, 11 Jun 2004 03:40:00 +0200, "Henri"
<hmfireball@.hotmail.com> wrote:

>Actually, the first chapter is about the DataRelation class, and
>DataTable.ChildRelations(String) and DataRow.GetChildRows(DataRelation).
>The second chapter is about ForeignKeyConstraint Class
>The only difference I see is that a foreign key allows to define cascade
>update and delete rules.
>Actually, ASP.NET permits to define many things like indexes, primary keys,
>relations, etc. but I thought that this had to be done on SQL Server, not
>from ASP.NET.
>That's why I'm a bit lost :-)
>
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> a crit dans le messa
ge de
>news:ORWb%23o0TEHA.2416@.TK2MSFTNGP12.phx.gbl...
>key
>to
>|||Hi,
Within ADO.Net, a Foreign Key Constaint is a subtype of the Data Relation. T
he FKC in ADO.Net behaves in a similar manner to a FKC within SQL Server, bu
t it is a constraint on the Data Set, not the database, which can be an impo
rtant consideration.
A Data Relation has additonal functionality that is not provided by the FKC,
( I think one is providing the Child Rows in the Data Set to a particular M
aster row.) I suggest you have a look at the class definitions and examine t
he different methods and pr
operties each suppiles

difference between table relations and foreign keys?

I've bought a book about ASP.NET with SQL Server 2000.
In one chapter, they talk about setting relations between tables, and in
another, about setting foreign keys.
But I can't understand the difference, as the purpose seems to be the same:
navigating from a parent table to a child one, and vice-versa.
Am I missing something?
Thanks!
HenriUnless you can show more detailed context, I think they are talking about
the exact same thing. A relationship is a bit more abstract; a foreign key
represents the implementation-specific way that a child row is connected to
a parent row.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Henri" <hmfireball@.hotmail.com> wrote in message
news:%23nSPik0TEHA.3828@.TK2MSFTNGP09.phx.gbl...
> I've bought a book about ASP.NET with SQL Server 2000.
> In one chapter, they talk about setting relations between tables, and in
> another, about setting foreign keys.
> But I can't understand the difference, as the purpose seems to be the
> same:
> navigating from a parent table to a child one, and vice-versa.
> Am I missing something?
> Thanks!
> Henri
>
>|||Actually, the first chapter is about the DataRelation class, and
DataTable.ChildRelations(String) and DataRow.GetChildRows(DataRelation).
The second chapter is about ForeignKeyConstraint Class
The only difference I see is that a foreign key allows to define cascade
update and delete rules.
Actually, ASP.NET permits to define many things like indexes, primary keys,
relations, etc. but I thought that this had to be done on SQL Server, not
from ASP.NET.
That's why I'm a bit lost :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> a écrit dans le message de
news:ORWb%23o0TEHA.2416@.TK2MSFTNGP12.phx.gbl...
> Unless you can show more detailed context, I think they are talking about
> the exact same thing. A relationship is a bit more abstract; a foreign
key
> represents the implementation-specific way that a child row is connected
to
> a parent row.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Henri" <hmfireball@.hotmail.com> wrote in message
> news:%23nSPik0TEHA.3828@.TK2MSFTNGP09.phx.gbl...
> > I've bought a book about ASP.NET with SQL Server 2000.
> > In one chapter, they talk about setting relations between tables, and in
> > another, about setting foreign keys.
> > But I can't understand the difference, as the purpose seems to be the
> > same:
> > navigating from a parent table to a child one, and vice-versa.
> > Am I missing something?
> > Thanks!
> > Henri
> >
> >
> >
>
>|||What you are reading about is Data Sets in ADO.Net. The
relations and constraints you define in a data set are
different and separate from relations and constraints in the
database. In ADO.Net, you can create something similar to a
database - tables (data tables), relationships (using the
DataRelation class), constraints (such as with the
ForeignKeyConstraint class). It's not the same thing as the
database you may be accessing for the data in the data sets.
For ADO.Net, you can find more information on how relations
and constraints work together, differently in .Net Framework
documentation. Check the remarks section of the definition
of the DataRelation class.
-Sue
On Fri, 11 Jun 2004 03:40:00 +0200, "Henri"
<hmfireball@.hotmail.com> wrote:
>Actually, the first chapter is about the DataRelation class, and
>DataTable.ChildRelations(String) and DataRow.GetChildRows(DataRelation).
>The second chapter is about ForeignKeyConstraint Class
>The only difference I see is that a foreign key allows to define cascade
>update and delete rules.
>Actually, ASP.NET permits to define many things like indexes, primary keys,
>relations, etc. but I thought that this had to be done on SQL Server, not
>from ASP.NET.
>That's why I'm a bit lost :-)
>
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> a écrit dans le message de
>news:ORWb%23o0TEHA.2416@.TK2MSFTNGP12.phx.gbl...
>> Unless you can show more detailed context, I think they are talking about
>> the exact same thing. A relationship is a bit more abstract; a foreign
>key
>> represents the implementation-specific way that a child row is connected
>to
>> a parent row.
>> --
>> http://www.aspfaq.com/
>> (Reverse address to reply.)
>>
>>
>> "Henri" <hmfireball@.hotmail.com> wrote in message
>> news:%23nSPik0TEHA.3828@.TK2MSFTNGP09.phx.gbl...
>> > I've bought a book about ASP.NET with SQL Server 2000.
>> > In one chapter, they talk about setting relations between tables, and in
>> > another, about setting foreign keys.
>> > But I can't understand the difference, as the purpose seems to be the
>> > same:
>> > navigating from a parent table to a child one, and vice-versa.
>> > Am I missing something?
>> > Thanks!
>> > Henri
>> >
>> >
>> >
>>
>|||Hi
Within ADO.Net, a Foreign Key Constaint is a subtype of the Data Relation. The FKC in ADO.Net behaves in a similar manner to a FKC within SQL Server, but it is a constraint on the Data Set, not the database, which can be an important consideration
A Data Relation has additonal functionality that is not provided by the FKC, ( I think one is providing the Child Rows in the Data Set to a particular Master row.) I suggest you have a look at the class definitions and examine the different methods and properties each suppiles|||Thanks for your help to both of you :-)
Just one last question:
If I define constraints and relations(diagrams) within SQL Server, can
ADO.NET retrieve them, so that I can use them without having to redefine
them when declaring the DataSet?
I'm currently checking the.NET doc and might find the answer by myself, but
if you know it, thank you for telling me :-)
Henri
"Henri" <hmfireball@.hotmail.com> a écrit dans le message de
news:%23nSPik0TEHA.3828@.TK2MSFTNGP09.phx.gbl...
> I've bought a book about ASP.NET with SQL Server 2000.
> In one chapter, they talk about setting relations between tables, and in
> another, about setting foreign keys.
> But I can't understand the difference, as the purpose seems to be the
same:
> navigating from a parent table to a child one, and vice-versa.
> Am I missing something?
> Thanks!
> Henri
>
>|||AFAIK, not by itself. I'd be surprised if there weren't utilities available out there to generate this stuff
for you, though.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Henri" <hmfireball@.hotmail.com> wrote in message news:uvGyEt5TEHA.3420@.TK2MSFTNGP09.phx.gbl...
> Thanks for your help to both of you :-)
> Just one last question:
> If I define constraints and relations(diagrams) within SQL Server, can
> ADO.NET retrieve them, so that I can use them without having to redefine
> them when declaring the DataSet?
> I'm currently checking the.NET doc and might find the answer by myself, but
> if you know it, thank you for telling me :-)
> Henri
> "Henri" <hmfireball@.hotmail.com> a écrit dans le message de
> news:%23nSPik0TEHA.3828@.TK2MSFTNGP09.phx.gbl...
> > I've bought a book about ASP.NET with SQL Server 2000.
> > In one chapter, they talk about setting relations between tables, and in
> > another, about setting foreign keys.
> > But I can't understand the difference, as the purpose seems to be the
> same:
> > navigating from a parent table to a child one, and vice-versa.
> > Am I missing something?
> > Thanks!
> > Henri
> >
> >
> >
> >
>
>|||Thanks :)
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> a écrit
dans le message de news:eljMa15TEHA.1012@.TK2MSFTNGP09.phx.gbl...
> AFAIK, not by itself. I'd be surprised if there weren't utilities
available out there to generate this stuff
> for you, though.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Henri" <hmfireball@.hotmail.com> wrote in message
news:uvGyEt5TEHA.3420@.TK2MSFTNGP09.phx.gbl...
> > Thanks for your help to both of you :-)
> > Just one last question:
> > If I define constraints and relations(diagrams) within SQL Server, can
> > ADO.NET retrieve them, so that I can use them without having to redefine
> > them when declaring the DataSet?
> > I'm currently checking the.NET doc and might find the answer by myself,
but
> > if you know it, thank you for telling me :-)
> > Henri
> >
> > "Henri" <hmfireball@.hotmail.com> a écrit dans le message de
> > news:%23nSPik0TEHA.3828@.TK2MSFTNGP09.phx.gbl...
> > > I've bought a book about ASP.NET with SQL Server 2000.
> > > In one chapter, they talk about setting relations between tables, and
in
> > > another, about setting foreign keys.
> > > But I can't understand the difference, as the purpose seems to be the
> > same:
> > > navigating from a parent table to a child one, and vice-versa.
> > > Am I missing something?
> > > Thanks!
> > > Henri
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>

difference between table relations and foreign keys?

I've bought a book about ASP.NET with SQL Server 2000.
In one chapter, they talk about setting relations between tables, and in
another, about setting foreign keys.
But I can't understand the difference, as the purpose seems to be the same:
navigating from a parent table to a child one, and vice-versa.
Am I missing something?
Thanks!
Henri
Unless you can show more detailed context, I think they are talking about
the exact same thing. A relationship is a bit more abstract; a foreign key
represents the implementation-specific way that a child row is connected to
a parent row.
http://www.aspfaq.com/
(Reverse address to reply.)
"Henri" <hmfireball@.hotmail.com> wrote in message
news:%23nSPik0TEHA.3828@.TK2MSFTNGP09.phx.gbl...
> I've bought a book about ASP.NET with SQL Server 2000.
> In one chapter, they talk about setting relations between tables, and in
> another, about setting foreign keys.
> But I can't understand the difference, as the purpose seems to be the
> same:
> navigating from a parent table to a child one, and vice-versa.
> Am I missing something?
> Thanks!
> Henri
>
>
|||Actually, the first chapter is about the DataRelation class, and
DataTable.ChildRelations(String) and DataRow.GetChildRows(DataRelation).
The second chapter is about ForeignKeyConstraint Class
The only difference I see is that a foreign key allows to define cascade
update and delete rules.
Actually, ASP.NET permits to define many things like indexes, primary keys,
relations, etc. but I thought that this had to be done on SQL Server, not
from ASP.NET.
That's why I'm a bit lost :-)
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> a crit dans le message de
news:ORWb%23o0TEHA.2416@.TK2MSFTNGP12.phx.gbl...
> Unless you can show more detailed context, I think they are talking about
> the exact same thing. A relationship is a bit more abstract; a foreign
key
> represents the implementation-specific way that a child row is connected
to
> a parent row.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "Henri" <hmfireball@.hotmail.com> wrote in message
> news:%23nSPik0TEHA.3828@.TK2MSFTNGP09.phx.gbl...
>
>
|||What you are reading about is Data Sets in ADO.Net. The
relations and constraints you define in a data set are
different and separate from relations and constraints in the
database. In ADO.Net, you can create something similar to a
database - tables (data tables), relationships (using the
DataRelation class), constraints (such as with the
ForeignKeyConstraint class). It's not the same thing as the
database you may be accessing for the data in the data sets.
For ADO.Net, you can find more information on how relations
and constraints work together, differently in .Net Framework
documentation. Check the remarks section of the definition
of the DataRelation class.
-Sue
On Fri, 11 Jun 2004 03:40:00 +0200, "Henri"
<hmfireball@.hotmail.com> wrote:

>Actually, the first chapter is about the DataRelation class, and
>DataTable.ChildRelations(String) and DataRow.GetChildRows(DataRelation).
>The second chapter is about ForeignKeyConstraint Class
>The only difference I see is that a foreign key allows to define cascade
>update and delete rules.
>Actually, ASP.NET permits to define many things like indexes, primary keys,
>relations, etc. but I thought that this had to be done on SQL Server, not
>from ASP.NET.
>That's why I'm a bit lost :-)
>
>"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> a crit dans le message de
>news:ORWb%23o0TEHA.2416@.TK2MSFTNGP12.phx.gbl...
>key
>to
>
|||Hi,
Within ADO.Net, a Foreign Key Constaint is a subtype of the Data Relation. The FKC in ADO.Net behaves in a similar manner to a FKC within SQL Server, but it is a constraint on the Data Set, not the database, which can be an important consideration.
A Data Relation has additonal functionality that is not provided by the FKC, ( I think one is providing the Child Rows in the Data Set to a particular Master row.) I suggest you have a look at the class definitions and examine the different methods and pr
operties each suppiles

Dial-up replication - same domain?

Hi,

When setting up dial-up replication (via RAS, not Internet) is it possible for the 2 servers to be in different domains?

I've seen a lot of comments that suggest that both ends should be in the same domain, but I'm wondering if this is required, or simply suggested for ease of configuration.

Any advice much appreciated.

AndrewAs long as both domains are trusted to each other then no worries.|||Sounds good. Both domains will be Windows 2K, so I should be able to set up what I need.

Thanks for the feedback.|||For instance try to copy file between domains and see the results;|||File copying works a treat.

Now on to the difficult bit ... replication :-)|||It is but be prepared and refer to books online for initial help.|||I've already got replication working across the LAN so I'm comfortable enough with that, (in an amateur kind of way) but I've just made a discovery that might make my life really difficult...

I'm hoping to replicate from one SBS 2K machine to another SBS 2K machine via dial-up. The RAS dial-up connectivity works, but visibility seems to be one way. I can only map drives &c from the machine that initiated the call. From the RAS server, I can't see/map drives on the client that dialled in. If this is not normal/expected behaviour, then I'm guessing that its a trust issue and I started looking at that, only to discover that it seems you can't create inter-domain trusts with SBS. It seems to be a limitation of the SBS version of Windows 2000.

Sooooo....., if my dial-up login credentials aren't enough to give me all I need to get replication happening, I don't know what I'll do.

Fleeing the country comes to mind ... !

I'm going to try replication now and see what happens.

Wish me luck ...|||Our setup replicates between serveral servers of which all but one are *not* on a domain. Took a bit of fiddling with IDs (there are several places you have to set user id's and passwords) but it can be done.|||OK, cool, so I should be able to get it to work then.

Now for the really silly question ...

How do I actually get to see the server over dial-up so I can setup the subscription? When I establish the dial-up link I can't see the server at the other end using Enterprise Mgr so I can't define the Pull subscription. Should I be able to just register it and it should just work?

I know I'm missing something really dumb here!

TIA|||Update: I've got the server registration going over dial-up now, but only by IP address, not by server name.

Then trying to define the Pull subscription generates an error which I'm guessing is because the remote server is registered by IP address & not by name.

DNS setup problem?

Device Information Settings - SimplePageHeader

I am trying to use the new SimplePageHeader device information setting
which was introduced in RS SP1 for Excel exporting but have not seen
any impact when using the setting. Following is an example of how I
am using the setting in an URL:
...ReportName&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeader=True
My motivation for using this setting was an attempt to stop the export
from merging several of the columns in the report since this results
in the error "This operation requires the merged cells to be
identically sized" when trying to sort on various columns within
Excel. My thought was that by moving the header out of the actual
worksheet (which is my understanding from the documentation of what
the setting is supposed to do), the rendered report may not need to
merge cells to get the output formatted properly. Any suggestions
would be appreciated.I think the device info is SimplePageHeaders.
--
Nico Cristache [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"f_mumble" <fred_mumble@.yahoo.com> wrote in message
news:5e9391dd.0406281737.724e4c66@.posting.google.com...
> I am trying to use the new SimplePageHeader device information setting
> which was introduced in RS SP1 for Excel exporting but have not seen
> any impact when using the setting. Following is an example of how I
> am using the setting in an URL:
> ...ReportName&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeader=True
> My motivation for using this setting was an attempt to stop the export
> from merging several of the columns in the report since this results
> in the error "This operation requires the merged cells to be
> identically sized" when trying to sort on various columns within
> Excel. My thought was that by moving the header out of the actual
> worksheet (which is my understanding from the documentation of what
> the setting is supposed to do), the rendered report may not need to
> merge cells to get the output formatted properly. Any suggestions
> would be appreciated.|||Thanks for the follow-up, but adding the 's' didn't make a difference.
Are my expectations of what this device info setting supposed to
accomplish accurate?
As a test I completely removed the header from the report, and as I
suspected the columns are no longer merged in Excel. As a result,
Excel is able to sort any of the columns with no problems.
Unfortunately, having no header on the report is not an option, so any
other suggestions are welcome.
"Nico Cristache [MSFT]" <nipirvan@.microsoft.com> wrote in message news:<uFBPjyXXEHA.796@.TK2MSFTNGP10.phx.gbl>...
> I think the device info is SimplePageHeaders.
> --
> Nico Cristache [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "f_mumble" <fred_mumble@.yahoo.com> wrote in message
> news:5e9391dd.0406281737.724e4c66@.posting.google.com...
> > I am trying to use the new SimplePageHeader device information setting
> > which was introduced in RS SP1 for Excel exporting but have not seen
> > any impact when using the setting. Following is an example of how I
> > am using the setting in an URL:
> >
> > ...ReportName&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeader=True
> >
> > My motivation for using this setting was an attempt to stop the export
> > from merging several of the columns in the report since this results
> > in the error "This operation requires the merged cells to be
> > identically sized" when trying to sort on various columns within
> > Excel. My thought was that by moving the header out of the actual
> > worksheet (which is my understanding from the documentation of what
> > the setting is supposed to do), the rendered report may not need to
> > merge cells to get the output formatted properly. Any suggestions
> > would be appreciated.|||I eventually found out how to use the device info. Here are my findings:
It IS SimplePageHeaders - with an 's', plural
I used it as part of the URL when rendering directly to Excel. (I couldn't
find any way of settign this device information at design time?) The URL was
of this form
http://myserver/ReportServer?%2fTDSI%2fAssetsSummary&FxRate=1.2&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeaders=True
This outputted my report into Excel but I think SimplePageHeaders means no
header. My original report had images and text boxes in the header (which
were admittedly causing the cell merges) but following the above the
spreadsheet does not show any of these. Is this the best I can get?
"f_mumble" wrote:
> Thanks for the follow-up, but adding the 's' didn't make a difference.
> Are my expectations of what this device info setting supposed to
> accomplish accurate?
> As a test I completely removed the header from the report, and as I
> suspected the columns are no longer merged in Excel. As a result,
> Excel is able to sort any of the columns with no problems.
> Unfortunately, having no header on the report is not an option, so any
> other suggestions are welcome.
>
> "Nico Cristache [MSFT]" <nipirvan@.microsoft.com> wrote in message news:<uFBPjyXXEHA.796@.TK2MSFTNGP10.phx.gbl>...
> > I think the device info is SimplePageHeaders.
> >
> > --
> > Nico Cristache [MSFT]
> > Microsoft SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "f_mumble" <fred_mumble@.yahoo.com> wrote in message
> > news:5e9391dd.0406281737.724e4c66@.posting.google.com...
> > > I am trying to use the new SimplePageHeader device information setting
> > > which was introduced in RS SP1 for Excel exporting but have not seen
> > > any impact when using the setting. Following is an example of how I
> > > am using the setting in an URL:
> > >
> > > ...ReportName&rs:Command=Render&rs:Format=EXCEL&rc:SimplePageHeader=True
> > >
> > > My motivation for using this setting was an attempt to stop the export
> > > from merging several of the columns in the report since this results
> > > in the error "This operation requires the merged cells to be
> > > identically sized" when trying to sort on various columns within
> > > Excel. My thought was that by moving the header out of the actual
> > > worksheet (which is my understanding from the documentation of what
> > > the setting is supposed to do), the rendered report may not need to
> > > merge cells to get the output formatted properly. Any suggestions
> > > would be appreciated.
>

Developing a client server app using SQLServer - Steps

How do we go about setting a C/S application. Here are the steps.
1. Network Operating system.
2. SQL Server 2000 Installation on a Client / Server Network.
3. Install and setup Active Directory Services on a Client / Server
Network.
4. Concept of Domain Controller in a Windows Network.
5. Setup a Domain Model and Client / Server Model on a Network.
6. Secure Databases in Sql Server.
7. Setup and use Windows Authentication in Sql Server.
8. Setup and use SQL Server Authentication.
9. Create Logins in Sql Server.
10. Define Database Roles in Sql Server.
11. Define Server Roles in Sql Server.
12. Use the Enterprise Manager of Sql Server.
13. Use the Query Analyzer of Sql Server.
14. Create a Database.
15. Create a Table using SQL Script.
16. Create Primary Keys and Foreign Keys.
17. Create Indexes, Clustered and Non Clustered Indexes.
18. Establish Connection with SQL Server over a Network.
19. Create a Connection Object.
20. Create a Command Object, its Properties and Methods.
21. Create a Recordset Object in a Visual Basic ( VB ) application.
22. Access SQL Server Database using ADO.
23. Retreive Data From SQL Server Over a client server Network.
24. Create Multiple Command Objects using a Single Connection.
25. Specify a OLEDB data provider in Visual Basic ( VB ) for a client
server application.
26. Pass Connection Information to SQL Server over a network using
Visual Basic ( VB.).
27.Insert a New Record in SQL server using Visual Basic ( VB ).
28.Update and Delete a record using the Execute Method.
29.Execute a Stored Procedure using a Command Object.
30.Create a Input Parameter.
31.Create a Output Parameter.
32.Create Dynamic Recordsets, Keyset Recordsets, Static Recordsets,
Forward Only Recordsets.
33.Create Client Side Only Recordsets.
34.Assign a lock for Client Side Recordsets.
35.Navigate and Bind Controls to a Recordset.
36.Retrieve Fields of Recordsets.
37.Manually Populate Controls.
38.Add a new Record, Modify and Delete a Record.
39.Setup a DNS server.
40.Setup a DHCP Server.
41.Assign IP Address in a Client Server network.
42.Setup a Network Topology.
43.How to Create a Project.
44.How to Create a Menu.
45.SQL Server Security.
46.Standard Security Mode.
47.Setup a Integrated Security Mode.
48.Create Constants.
49.Relational Databases are used in a Client Server Accounting
application.
50.Implement relationships using Key Fields.
51.Client/Server Architecture.
52.Create a Class for developing a database application.
53.Object Oriented Programming is used in a VB/SQL Environment.
54.Use a Datagrid in a VB, Sql server accounting application.
55.Create and Use Standard Modules in a database application.
56.Design the database using SQL Server.
57.Program the Form_Load() event procedure.
58.Program the Form_Activate() event procedure.
59.Program the Cancelbutton.
60.Setup and Validate the data entered in the text box control.
61.Create and Add a Class using Visual basic ( VB ) for a client server
application.
62.How to write Property Procedures.
63.How to write Get Property Procedure.
Any questions email me. Before that you can have a look at the FAQ i
have collected and posted here http://www.vkinfotek.com/faq.html
Regards
MadhWha-a-a-a-t?
Arnie Rowland, YACE*
"To be successful, your heart must accompany your knowledge."
*Yet Another certification Exam
<pedaammulu@.yahoo.com> wrote in message
news:1151489920.428568.278820@.x69g2000cwx.googlegroups.com...
> How do we go about setting a C/S application. Here are the steps.
> 1. Network Operating system.
> 2. SQL Server 2000 Installation on a Client / Server Network.
> 3. Install and setup Active Directory Services on a Client / Server
> Network.
> 4. Concept of Domain Controller in a Windows Network.
> 5. Setup a Domain Model and Client / Server Model on a Network.
> 6. Secure Databases in Sql Server.
> 7. Setup and use Windows Authentication in Sql Server.
> 8. Setup and use SQL Server Authentication.
> 9. Create Logins in Sql Server.
> 10. Define Database Roles in Sql Server.
> 11. Define Server Roles in Sql Server.
> 12. Use the Enterprise Manager of Sql Server.
> 13. Use the Query Analyzer of Sql Server.
> 14. Create a Database.
> 15. Create a Table using SQL Script.
> 16. Create Primary Keys and Foreign Keys.
> 17. Create Indexes, Clustered and Non Clustered Indexes.
> 18. Establish Connection with SQL Server over a Network.
> 19. Create a Connection Object.
> 20. Create a Command Object, its Properties and Methods.
> 21. Create a Recordset Object in a Visual Basic ( VB ) application.
> 22. Access SQL Server Database using ADO.
> 23. Retreive Data From SQL Server Over a client server Network.
> 24. Create Multiple Command Objects using a Single Connection.
> 25. Specify a OLEDB data provider in Visual Basic ( VB ) for a client
> server application.
> 26. Pass Connection Information to SQL Server over a network using
> Visual Basic ( VB.).
> 27.Insert a New Record in SQL server using Visual Basic ( VB ).
> 28.Update and Delete a record using the Execute Method.
> 29.Execute a Stored Procedure using a Command Object.
> 30.Create a Input Parameter.
> 31.Create a Output Parameter.
> 32.Create Dynamic Recordsets, Keyset Recordsets, Static Recordsets,
> Forward Only Recordsets.
> 33.Create Client Side Only Recordsets.
> 34.Assign a lock for Client Side Recordsets.
> 35.Navigate and Bind Controls to a Recordset.
> 36.Retrieve Fields of Recordsets.
> 37.Manually Populate Controls.
> 38.Add a new Record, Modify and Delete a Record.
> 39.Setup a DNS server.
> 40.Setup a DHCP Server.
> 41.Assign IP Address in a Client Server network.
> 42.Setup a Network Topology.
> 43.How to Create a Project.
> 44.How to Create a Menu.
> 45.SQL Server Security.
> 46.Standard Security Mode.
> 47.Setup a Integrated Security Mode.
> 48.Create Constants.
> 49.Relational Databases are used in a Client Server Accounting
> application.
> 50.Implement relationships using Key Fields.
> 51.Client/Server Architecture.
> 52.Create a Class for developing a database application.
> 53.Object Oriented Programming is used in a VB/SQL Environment.
> 54.Use a Datagrid in a VB, Sql server accounting application.
> 55.Create and Use Standard Modules in a database application.
> 56.Design the database using SQL Server.
> 57.Program the Form_Load() event procedure.
> 58.Program the Form_Activate() event procedure.
> 59.Program the Cancelbutton.
> 60.Setup and Validate the data entered in the text box control.
> 61.Create and Add a Class using Visual basic ( VB ) for a client server
> application.
> 62.How to write Property Procedures.
> 63.How to write Get Property Procedure.
> Any questions email me. Before that you can have a look at the FAQ i
> have collected and posted here http://www.vkinfotek.com/faq.html
> Regards
> Madh
>