I have an SQL express Server whereby the Transaction log becomes full.
Given the Edition of SQL server it cannot be directly managed with various tools like in the Standard Edition of SQL Server.
We do have another SQL Server - Full Standard version used in this environment as part of a larger system.
To anticipate the question: No we cannot add this database to that server.
Is there any way we can utilize the power of Standard SQL server to handle the Transaction logs for the SQL express server?
As if the Transaction Log was being handled by our full SQL Server with the tools available there?
Related
Is it possible to set up a replication between an SQL Server Express Database that we can't touch, with an SQL Server Standard database?
We only have read-only access on the SQL Server Express database, so we are oblige to use only SQL requests.
We thought of using a python script and doing the replication ourselves, but is there a framework that can do that ?
We don't need realtime replication, a time span of minutes is enough.
I am a bit confused about how SQL Server processes multiple queries while I run a query in SQL Server Express but the data is located in the Business / Enterprise SQL Server.
I have an Enterprise version of SQL Server installed on the server which has multiple TB of data. I do not have physical access to the server hence I have two approach. Use RDP to connect to the server and run the query, or connect to SQL Server instance via SQL Server Express which is installed on my local machine (obviously we should be in the same domain). I do not have any question about RDP, my concern is about the second approach.
When I run multiple queries on my local machine (not on the server), I noticed that the performance is very slow.
From here and here it look likes that my SQL Server Express is running the query and because of the # CPU limitation, it is very slow.
But I would like to be sure about how SQL Server processes my queries. To be specific, I would like to know more about step 3 and 4 as shown in here. Specially, I would like to know how Express and Enterprise talk to each other over tcp/ip. What does SQL Server Express send to Enterprise and what does Enterprise send to Express?
I found this article, but this one does not look like the thing that I am looking for.
Well, either
you are connected to your local SQL Server Express and the query is run there (locally - with all the limitations)
OR
you are connected (using SSMS from your local machine) to the SQL Server Enterprise database, and then the query is run on that server (not on your local machine - you just use a GUI on your local machine to see what's going on). Since those queries are run on the server, no limitations from your local Express instance will affect your queries
Unless you've setup some kind of replication or a "linked server", there's no "talking" between your local instance and the remote server instance.....
SQL Server is the database engine, and SSMS (SQL Server Management Studio) is just an IDE (Integrated Development Environment).
All queries are ALWAYS executed on the server regardless if it is Express or Enterprise editions.
SSMS does not execute a query ever, it does not do any work. It only passes the query to the server and display the resulting record set. The only speed difference that can be observed would be due to transferring the data set over the network from the server to the client.
Please read: What's the difference between SQL Server Management Studio and the Express edition?
Him
Please explain what is the difference between different datasources for SQL (shown in the pic.)
I mean difference between Microsoft SQL Server and Microsoft SQL Server Database File
Connecting to Microsoft SQL Server means that you are establishing a network connection to a SQL Server -- the database engine is running either on your machine or remotely and you are using the SQL Server as a service and are connecting to it. That server has the data and you just use a protocol to request operations to be performed.
Connecting using a Microsoft SQL Server database file (MDF) means that you want to use a database file and have a running SQL Server engine running locally use that MDF file. So, if you have SQL Express on your machine, when you create a connection to a MDF file, you're essentially using the SQLExpress engine on your machine to serve up that MDF file (and the database contents) to you.
I admit I almost always connect to a SQL Server, as I'm not guaranteed to have the MDF file available in all environments. Plus, I usually don't install SQL Express.
That's how I understand the difference. Hope this helps!
Maybe the "Microsoft SQL Server Database File" option refers to manually using SQL Server's files (*.MDF), whereas the Microsoft SQL Server refers to connecting to a full-blown SQL Server ?
I want to know if SQL Server Reporting Services Standard Edition is capable of running a report against a SQL Server Express database.
In addition if its possible to schedule reports against a SQL Server Express database.
Yes. Reporting Services doesn't care about where it gets data from.
Scheduling is handled by the SQL Server used by Reporting Services for its metadata. Nothing to with the source of the user data (Express in this case).
Is it recommended to use two versions of SQL Server (2005 and 2008) for storing data of an application. We have a situation where we have an existing web application consuming SQL server 2005 as a database. Some enhancements in the application required us to solution a FILESTREAM data store. Now we have our data in SQL Server 2005 and associated FILESTREAM data in SQL Server 2008. Being very new to SQL Server I would like to ascertain how bad is this in terms of performance? How can we achieve atomicity across both the database versions, is it via using a linked server or some other mechanism? Any alternative solutions would be fine except that we just cannot migrate the existing application to SQL Server 2008.
To keep your transactions ACID, you can use distributed transactions at a stored procedure level, or from a code level using DTC (e.g. via a .net TransactionScope). DTC would need to be present on both SQL Servers, and on your App Server as well if you do the ACID from there. There is some overhead with DTC
Edit : You will also need to link the servers with sp_addlinkedserver and provide credentials with sp_addlinkedsrvlogin