Showing posts with label exchange. Show all posts
Showing posts with label exchange. Show all posts

Tuesday, March 20, 2012

quistion about sqlserver

hi dear
do you recommend me to install exchange server with sql
server?
please tell me .
best regards
soheila zolfaghari> do you recommend me to install exchange server with sql
> server?
Both servers (Exchange and SQL Server) are memory-intensive, so you should
double check your current or estimated memory needs for your environment and
configure an upper limit for SQL Server manually. They will also compete for
CPU and I/O.
If you plan for previous versions of Exchange and SQL Server, SQL Server 7.0
and Exchange 5.5You must explicitly configure memory usage in SQL Server if
you run both a SQL Server 7.0 and a Microsoft Exchange version 5.5 server on
the same computer. SQL Server will not operate properly if you leave the SQL
Server minimum dynamic memory option set at the default value of 0.
I addition to this, I am not a fan of installing SQL Server together with
anything else, but on a tight budget and in a small environment, there are
no big obstacles for such configuration AFAIK.
sincerely,
--
your Software Submit.NET Team
http://www.softwaresubmit.net
mailto:info@.softwaresubmit.net

quistion about sqlserver

hi dear
do you recommend me to install exchange server with sql
server?
please tell me .
best regards
soheila zolfaghari> do you recommend me to install exchange server with sql
> server?
Both servers (Exchange and SQL Server) are memory-intensive, so you should
double check your current or estimated memory needs for your environment and
configure an upper limit for SQL Server manually. They will also compete for
CPU and I/O.
If you plan for previous versions of Exchange and SQL Server, SQL Server 7.0
and Exchange 5.5You must explicitly configure memory usage in SQL Server if
you run both a SQL Server 7.0 and a Microsoft Exchange version 5.5 server on
the same computer. SQL Server will not operate properly if you leave the SQL
Server minimum dynamic memory option set at the default value of 0.
I addition to this, I am not a fan of installing SQL Server together with
anything else, but on a tight budget and in a small environment, there are
no big obstacles for such configuration AFAIK.
sincerely,
--
your Software Submit.NET Team
http://www.softwaresubmit.net
mailto:info@.softwaresubmit.net

Saturday, February 25, 2012

Quick and Easy question

I want to present an option to one of my clients to
switch from Exchange to an SQL database.
They are using Public folder for a lot and we get blamed
everytime something gets deleted by a user. They do have
a lot of data in PF. I also know that when something goes
awol and we have to restore the PF by dismounting PF and
taking everyone down for however long.
My questions are these:
How quickly can you restore SQL. Do you have to take the
whole database down to restore; can you restore just
certain tables, data, etc ..; can the users still work
away while restoring any portion of the database?
Thanks for all the help!!
Kevin
A database is unavailable while it is being restored (although it can be in
use while being backed-up). You can control the placement of individual
tables and indexes on filegroups and then backup or restore those filegroups
individually. You can also do a point-in-time restore which allows you to
roll back to a point before any data loss or corruption occurred.
However, you seem to be asking the wrong question. I don't know Exchange but
in SQLServer the solution to your problem is to implement user/object based
permissions so as to prevent users from deleting data that they are not
authorized to delete.
David Portas
SQL Server MVP

Quick and Easy question

I want to present an option to one of my clients to
switch from Exchange to an SQL database.
They are using Public folder for a lot and we get blamed
everytime something gets deleted by a user. They do have
a lot of data in PF. I also know that when something goes
awol and we have to restore the PF by dismounting PF and
taking everyone down for however long.
My questions are these:
How quickly can you restore SQL. Do you have to take the
whole database down to restore; can you restore just
certain tables, data, etc ..; can the users still work
away while restoring any portion of the database?
Thanks for all the help!!
KevinA database is unavailable while it is being restored (although it can be in
use while being backed-up). You can control the placement of individual
tables and indexes on filegroups and then backup or restore those filegroups
individually. You can also do a point-in-time restore which allows you to
roll back to a point before any data loss or corruption occurred.
However, you seem to be asking the wrong question. I don't know Exchange but
in SQLServer the solution to your problem is to implement user/object based
permissions so as to prevent users from deleting data that they are not
authorized to delete.
--
David Portas
SQL Server MVP
--

Quick and Easy question

I want to present an option to one of my clients to
switch from Exchange to an SQL database.
They are using Public folder for a lot and we get blamed
everytime something gets deleted by a user. They do have
a lot of data in PF. I also know that when something goes
awol and we have to restore the PF by dismounting PF and
taking everyone down for however long.
My questions are these:
How quickly can you restore SQL. Do you have to take the
whole database down to restore; can you restore just
certain tables, data, etc ..; can the users still work
away while restoring any portion of the database?
Thanks for all the help!!
KevinA database is unavailable while it is being restored (although it can be in
use while being backed-up). You can control the placement of individual
tables and indexes on filegroups and then backup or restore those filegroups
individually. You can also do a point-in-time restore which allows you to
roll back to a point before any data loss or corruption occurred.
However, you seem to be asking the wrong question. I don't know Exchange but
in SQLServer the solution to your problem is to implement user/object based
permissions so as to prevent users from deleting data that they are not
authorized to delete.
David Portas
SQL Server MVP
--