SQL Server Health Check (T-SQL)

I'm looking for a peer review from my fellow SQL Server DBA's. I've written an 89-point health check that I'd really appreciate feedback on. You can find the health check scripts at www.sqlhc.com.
All scripts are free to use.
Thanks,
Chris Jones

Excellent!!! Great work... thanks.

Similar Messages

Common requirement_SSMA Runtime emulation components were not found on SQL Server, please check if Extension Pack is installed correctly

Greetings,
After the installation of the extension pack (local sql server and installed local) i get this warning:
Common requirement SSMA Runtime emulation components were not found on SQL Server, please check if Extension Pack is installed correctly
and
Common requirement SSMA Synchronization components were not found on SQL Server, please check if Extension Pack is installed correctly.
In the Program and Features Control panel the Feature "SSMA Extensionpack" (or similar) is installed and i see it in the startmenu.
what's wrong here, any hints?

Hi A. Bloise,
Based on your description ,we need to verify that the type and version of SSMA Extension Pack. Assume that you install SSMA for Oracle Extension Pack, I recommend you check the following things.
1. Make sure that the setup file of SSMA for Oracle Extension Pack is not corrupted. You can download it from
Microsoft Download Center.
2. Make sure that your computer meets the following requirements for the SSMA for Oracle Extension Pack.
    •SQL Server 2005 or higher.
    •Microsoft Windows Installer 3.1 or a later version.
    •Oracle Client 9.0 or a later version, and connectivity to the Oracle databases that you want to migrate.
    •The SQL Server Browser service must be running during installation.
3. Make sure that the account used to install the extension pack, is a member of the sysadmin server role on the instance of SQL Server.
If this does not work, please contact with SSMA support team for further help:
[email protected]
Thanks,
Lydia Zhang

