Hi ,
We have a LAN set up in our company . I want that some specific local
machine's IP addresses to have access the live database server.
Want to restict machine's IP address from connecting to the live database
. How can I go for this ? I donot have that much idea about firewall and
router stuff . pls send me the link also which will help me in doing this.
I do have complex password for SA and have created a different login /role
and users for specific rights .But still want to do the above thing to make
the database more secured.
Pls help me in this.
Regards,
Swatiusing ipsec u can achive this. It is a filter. u can allow and disallow i.ps
.
"swati" wrote:
> Hi ,
> We have a LAN set up in our company . I want that some specific local
> machine's IP addresses to have access the live database server.
> Want to restict machine's IP address from connecting to the live databas
e
> .. How can I go for this ? I donot have that much idea about firewall and
> router stuff . pls send me the link also which will help me in doing this.
> I do have complex password for SA and have created a different login /role
> and users for specific rights .But still want to do the above thing to mak
e
> the database more secured.
> Pls help me in this.
> Regards,
> Swati
>
>
>
>|||Hi Suresh ,
Canyou pls throw some light on how to use the ipsec ? I am totally new in
this area . Waiting for your reply
Thanks & Regards,
Swati
"suresh" <suresh@.discussions.microsoft.com> wrote in message
news:35ED9BA4-EC43-4350-9CBE-81141FC72466@.microsoft.com...
> using ipsec u can achive this. It is a filter. u can allow and disallow
i.ps.[vbcol=seagreen]
>
> "swati" wrote:
>
database[vbcol=seagreen]
and[vbcol=seagreen]
this.[vbcol=seagreen]
/role[vbcol=seagreen]
make[vbcol=seagreen]|||http://www.microsoft.com/technet/it...ty/ipsecld.mspx
Using IPSec to Lock Down a Server
is a good start
Cheers
Ken
"swati" <swati.zingade@.ugamsolutions.com> wrote in message
news:O3U6tii7EHA.2608@.TK2MSFTNGP10.phx.gbl...
> Hi Suresh ,
> Canyou pls throw some light on how to use the ipsec ? I am totally new in
> this area . Waiting for your reply
> Thanks & Regards,
> Swati
>
> "suresh" <suresh@.discussions.microsoft.com> wrote in message
> news:35ED9BA4-EC43-4350-9CBE-81141FC72466@.microsoft.com...
> i.ps.
> database
> and
> this.
> /role
> make
>
Showing posts with label addresses. Show all posts
Showing posts with label addresses. Show all posts
Thursday, March 8, 2012
Friday, February 24, 2012
data types
I'm reading Sams TY SQL in 10 minutes and on the examples he uses CHAR for
practically everything, id's, addresses etc.
I upsized a small dbase from access and when I looked at a table, the
datatypes were a lot different. I noticed all ID fields were int and
nvarchar was used on most other fields. In the reserved words glossary, I
didn't see nvarchar. I guess it's missing a few types from the list.
I did a search for dbase schemas on google and found the Duwamish Book
example on MSDN. That dbase also uses nvarchar and int as the upsized access
dbase did.
Just curious why I should use nvarchar instead of char etc.
ThanksThe n in nvarchar indicates that it's for unicode. If you don't plan to use
unicode, you don't need to use nvarchar, and you can use varchar instead.
nvarchar is documented in the SQL Server Books Online.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"James" <no@.email.com> wrote in message
news:%23e1oE4TiDHA.1456@.TK2MSFTNGP11.phx.gbl...
> I'm reading Sams TY SQL in 10 minutes and on the examples he uses CHAR for
> practically everything, id's, addresses etc.
> I upsized a small dbase from access and when I looked at a table, the
> datatypes were a lot different. I noticed all ID fields were int and
> nvarchar was used on most other fields. In the reserved words glossary, I
> didn't see nvarchar. I guess it's missing a few types from the list.
> I did a search for dbase schemas on google and found the Duwamish Book
> example on MSDN. That dbase also uses nvarchar and int as the upsized
access
> dbase did.
> Just curious why I should use nvarchar instead of char etc.
> Thanks
>|||> I upsized a small dbase from access and when I looked at a table, the
> datatypes were a lot different. I noticed all ID fields were int and
> nvarchar was used on most other fields.
You shouldn't be using varchar unless you know you'll need to support
foreign alphabets / unicode characters.
For a description of the (n)(var)char/(n)text datatypes, see
http://www.aspfaq.com/2354
For an exhaustive discussion of differences between Access and SQL Server,
see http://www.aspfaq.com/2214
For some other issues with upsizing, see http://www.aspfaq.com/2182
> In the reserved words glossary,
Of a SAMS book? You should be using Books Online for this kind of thing,
IMHO. Also, see http://www.aspfaq.com/2080|||Thanks
practically everything, id's, addresses etc.
I upsized a small dbase from access and when I looked at a table, the
datatypes were a lot different. I noticed all ID fields were int and
nvarchar was used on most other fields. In the reserved words glossary, I
didn't see nvarchar. I guess it's missing a few types from the list.
I did a search for dbase schemas on google and found the Duwamish Book
example on MSDN. That dbase also uses nvarchar and int as the upsized access
dbase did.
Just curious why I should use nvarchar instead of char etc.
ThanksThe n in nvarchar indicates that it's for unicode. If you don't plan to use
unicode, you don't need to use nvarchar, and you can use varchar instead.
nvarchar is documented in the SQL Server Books Online.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"James" <no@.email.com> wrote in message
news:%23e1oE4TiDHA.1456@.TK2MSFTNGP11.phx.gbl...
> I'm reading Sams TY SQL in 10 minutes and on the examples he uses CHAR for
> practically everything, id's, addresses etc.
> I upsized a small dbase from access and when I looked at a table, the
> datatypes were a lot different. I noticed all ID fields were int and
> nvarchar was used on most other fields. In the reserved words glossary, I
> didn't see nvarchar. I guess it's missing a few types from the list.
> I did a search for dbase schemas on google and found the Duwamish Book
> example on MSDN. That dbase also uses nvarchar and int as the upsized
access
> dbase did.
> Just curious why I should use nvarchar instead of char etc.
> Thanks
>|||> I upsized a small dbase from access and when I looked at a table, the
> datatypes were a lot different. I noticed all ID fields were int and
> nvarchar was used on most other fields.
You shouldn't be using varchar unless you know you'll need to support
foreign alphabets / unicode characters.
For a description of the (n)(var)char/(n)text datatypes, see
http://www.aspfaq.com/2354
For an exhaustive discussion of differences between Access and SQL Server,
see http://www.aspfaq.com/2214
For some other issues with upsizing, see http://www.aspfaq.com/2182
> In the reserved words glossary,
Of a SAMS book? You should be using Books Online for this kind of thing,
IMHO. Also, see http://www.aspfaq.com/2080|||Thanks
Subscribe to:
Posts (Atom)