While executing the estimated execution plan / actual execution plan, the missing index feature is not showing. How can I enable that ?
I am using SQL Server 2008
The missing indexes feature is on by default. No controls are provided to turn the feature on or off, or to reset any of the tables returned when the dynamic management objects are queried. When SQL Server is restarted, all of the missing index information is dropped.
This feature can only be disabled if an instance of SQL Server is started by using the -x argument with the sqlservr command-prompt utility.
Documentation.
Related
When I tried to build my web application, I was stucked for almost a week only because I didnot know to configure url with unicode information. Even if I publish the executed sql by hibernate, when the sql arrives at mysql server, it is actually encoded/decoded to different thing because of the usage of chinese character.
So I wonder is it possible to publish the arrived sql at mysql server side in order to make sure about what is going on at every level.
In order to publish the arrived sql at the mysql server side you should enable query logging
this link is showing how to do that
How to enable MySQL Query Log?
and official documentation
http://dev.mysql.com/doc/refman/5.7/en/query-log.html
I want to continually sync every 30 mins or less around 380000 rows of data from 11 tables from a SQL Server database to a MySQL database. How can I do this? What programs can do this?
This post, which is often used to close questions like these as a duplicate, does not work for me, for the following reasons.
The SQL Server is part of a CRM system, I'm not sure if it may be a lite version or something, but long story short I do not have access to the SQL Server Management Studio.
The MySQL database is part of my hosting package, which means I have access to it via phpmyadmin and the like, but not to the console or anything. And obviously I cannot access it via localhost.
So basically what I'm looking for is a way to connect to both databases, probably via ODBC drivers, and sync data every x minutes/hours.
I finally used a program called Omega Sync. Now called Spectral Core Replicator.
Omega Sync can compare and synchronize both database schema and table data. Schema comparison and synchronization for databases of same kind
Data comparison and synchronization even for databases of different kind
Compare and Synchronize databases of unlimited size!
Supported databases
Access
SQL Server
MySQL
Oracle
Interbase
Firebird
ODBC sources
I am not associated with this company or product in any way.
Microsoft SQL Server replication can apply the changes to generic ODBC/OleDB subscribers. You can configure MySQL as a subscriber if you follow the right steps and use the correct drivers, but is not officially supported so you are on your own if something goes wrong. Eg. see Set up replication between Microsoft SQL Server 2000 and MySQL. since the article is for SQL 2000 is already deprecated since Microsoft SQL 2008 supports OleDB subscribers, not ODBC.
You will need a very deep understanding of both Microsoft SQL Server, MySQL, ODBC/OleDB and Microsoft SQL Server replication. If you hit errors you'll have to solve them on your own, as the public information on this subject is scarce. I can only tell you that is possible and I've seen it done. Good Luck!
I am using an open source software which support mysql and i create application that uses asp.net 4.0 and sql server 2008....
Is it possible to Connecting MYsql with sql server ?
I want every insertion and updating should be made to both database servers as they have same schema of tables but one is mysql and other is sql server 2008 ?
kindly explain step by step if possible
hope this will help,this shows step by step connection
http://www.codeproject.com/Articles/29106/Migrate-MySQL-to-Microsoft-SQL-Server
You can use linked server in MS SQL Server.
From the documentation - A linked server allows for access to distributed, heterogeneous queries against OLE DB data sources.
Have a look at sp_addlinkedserver function.
We got some SQL scripts, some of them are using Syntax like :
Create procedure procABC(...)
as
begin
...
...
'ColA'= CONVERT(smalldatetime(10),ColB,103),
...
...
End
Same kind of syntax we also have for INTEGER like
INTEGER(5)
I know that this kind of syntax is used in MySql to set display width of a column or variable. But In any of the SQL Server version starting from SQL 7 to SQL 2008 this syntax fails.So my question is :
We have got this script from a SQL server machine as a backup, is it possible to have some kind of cached scripts, like we have in ORACLE where script may be invalid but still it will be on the server in invalid mode and will give compilation error if there are any syntax errors..
Is there anyway to achieve same kind of functionality in SQL server as we are supposed to re-create these objects (Something other then SUBSTRING) .
If I understand your additional information correctly, you have a SQL Server 2000 database that was created by some scripts, but the only scripts you have are in MySQL syntax and you're not sure how they are related to the SQL Server database. Your goal is to create a set of scripts that can be used to re-create the SQL Server 2000 database on a SQL Server 2008 system.
First, if that understanding is correct then I would completely forget about the MySQL scripts. They might have some value as documentation if there are useful comments in them, but they are not directly necessary for your task.
Second, I would upgrade your SQL 2000 database to SQL 2008. You can back it up and restore it on a SQL 2008 server, or you can upgrade the entire SQL Server itself from 2000 to 2008.
Third, I would generate the SQL scripts for the database objects using SQL Server Management Studio or the SMO API if you prefer. A Visual Studio database project could also be a good way to manage the scripts.
There is plenty of information on all these tasks on this site, in the SQL Server documentation, on MSDN etc. If you need more help, you should ask more precise questions about what you want to do and what you have tried already.
I have an existing multi-instance SQL 2008 cluster, and I'm trying to add Analysis Services to an existing instance. I start the installation, pick "Add features", configure SSAS, and then on the final pre-installation check, I fail the "Existing clustered or cluster-prepared instance" check. Of course I'd fail this check - I'm trying to add a feature to an existing clustered instance. Here's a picture of the error:
(source: trycatchfinally.net)
Has anybody successfully added a feature to a clustered instance in SQL 2008? I can't believe it can't be done - my alternative is to remove SQL from one node, try to add the feature again, hoping I don't fail this same check (though I probably will), and then re-add to the second node. This seems dangerous and unnecessary.
I found another person who had the same question, but the people answering it clearly aren't even reading the question, since they're mentioning how to cluster a server, and that he should use SQL 2000, so this is no help at all (though I'd love to point him here once it's answered: http://forums.techarena.in/software-development/1209984.htm
Take a look at the SQL Server 2008 Failover Clustering whitepaper.
http://download.microsoft.com/download/6/9/D/69D1FEA7-5B42-437A-B3BA-A4AD13E34EF6/SQLServer2008FailoverCluster.docx
Page 31 & 32
"Note: SQL Server 2008 does not support adding features to an existing failover cluster instance, so Analysis Services cannot be added to an existing instance of SQL Server. To share a resource group with an instance of SQL Server, you must choose to install Analysis Services during the initial installation of SQL Server."
Warning: I have never added analysis services to my existing cluster environment.
But this is how i would go about it:
1. Remove one node from cluster ( provided u have > 2 nodes ).
2. Install Analysis services.
3. Bring the node back into cluster.
Try to find necessary /skiprules parameter.
I have used the following setup SQL command to install SSRS feature with clustered instance:
Setup.exe
/SkipRules=StandaloneInstall_HasClusteredOrPreparedInstanceCheck
/Action=Install
The option to add or remove features is not supported either when running the setup through SQL Server Installation Center or when running the setup from a command prompt. For more information on the what happens when you try to add a feature through setup you can refer to the following forum post:
Why do I get ‘Rule “Existing clustered or clustered-prepared instance” failed’ error while adding new features to an existing instance of SQL Server Failover Cluster?
This article can be found here.
If you need to add or remove features to an existing installation you need to reinstall the virtual instance with the required features. For additional information you can refer to the following topics in SQL Server Books Online:
How to: Remove a SQL Server Failover Cluster Instance (Setup)
How to: Create a New SQL Server Failover Cluster (Setup)
Note: The SQL Server Analysis Services resource is a part of any SQL Server failover cluster’s resource group where Analysis Services is installed. Although it is possible to install both Database Engine and Analysis Services in the same resource group, it is generally recommended to install them as separate instances. Analysis Services is not dependent on SQL Server, and it should be installed to a separate resource group for maximum availability and performance.