[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'

Hi,
We have exadata x3-2. I am seeing this error in alert log file frequently.
The db version: 11.2.0.3 On RAC on Linux 5.8 x86-64Bit
Errors in file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
The file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc
Contains many repeated lines like below
*** 2015-01-21 06:34:40.209
ERROR, tran=21.24.51311, session#=1, ose=0:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
Could any please help why is this happening.
Thanks

Hi,
You have customers who are running distributed transactions using a gateway which need to be rolled back. However, the gateway has not been correctly configured for distributed transactions. To roll back a transaction on the SQL*Server database a connection is made as the user defined in the parameter HS_FDS_RECOVERY_ACCOUNT in the gateway init<sid>.ora file but this user has not been created in the SQL*Server database with the password defined in HS_FDS_RECOVERY_PWD. This user also needs to own the transaction log table.
I assume you are using the Database Gateway for SQL*Server (DG4MSQL) as the Database Gateway for ODBC (DG4ODBC) doesn't support distributed transaction.
If you have access to My Oracle Support have a look at this note -
How to Setup DG4MSQL to Use Distributed Transactions (Doc ID 227011.1)
Otherwise, check the Gateway documentation.
Regards,
Mike

Upgrading SQL Server 7.0 to SQL Server 2000

Hello,
We want to upgrade Microsoft SQL Server 7.0 to SQL Server 2000 to implement Mobile scenario in CRM .If anyone has any utility implementation guide or good information regarding it ,kindly please forward it to my mail id [email protected]
Thanks and Regards,
Saumya Maheshwari

Hello Saumya,
I have sent you a Upgrade note. Hope that will be of help. However, I like to tell you that there is no migration procedure, per se. But you could follow the steps in the document and it should be a straight forward approach to 2000.
In case,the authentification of the SQL Server 7.0 is set to "Windows NT only";While upgrading, the user chooses "The SQL Server system administrator login information (SQL Server authentication)" in the "Connect to Server" step and enters the password for the system administrator (sa).
In the next step, the upgrade program checks if the user can log on to SQL Server. First, the Windows authentification of the logged on user is checked, which is successful. The 'sa' user and the relevant password are not verified. However, later in the upgrade process, the program tries to execute the scripts with the 'sa' user; this fails due to the "Windows NT only" authentification for SQL Server. The error ("Error running script: upgrade.sql(1)") message is written to the log file (upgrade.out) of the script (upgrade.sql):
Login failed for user 'sa'. Reason: Not associated with a trusted SQL
Solution - The upgrade program of SQL Server 2000 saves the settings of the upgrade in the registry. You can change the authentification mode there. Start the registry editor and go to the following entry in the left panel:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup\Resume\
Locate the "DO-NT" value in the right panel. Change this value from "0" (SQL Server authentification) to "1" (NT authentification). You can then restart the upgrade; the program now logs on to SQL Server via the Windows authenification and also executes the scripts under this authentification.
Please award points in case you find the solution of help to you.
Thanks
Sumit

How to find out sql server administrator account in sql server 2008 R2

how to find out sql server administrator account in sql server 2008 R2
adil

there is any way to find out actual administrator
because i forget that user i used to logon to server and installed sqlserver
adil
Hi adilahmed,
According to your description, you forgot the account which was used to install SQL Server. SQL Server service account information is stored in Windows Registry database. You can get this information from Services Console or SQL Server Configuration.
For example, to get account information from Services Console.
1. Go to Start > Run > Services.msc
2. Right Click on SQL Server Service, i.e. “SQL Server (InstanceName)” and go to properties
3. The account information is available under Log On tab.
Or you can get the information by using DMV and so on.
SELECT servicename, service_account FROM sys.dm_server_servicesGO
If you now log in SQL Server by using sysadmin account, you can check all login names in security and find the original account to login.
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Which is the best way to migrate the SQL SERVER 2000 Database to SQL SERVER 2003 Database?

Hi,
I need to migrate the Production database sql server 2000 to Sql server 2003, Please give me the best idea to migrate the database without any loss data, credentials and Objects.
Nandha Kumar

SQL server does not have any version named SQL server 2003 please check the version correctly it should be either SQL 2005,2008,2008 R2,2012
You can use the backup/restore to upgrade the SQL 2000 database to till SQL 2005,2008,2008R2
For SQL Server 2000 to 2012
First upgrade from SQL 2000 database to either SQL 2005, 2008 or 2008R2 and than upgrade it to SQL 2012.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/eaa1eb44-729f-466b-8233-cb768fbb4208/upgrading-to-sql-server-2008-from-sql-server-2000?forum=sqlsetupandupgrade
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4fac7511-2c75-46a0-802b-807dd26b12bf/sql-2012-will-not-convert-a-sql-2000-database?forum=sqlservermigration
And after migration to SQL 2005 or 2008, if you want to script the database than can generate scripts pick DB and check off "script all objects in the selected database".
http://blog.sqlauthority.com/2011/05/07/sql-server-2008-2008-r2-create-script-to-copy-database-schema-and-all-the-objects-data-schema-stored-procedure-functions-triggers-tables-views-constraints-and-all-other-database-objects/
You can upgrade from SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 to SQL Server 2012.
http://msdn.microsoft.com/en-us/library/ms143393(v=sql.110).aspx
Please click the Mark as answer button and vote as helpful if this reply solves your problem

Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
"fix after" status.
First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService. That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list. I tried
setting the service account to a local account as well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

Hi Bob，
Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.) Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
specifically listed as a SQL DB user tries to use the front end they get an error of:
Microsoft SQL Server Login
Connection failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
Thanks a billion in advance ----

Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
all other roles, as well as allowing select only, and still have no access for the guest account.
The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
thru MS Access ACCDB, using a (by default) read only OCDB connection.
This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
since the result set would involve hundreds of thousands if not millions of records.
So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
as well as running our network on Microsoft's network software.

How to restore SQL Server 2008 database to SQL Server Express 2012

How to restore SQL Server 2008 database to SQL Server Express 2012.
I BACKED UP a SQL Server 2008 database from work, which runs the enterprise version of 2008, and I tried to RESTORE it to my new 64-Bit home PC which is running the new SQL Server Express 2012 64-Bit (Advanced Edition).
But if fails. I get the following message text.
Can anyone help me please. I thought restoring a 2008 database to the later version 2012 would be possible.
Here is the error message. Thanks.
TITLE: Microsoft SQL Server Management Studio
Restore of database failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the backup, or use a
backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)

ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 8.00.2039. That version is incompatible with this server, which is running version 11.00.3128. Either restore the database on a server that supports the
backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.SmoExtended)
Are you sure your database is SQL server 2008 from error message it seems your SQL server version is 2000.I guess you have multiple versions of SQL server.
AFAIK you cannot restore backup of SQL server 2000 to 2012 directly .Restore it first to SQL 2008/2008R2 or 2005 then take backup again of new database created and then you would be able to restore it on 2012.Its kind of intermediate way
Also make sure your DB size is less than 10 G as max DB size supported by Express edition is 10 G and if your DB size is more than 10 G restore will fail.
You are also trying to restore enterprise DB backup on express edition so you will loose enterprise features on express edition
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Daily backup on Ms sql server management studio (MS sql 2005).

I wander how to perform daily backup on Ms sql server management studio (MS sql 2005).
In sql server Entereprise manager (MS sql 2000) I had no problem to shedule.
But now I do not find this option

