Viewing 15 posts - 301 through 315 (of 432 total)
To remove clustered SQL instance, you can launch the SQL installation Wizard, Select Maintance and then "Remove node from a SQL Server failover cluster." Start on the passive...
November 26, 2012 at 3:44 pm
Which version of SQL and which patch?
This sounds similar to my issue (which is posted in this section but has had no responses yet) where we added...
November 15, 2012 at 11:01 am
Reinstalling can be tricky. Try deleting the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server,
then delete the C:\Program Files\Microsoft SQL Server and C:\Program Files(x86)\Microsoft SQL Server(if you're 64-bit) folders, then reboot again.
November 14, 2012 at 9:47 am
Here is a summary of what is on this exam: http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-432&locale=en-us#tab2
You will need working knowledge of each area described here. If you have not worked in each of these...
November 9, 2012 at 3:26 pm
Thanks Sean! select * from sys.master_files is a better way to get a list of all active data & log files.
November 9, 2012 at 2:52 pm
For each Database in SSMS run
sp_helpdb <database name>
or
USE <database name>
SELECT * FROM sys.database_files
This will help you build a list of all data & log files that ARE attached.
If...
November 9, 2012 at 2:49 pm
Yes it would. Just make sure to do the Clustered installation of SQL. If you do a non-clustered installation - even on a clustered OS - you'll...
November 8, 2012 at 2:55 pm
In this case all applications will support the same edition/version/patch level. No conflicting instance-level settings are needed and Transparent Data Encryption will not be used. I'm...
November 8, 2012 at 9:31 am
Network issues can make clusters inaccessible, prevent failover, or trigger failovers than shouldn't happen, but they shouln't cuase the cluster instance or SQL server to completely shut down.
November 8, 2012 at 9:26 am
Separate databases can have different database options set. Recoverability is a BIG advantage partularly in development. If one developer hoses what he's doing and wants to revert...
November 7, 2012 at 10:51 am
Lesson learned: If you are doing massive changes to a large database that you'll want to reverse, use a full backup, not a snapshot.
http://support.microsoft.com/kb/2002606
Dan
October 12, 2012 at 2:47 pm
I'm curious why a search query would have so many criteria. Usually a search query will be by a primary key or other unique identifier, or by 1-3 columns...
October 5, 2012 at 2:48 pm
deleted - misread context of question.
October 5, 2012 at 2:41 pm
When I came onto this job and looked at the SSMS Security node for the instances & DBs I was now reposonsible for, I saw long lists of logins I...
October 5, 2012 at 11:45 am
I've also thought of creating one proc that takes the database name as the parameter. Asking them to type something like
exec sp_manualbackup 'databasename'
would not be so bad...
October 5, 2012 at 11:31 am
Viewing 15 posts - 301 through 315 (of 432 total)