Wednesday, March 21, 2012
is this disaster recovery / 'high availabilty" setup OK?
I am going to use two SQL servers for this application. These two SQL
servers are sync between them.
Each night, a copy of the SQL database is copied to a network share, and
then the backup program, ARCserve, will back up the database on the network
share nightly.
Is this approach a best practice? Any pointers/comments/suggestions are
greatly appreciated.
Thanks,What you want to achieve by using 2 servers ? to me using 2 servers for
accounting is not a good idea.
about backup - that is fine if you put databases in sync.
"Doug Fox" wrote:
> An accounting application uses a SQL server.
> I am going to use two SQL servers for this application. These two SQL
> servers are sync between them.
> Each night, a copy of the SQL database is copied to a network share, and
> then the backup program, ARCserve, will back up the database on the networ
k
> share nightly.
> Is this approach a best practice? Any pointers/comments/suggestions are
> greatly appreciated.
> Thanks,
>
>
Is this a new SQL BUG
For each login defined in the SQL Server, I'm finding that the error message is getting generated 18 times. My guess is that someone is trying to run some kind of code.
Any experience?Make sure you don't have any easily guessable accounts, and DEFINITELY, - change your SA password. This is not a bug (unless you don't have the latest security patch from M$, in which case it is and has been fixed). Whatch out, someone is after your server.
Friday, March 9, 2012
Is there anyway to tell when a database was last accessed or changed?
Is there a simple way to tell when a database was last accessed or changed?
We have some databases on old servers which we would like to discontinue but do not know if they are being used.
We would rather not just take them offline.
Is there anyway I can find out if they are still being used?
Please help if you can.
Regards, Major (that is my Christian name ;-)
I've run into this problem a few times. The best way I have found to deal with this is to set up a trace on the databases for reasonalbe period of time. With the trace, you should be able to see who accessed what, when, and with what application. This info can be helpful in determining how the database is being used in your organization.
The difficult part is to determine what constitutes a reasonable period of time. Some business groups access some databases on monthly, some on quarterly, and others on annual cycles. Other databases are used upon occurance of special events such as an audit or a lawsuit.
So, in addition to the trace, you may want to send out a survey asking for users to step forward. You will also want to be certain to take a few good backups and be able to access them very quickly should a user step forward after the database has been decommissioned.
Finally, get approval of higher-ups before dropping the database. This just helps spread the blame should someone in the business get upset.
Good luck,
Bryan
Adding on to Bryan's comments, when the decision is finally made, I normally just take the databases 'off-line' for a period of time. Then if something breaks, it is quick and easy to put the database back online. (I've been know to keep databases in 'off-line' mode up to a year before completely removing them from the server.
Even with backups, when some upper level 'suit' is put out because the special use database isn't available and he must have a report in a hour, it is a boon to quickly revert to on-line status and say 'oops'.
Wednesday, March 7, 2012
Is there any videos for reporting servers
yes.
Go to Susan site at:
http://blogs.msdn.com/swisowaty/default.aspx
Search there for her great webcast about reporting services.
Good Luck.
Is there any third party s/w that lists SQL servers in a network and query more info about
query more info about the server?Per this msft support article, just run this in query analyzer (mssql
2000).
http://support.microsoft.com/kb/321185/EN-US/
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY
('productlevel'), SERVERPROPERTY ('edition')|||Thanks Louis... This really helped. But how do I query this info of all
the SQL servers in a network? This only gives me info about the one
that I execute the script from... Is there a way to do that?
Thanks again..!|||On 16 Dec 2004 05:55:49 -0800, SQLDBA wrote:
> Thanks Louis... This really helped. But how do I query this info of all
> the SQL servers in a network? This only gives me info about the one
> that I execute the script from... Is there a way to do that?
> Thanks again..!
osql.exe -L is supposed to enumerate the servers on the network.|||I did some research on the groups and found out about SpotLight on SQL
servers by Quest. Has anyone tried this and can any one please let me
know if its worth buying this? Any other competiters who has a better
tool than this?
Thanks again...|||>Thanks Louis... This really helped. But how do I query this info of all
>the SQL servers in a network? This only gives me info about the one
>that I execute the script from... Is there a way to do that?
>Thanks again..!
Yes, you can utilize OSQL to run queries on all the SQL servers in the network.
You may have to insert all the outputs into a table and filter them.
just type "help osql" at the command prompt.
Joe
MCDBA, MCSD, OCP
Is there any third party s/w that lists SQL servers in a network and query more info about
query more info about the server? I need to find out the sql version,
whether its a msde or a msee. Also the service pack details and list
the databases in that server. Any help appreciated...
Thanks..!No need to buy a 3rd party apps for this.
use "osql -l" (try capital L if this doesn't work) at the command prompt.
If you want to obtain SQL info just use the following sp and xp. You can also
obtain these information remotely (without EM or QA) using osql.
exec master..xp_msver
exec sp_server_info