Hi
Please follow these steps in SQL Server Management Studio in SQL Server 2005 and <b>award points</b>
1. Start SQL Server Management Studio.
2. In the Connect to Server dialog box, click the appropriate values in the Server type list, in the Server name list, and in the Authentication list.
3. Click Connect.
4. In Object Explorer, expand Databases.
5. Right-click the database that you want to back up, click Tasks, and then click Back Up.
6. In the Back Up Database - DatabaseName dialog box, type the name of the backup set in the Name box, and then click Add under Destination.
7. In the Select Backup Destination dialog box, type a path and a file name in the Destinations on disk box, and then click OK.
8. In the Script list, click Script Action to Job.
9. In the New Job dialog box, click Steps under Select a page, and then click Edit if you want to change the job parameters.
Note In the Job Step Properties - 1 dialog box, you can see the backup command.
10. Under Select a page, click Schedules, and then click New.
11. In the New Job Schedule dialog box, type the job name in the Name box, specify the job schedule, and then click OK.
Note If you want to configure alerts or notifications, you can click Alerts or Notifications under Select a page.
12. Click OK two times.
You receive the following message:
The backup of database 'DatabaseName' completed successfully.
Note To verify the backup job, expand SQL Server Agent, and then expand Jobs. When you do this, the SQL Server Agent service must be running.

Upgrade from sql Server 9.0 to sql Server 12.0

I am currently running SQLEXPRESS (SQL Server 9.0) It appears that there is a limit to the size of the database which I have exceeded. I want to restore a backup of my customers DB and am not allowed to do so. Appears to be a size issue,
the customer DB is over 5 GB.
Will I eliminate this size restriction using sql Server 12.0?
I don't see any references to upgrading sql Server 9.0 to sql Server 12.0, only references to a new installation. Can it be upgraded and how do I do that?

Hello,
Please read the following article.
http://www.mssqltips.com/sqlservertip/2941/upgrading-to-sql-server-2012-express
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server Express 2014 and SQL Server Agent

Any chance SQL Server Express 2014 supports SQL Server Agent. I have a home weather database and I have to import Data every 30 seconds.

Any chance SQL Server Express 2014 supports SQL Server Agent. I have a home weather database and I have to import Data every 30 seconds.
SQL server 2014 express does not have SQL Server agent.You can take help from creating batch files and running them thorugh CMD.windows scheduler will let you schedule it.
How to schedule and automate backup in SQL Express
Free job scheduling toll for SQL Express
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Server Audit Feature for SQL Azure

What is the status of support for SQL Server Audit features in SQL Azure? If auditing is supported in SQL Azure, can you point me to some resources that describe best practices for using auditing in SQL Azure?

New feature in Azure SQL Database!
Azure SQL Database Auditing tracks database events and writes audited events to an audit log in your Azure Storage account. Auditing is available in preview for Basic, Standard, and Premium service tiers. Auditing can help you maintain regulatory compliance,
understand database activity, and gain insight into discrepancies and anomalies that could indicate business concerns or suspected security violations.
See Get started with SQL database auditing
http://azure.microsoft.com/en-us/documentation/articles/sql-database-auditing-get-started/
Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

SQL Server 2014 New T-SQL Features

I have seen the following new T-SQL features:
1. In-memory OLTP tables.
2. Inline specification of CLUSTERED and NONCLUSTERED indexes is now allowed for disk-based tables.
3. The SELECT … INTO statement is improved and can now operate in parallel.
Any others? Thanks.
Kalman Toth Database & OLAP Architect
Free T-SQL Scripts
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

http://windowsitpro.com/sql-server-2014/top-ten-new-features-sql-server-2014
http://www.sqlpass.org/sqlserver2014/Webinars.aspx
Enhanced query processing for better performance without app changes.
Buffer Pool extension to SSDs for faster paging.
Resource Governor controls IO along with CPU and memory.
Enhanced Always On now supports 8 secondary for better HA (High Availability

Migrating SAP products from a non-SQL Server platform to a SQL Server 2005

Hi,
I have another question too.
Can someone pls provide me the Considerations for Migrating SAP products from a non-SQL Server platform to a SQL Server 2005 platform?
More specifically from Oracle to SQL 2005.
Regards
Abhi

Hello
You need to perform an OSDB migration.
This will involve exporting your SAP system into a DB neutral format and then reloading this into an SQL 2005 SAP system.
Please review http://service.sap.com/osdbmigration
I recommend you review the homo/heterogeneous system copy guide for your SAP release.
Thanks
N.P.C

SQL Server Health Check (T-SQL)

Similar Messages

Maybe you are looking for