Hello,
Is SQL Server 2005 mirroring production ready yet. We have two servers and plan to set up mirroring between them. We have the Standard Editon installed on them.
Is Standard Edition sufficient or does it need Enterprise Edition?
Thanks in Advance,
Sarath R
Can someone at Microsoft comment on this article, specifically, how it relates to SQL Replication? Will SQL Replication fall into the category of what this article describes, or only the mirroring feature?
View 1 Replies View RelatedI must release a new Db on 4/1 into an isolated small network (pier workgroup) and my choices are MSDE or Express. I'm new to both (MSDE yesterday, Express today). I am familiar with SQL Server and prefer using the tools with Express, but is it stable enough to use in this type of production environment?
View 5 Replies View RelatedI will be hosting my website in the next few months and doing more testing and I was having trouble finding a place to host the site that allows enough space for my sqlserver2005 database. I am estimating that the database will be around 40-50GB. Most hosting companies only give about 500MB for the database. Does anyone know of a company that provides more space? Also, is SQL Express production ready, or is it just for developing applications? If it is production ready, is there any "major" performace impact in using it over the full version. The reason I am asking is because hosting companies only give 500MB for a database, but alot more space for the web page. If I can put the SQLExpress file in the App_Data folder, then I will have more space. Does this even sound like it will work? Opinions are appreciated!
View 9 Replies View RelatedHello,Is the multiple instances capability of SQL2K mature enough for aProduction system?We're looking at upgrading our hardware but the proposed solutioncalls for consolidating two currently separate SQL Server's onto onemachine with two CPU's.Of the current two servers, one is for OLTP (~800Mb) and the other forreporting (some ad-hoc, some canned queries, 2-3Gb). We purge the OLTPdb nightly and archive the purged data in the reporting server whereit stays for a couple of months before getting purged from there.Maybe I'm being overly cautious here but the OLTP system is especiallytime-sensitive. If anything causes it to slow down significantly welose $$$.Thanks,Martin V.
View 1 Replies View Related
we are having 2 prodction servers in our environment.
and we are planning to perform database mirroring between them.i want to mirror server 1 databases to server2 and server 2 databases to server 1.
is this possible??
if possible , can any one give me a link to document where i can find more info on this, or send me the steps what i need to done for this...
thanks
Server A = primary SQL DBs (mirroring origination)
Server B = failover SQL DBs (mirroring destination)
For database mirroring a witness is required.
Can the witness live in another instance of SQL on server B?
I cannot understand how this was allowed to happen, but I can recreate the situation all day long. Someone, please tell me that I have missed an obvious solution to this;
With a fresh install of SQL 2005 Express (SP2) I have 4 databases installed and two service-based applications running. One of the service applications uses/requires three of the four databases and the second service application uses/requires the fourth database.
On boot, with the above described services set to depend on SQL Server service startup I get repeated failures on initial database access. Looking at the event log reveals why (in sequence):
SQL Server Startup...
Event: Server local connection provider is ready to accept connection on...
Event: Server named pipe provider is ready to accept connection on...
Event: Server is listening on [ 'any' <ipv4> 1911]
Application Service Startup...
Event: SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again
Moments Later:
Event: SQL Server is now ready for client connections. This is an informational message; no user action is required.
Now, its clear that the SQL service has started, and that this opens the floodgates for dependant services to start, each of which is told - essentially - to go away and come back once the SQL server has **really** started. With the accompanying suggestion to 'look for the informational message that indicates that SQL Server is ready' in the event log.
Am I reading the situation right so far?
In response to this, with my developer way of thinking, I could probably script the startup of application services rather than have them start automatically at boot or some such insane idea. But its not really the way that I had planned to spend the next few hours of my life, and it seems to me that I should not have to do such a thing.
Our in house service application (one of the two described) is in fact robust enough (just enough) to survive and to try the connection periodically, accomplishing a successful startup even with no database available.
The second of the two services is external and is unfortunately unable to start with no database available (Business Objects XI CMS). The normal means of making this service robust against database outages is the service restart procedure setting. But since the service doesnt ever start successfully, this doesnt work (learn something new every day - the restart is literal. It does not provide an initial startup retry and the service must have been started and fail for the retry to kick in)
Now, im not trying to bash anyone over this situation and regardless of the inflexible nature of the external service application and the general sillyness of the SQL server startup sequence - i mean c'mon... we are started but not ready? How about dont report startup until after you are ready? - the end result is that I need to come up with a solution to this problem.
I cant imagine that this is the first time that this behaviour has been questioned and I have to believe that there will be a simple, reliable workaround. I will keep looking for myself, but if any of this sounds familiar and you have a suggestion, your response will be greatly appreciated.
Hi,
I have a package which reads an XML file from a certain folder and parses it.
I deployed my package onto the server. Copied XML files on the D: drive the following folder on the server.
Dim reader As New Xml.XmlTextReader("D:AppsRequestClientsClientsStatus.xml") is fine.
But
Do While (reader.Read())
generates "The Device is not ready"
I think it is still trying to read it from my desktop on which I don't have a D drive.
Any help is appreciated.
Hi folks
I attended one of the SQL Server 2005 "Ready to Launch" parties a couple of years ago and was given a complimentary SQL Server Standard Edition CAL along with a copy of the SQL Server 2005 Standard setup DVD.
As there's no mention in the "Ready to Launch" pack of an included Server license I was wondering whether it is possible to install a copy of SQL Server 2005 on a standalone server and use the single CAL in a Production environment without having to purchase a Server license? The pack does include a Product Key - is this the Server license?
Thanks
Chris
Hello All, i am trying to create a normal ASP.NET application using VS2005. Yesterday i was adding tables.. entering data from within "View Table Data" tab, but today i am unable to do any data insertion or updating except by entering the insert or update statement by hand. When updating data of existing record or trying to add new data, it reports that "Cell is readonly!". I did not modify any settings or configuration and actually did nothing to set it to readonly! I am quite confused to be honest and writing sql statements by hand is kinda time consuming for me if i want to update a single field. What can i do to re-enable data modifications from VS2005 without reporting readonly? Thanks,Rakan
View 1 Replies View Relateddo i need a host with MS SQL SERVER? how do i upload my database? hmm
View 3 Replies View RelatedI just set up a server with Windows 2003 Standard x64. I have a copy of SQL Server 2005 Standard Edition that I got from the Microsoft Launch event. On the back of the case, it gives version requirements for both the x86 and x64 versions. When I went to install it, it didn't ask me which one I wanted to install. When I look on the CD, I see different installers for x86 and x64 for various pre-requisites, like MSXML. As I'm installing SQL Server I see that it is installing most things to "C:Program Files (x86)" which is where 32-bit programs go.. I decided to let it finish. Most of the binaries and everything, include sqlservr.exe, are in the Program Files (x86) folder, but it did install a few things in Program Files, so it must be aware of the difference.
I checked task manager and, I see that the sqlservr.exe and SQLAGENT90.exe are NOT 32-bit processes. So, great, they're running natively in 64-bit mode! But when I look at the server options in SQL Server Management Studio, the patform is listed as NT INTEL X86. The memory page also shows an option to use AWE which according to the documentation is only available and relevant to 32-bit installations.
SO I'm pretty confused. Almost everything points to this being an x86 installation, but the running processes are running natively in x64. Does anyone know what's going on here?
I just tried to run the x64 version of SP1 for SQL 2005, and it told me that it cannot update x86 products, so I guess that clinches it. I'm still pretty confused and annoyed though. If this isn't x64, how can I get an x64 version of the same product, and will my license key work?
We are using SQL Server CE 3. So far, the product gets an A for ease of installation and its ability to deal with complex queries and but fails in a number of other areas. This is causing mjor project overruns.
1. Speed is a major concern. Small simple queries take an unreasonable tme to execute. This has required fundamental changes to current design patterms and a major re-write.
2. Bugs: Set identity_insert tablename on: tablename appears to be case sensitive (10 hours to track this beasty down)
3 Vista seems to have its own issues - refusing to cast fieldnames for simple column names
eg 'Select UID as DepositID ...' returns a "DepositID" under Windows XP but returns "UID" under Windows Vista.
Does this mean there is a different engine operating in the Vista environment. [I have since tracked this to a quirk in the SDAC interface ]
All this in a product we are intending to ship in the near future.
Ar others having these / similar problems?
Is there a register of known issues and workarounds?
Is the product under active repair / development ?
Why is behaviour different under Vista?
I created a little test application with SQL server. After everything was tested successfully I builded a setup file with Installshield. I installed the setup file on a different mashine. Everything runs without problems, but when I make entries to the database and I reopen the application no entry is saved. I am new to SQL server.
thx for any help
I am getting alerts as Availability group not ready for automatic failover , how to check and resolve the issue ?
How to check the databases status whether they are in sync unsync in High availability ?
We're using ADO disconnected recordsets. On SQL 2000, we could update these on the client (without propagating the changes to the server) even if the underlying view or table was non-updatable.
When running our apps against SQL 2005 (using the same client-side environment), we can no longer change any attributes of those disconnected recordsets, that connect to a non-updatable database object (the rest of the app runs fine, we can update all updatable database objects through disconnected recordsets) . Does SQL 2005 respond to such calls differently from SQL 2000, so that ADO recordsets are built in a new way (which makes them read-only in our setting)?
Thanks for any suggestions.
Rene
how to resolve and trouble shoot the availability group is not ready for automatic failover in sql2012
View 4 Replies View RelatedWhen I execute the following transaction log backup TSQL in SSMS
BACKUP LOG ProductDB
TO DISK = 'D:Database_BackupTransProductDB.trn';
I get this error:
Msg 3201, Level 16, State 1, Line 2
Cannot open backup device 'D:Database_BackupTransProductDB.trn'. Operating system error 21(The device is not ready.).
Msg 3013, Level 16, State 1, Line 2
BACKUP LOG is terminating abnormally.
I also have a daily database backup job that puts the backup file under this directory.
D:Database_BackupData
So I changed the path to this and it still fails.
BACKUP LOG ProductDB
TO DISK = 'D:Database_BackupDataProductDB.trn';
However if I change it to this path, it works:
BACKUP LOG ProductDB
TO DISK = 'MyServerDataProductDB.trn';
This turns out to be the path I used a few weeks back when I backed up the log for the very first time. But I now wanted to store my transaction log backups in D:Database_BackupTrans.
I have this simple full text search query that works perfectly on my own computer using sql server 2005 express, however, on the production server(shared hosting)when I added the first 50+ rows, the full text search works perfect, but as the number of rows increases, the full text search can only see the first50+ rows, but not the new ones. Is there any quick solution for this or it's just a common mistake for developers for not properly indexed columns?Is there a way to re-indexed all rows without loosing data on the live server? search query: SELECT TOP 50 *FROM li_BookmarksWHERE FREETEXT(Keywords,@Keywords)
View 2 Replies View RelatedI currently have a SQL Server cluster setup with a Primary DB Server SERVER1 and the Standby server SERVER2. SERVER1 has been failing more than normal is the past few weeks and its takes upto 5 mins for SERVER2 realize that SERVER1 is down. I am looking for a better way to implement a backup server on production with minimum downtime. Please adivse..
View 1 Replies View RelatedProduction and development servers are on different domains and they do not trust each other. How do I import data from the table t1 from a database db1 in production and load it into table t1 inside database db1 in development?
View 3 Replies View RelatedAny help would be greatly appreciated.My problem is that I need to set up a backup SQL Server 2000 machinewhich can be used in case of a failure to my primary. All databases(30 as of now) must be an up to the minute exact copy of productionand include most recent changes in data as well as any structurechanges (Tables, Views, SP's, Triggers, Users . . etc).When I tried this using Transactional Replication, the replicationprocess gets fouled up once I introduce any kind of structure changesto the DB. I've considered the idea of doing periodic backups andrestoring it to my backup SQL server, but this does not give me theconcurrency needed with 0 latency.I've seen articles that recommend using Transaction Replication with'Scheduled Table Refresh', and also doing database dumps to restore onthe backup machine, but I have not been able to find any documentationregarding this to try out. How can I implement this type of backupstrategy in SQL 2000?
View 2 Replies View Related
I would like to deploy several reports to production server, Do i need to install reporting services entire software in order to run the reports or is it possible to just have runtime files installed on it to run the reports.
please help, i have almost 100 reports to be deployed on this server which is located in other country.
Thanks for the helpful information.
(i am using SQL server 2005 / reporting services 2005.)
ok ok, stop laughing. for real, is there any programatic way of doing this? whom ever created this database i inherited (SQL 2000) created the LDF and DATA files on the same drive and in the same folder for that matter. just trying to do a little disaster magament.
thanks
matt
This feels like a silly question, but I`m going to ask it anyway...
I have limited SQL Server experience, but have run into a wall with a client`s Web/Access combination. I need to upgrade to SQL Server. I have Beta3 installed on a development box and am very happy with it. Is anyone running this thing in a production environment? This isn`t going to be experience huge loads, so I`m tempted. Tell me if I`m crazy for wanting to try it.
I have a brand new database server with system databases.
I need to copy like four production database from another server to this new server. Can i do restore of the last production backups and restore them on the new server without creating the empty databases on the new server.If any one has better approach i will appreciate
1.First issue
The port number already allocated was 2059. We have changed that into the default port 1433 in the node. Now we are able to connect the node from the client application. But we are not able to see the configuration manager in any of the environment now.
2. 2nd issue
Cluster Environment
Error while executing the Package The connection details are not loaded in the connection manager tag
The same error with advanced information.
Another error window
R.S.Moorthy
I have production server 2000. The server gets disconnected sometime by itself and sometime it is working fine.Sometimes it even doesn't get restarted. Is there any problem with service packs and some performance issues.
Can you SQL guru give me best suggestion and how should i proceed.
Hi,I ran test data on my development machine and it took 1 minute toinsert the data. Ran the same set of data on the server and took 5minutes.Check both database and everything is the same. I even copied theproduction DB on my machine and it was taking still about 1 minute.Look at the fragmentation, and all the numbers are better on the serverthan my development machine so it should be faster.In the application I put some timer and discover that the insert istaking 0.015 ms on the server and 0 on the development. So the problemis on the insert.It is a Web application using ASP.NET.Here are the spec of the computers:Development: P4 HT 3.2GHz 1gig memory running WIN XPServer: Xeon 2.8GHz 1.5Gig memory running WIN 2000 serverAny idea how I to pinpoint the problem? I'm not at the point ofthinking that it can be the hardware, but how to verify that?ThanksFrank
View 2 Replies View RelatedHi,
Presently our Organisation is in process of Implementing SOX.
Under Compliance all the User have to be removed from the Production Server.
1.My Question is Do a DBA Should have Admin Privilages on the Production Server.
If yes then what are the Actitvies that a DBA has to perform only if DBA have admin privilages.
Regards
Sufian
Like most enterprise there is the database administrator (dba) and there are the developers(dev). The dba are conservative while the developers are also exploring their options.
One of the current usage I'm experimenting on is to provide data visualization - image for the data. Like most I needed to "create" the System.Drawing assembly in the database, marking it unsafe.
During my testing, my code had some exception and that brought down SQL Server.
I read that the CLR is better compare to the sp_OAs as well as the extended stored procedures written in C++ because it isolates the execution in a separate app domain and termination is clean - in case of any errors, it should not bring down SQL Server.
Also I read marking assembly unsafe void these benefits of isolation.
Instead of having to manage the situation where it involves code review by the dba and asking the dba to take some risk, is there a technique where all CLR code that runs in the production server does not pose stability issues.
How can I apply SP2 on running production server if SP resets all protocols (from TCP/IP enabled on production server to Shared Memory enabled) without disrupting its connections and thereafter its work?
View 1 Replies View Related