Can we set up two mirror databases to one principle server in SQL Server
View Complete Post
We have a DB mirror. We run a planned failover from one server to the other and everything worked fine. (including maintenance plan for backup of all types (Full, Diffrential, Log).
Yesterday we stopped the mirror server and everything was fine beside of that the backup log job (Maintenance plan) and another Maintenance plan job worked for all the time the mirror server was down (the jobs usually take 0.5- 5 minutes) and only when the
mirror server was back on they finished with the following error:
Database 4 cannot be autostarted during server shutdown or startup
i have a problem to bring the data from the oracle (external database) and the
sql server together (with similar data). The linq entities are linked to each
other. The structure is like different countries with different cities and so
on. To display these "non original linq objects" i need to put them
into entities (linked to each other). Now i add some of them to my sql database.
But for every entity i must check the connection to the other objects i don't
want to add and delete them (otherwise linq will add all the connected objects, even those I don't want to add). If this goes wrong the whole input-method crashes. Is there any
other possibility, except from checking every single entity and removing unwanted connections, to handle this procedure?
Thanks a lot,
For some versions it appears to be "select name from sysdatabases" and for some "sp_databases"
??? - thanks - dave
How can I get the databases names attached to specific SQL server instance?
I Need to configure Merge Replication, in this replication Can i chose the Replication Databases Recove model are
Simple is there any problem or not, why i am asking this question is, every time my log file size is become very large nearly 250GB.
Please help me
While SQL queries don't reference indexes explicitly, we all know how important indexes are to database performance. They constitute the backbone of database operations. Indexing currently is a difficult
undertaking usually mastered by senior DBAs/developers. What happens if a SQL Server site does not have an indexing expert? Performance will range from less than optimal to unacceptable.
The SQL Server Database Engine has access to all the technical information, albeit not all recorded currently, to enable automating indexing.
The DBA would have to supply query priority information, especially indicate which are the
Business Critical queries. It is safe to assume that very frequent queries are Business Critical. However, there are less frequent queries which maybe Business Critical as well.
In a nutshell current indexing wisdom: Primary Key columns (this is already automatic), Foreign Key columns and columns in WHERE clause predicates should be indexed.