I have two SQL servers that I am trying to setup log shipping on. I am unable to get the restore of the initial database to work on the standby server. It gets a "unable to open file" error when trying to do the restore.
I have created a "syncaccount" user on both machines, and both have same password. I have used configuration manager to set the user/password for the agents on both servers.
I have given syncaccount admin access. I have added syncaccount to the shares on both servers.
Wy am I getting this error.
Does anyone else think it is VERY difficult to make this function work.
I have a WORKGROUP network with 2 SQL Server 2005 servers. I want to configure for log shipping.
When I try and set up the 'Secondary Database Settings', and try and run the process, it gets an error saying it cannot access the backup file (the secondary cannot access the backup file on the primary). The file is there. It is shared. I have created local accounts on both machines called 'SyncAccount', and have given full control over the shared directory (on the primary) and local directory on the secondary. I have chaged the SQL Agent to use the local account.
TITLE: Microsoft SQL Server Management Studio ------------------------------
SQL Server Management Studio restore database 'ISC'
I am embarking on a project to upgrade our SQL server environment. I'm curious for some opinions on the relative benefits of Log Shipping versus a Clustered environment and you have any experience that has helped form your opinion on the issue?
We have 4 Servers which have SQL SERVER 2012 and "AlwaysOn" have been enabled on all 4 servers:
Server1,Server2,Server3,Server4
Server1 is the Primary node and thr rest are secondaries. There is a Sync relation between Server1 and Server2 and also there is aSync relation between Server1 and Server3 & Server4.
Is it possible to setup log shipping from Server2 & Server3(secondaries) to two new servers?
I have finished a change request from our client. I need to update clients' database with the one in developments.Here is the changes i made to database:Added/Changed some tablesAdded/Changed some stored proceduresAdded data to some dictionary tableThe data in clients' current database MUST be kept. So how can I merge the changed information to clients' database?
I could not able to find Forums in regards to 'Log Shipping' thats why posting this question in here. Appriciate if someone can provide me answers depends on their experience.
Can we switch database recovery model when log shipping is turned on ?
We want to switch from Full Recovery to Bulk Logged Recovery to make sure Bulk Insert operations during the after hours load process will have some performance gain.
I 'm sure I am missing something obvious, hopefully someone could point it out. After a failover log shipping, I want to fail back to my inital Primary server database; however, my database is marked as loading. How can I mark it as normal?
I did the failover as follow:
I did a failover log shipping from the 2 server Sv1 (Primary) and Sv2 (Secondary) by doing the following
1) Stop the primary database by using sp_change_primary_role (Sv1)
2) Change the 2nd server to primary server by running sp_change_secondary_role (Sv2)
3) Change the monitor role by running sp-change_monitor_role (Sv2)
4) Resolve the log ins - (Sv2)
5) Now I want to fail back - I copy the TRN files to Sv1 - use SQL Ent to restore the database at point in time. The task is done; however, the database is still mark as loading. I could not use sp_dboption.
My package is to copy data from an Access 97 db into a SQL2k5 table.
Problem is that the 'mdb' is subscribed to a 'mdw' workgroup and I have been unable to workout / read how to get the SSIS manager to join the workgroup. Connection fails because "...you don't have necessary permission..."
I was able to do this previously for SQL 2k by messing with the registry, but I'm now on unfamiliar teritory.
Has anyone had problems like this. I recently got SQL Server 2005 Workgroup edition. I did the normal 'read everything I could' to make sure I was getting the correct version for my business. After having to wait 4 weeks to upgrade, as we were waiting for our accounting system to be upgraded to come inline with SQL 2005, I came across the problem where DTS is not really compatible to the degree I needed with this edition. I have since gone back to the reseller and they say we can't exchange it for Standard edition as 4 weeks has passed. The only thing we can do is pay out (1 month later) another £6,000 to get the version we need, totaling £11,000 Being that we are a small business, paying out another £6,000 isn't an option. Does anyone have any good advise on this? Many thanks Scott
My company has a large-ish website and we are migrating to new servers. There will be a web server (accessible to the world) backed by a SQL Server 2005 Standard server (only accessible by the web server and through VPN/Remote Desktop to administrators and our internal network). We can either put the database server (which is not in a cluster) on our domain or leave it in a workgroup. My first thought is leave it in a workgroup simply for security and reliability (i.e. if the DC goes down or loses connectivity), but people here are disagreeing with me.
Should I put the database server (which is not used internally at all) on the domain or leave it in a workgroup?
My company has a large-ish website and we are migrating to new servers. There will be a web server (accessible to the world) backed by a SQL Server 2005 Standard server (only accessible by the web server and through VPN/Remote Desktop to administrators and our internal network). We can either put the database server (which is not in a cluster) on our domain or leave it in a workgroup. My first thought is leave it in a workgroup simply for security and reliability (i.e. if the DC goes down or loses connectivity), but people here are disagreeing with me.
Should I put the database server (which is not used internally at all) on the domain or leave it in a workgroup?
Hi I've build a client management (Windows) application in VS2005 which works fine on the local development machine but falls over when trying to connect to the SQL Server Express file located on a second machine on the same Workgroup. Several of the apllications will connect to the database file from networked computers. The error I get when testing the connection or trying to connect via the App is:---------------------------------------------------------------The file "Z:BushBreaks.MDF" is on a network path that is not supported for database files.An attempt to attach and auto-named database for file z:ushbreaks.mdf failed. A database with the same name exists, or specified file cannot be opened or it is on a UNC share.--------------------------------------------------------------- How can I configure this database and/or connection to be able to allow connections to the MDF file? Please note that security is not an issue if that is at all relevant. Many ThanksJohn
We have a set of client servers which will include a SQL Server 2000 active/passive cluster attached to a SAN. We have all the equipment here (no attachment to client site) to configure. My worry is since it will have to be setup as a workgroup, and then shipped to client to add to their domain, is this a doable option. has anyone had to do this or tried this? Or would we be better off shipping whole thing to client and setting up cluster there?
I want to copy the database backup files to another server as a part of logshipping implementation. tried using xcopy it doesn't work. it says "invalid drive specification" also tried using a dll, the dll does the copying i just had to call the dll through an sp, while trying this the QA hanged, tried killing the process but the process didn't kill, i had to restart the service.
the network in not a domain its workgroup. with sql server 2000 on win2k server.
any inputs are welcome. thanks in advance regards, harshal.
I am currently hosting my ecommerce site on a dedicated server with dual AMD processors and 2 gigs of ram. I have on average 20 people on the site at one time.
on this server i have sql express, from which i understand, only utilizes one of the processors and 1gig of ram. I have the choice to pay an extra 150 a month to have my host put sql workgroup on my system.
My question is, will i notice any kind of real performace boost by upgrading. Or at the level that i am at, there wont be much difference?
I would like to ask regarding sa performance difference between the two version of SQL 2005. Which is better the SQL 2005 workgroup or the standard edition..?
We're running a simple network with a Windows XP Pro machine runningSQL Server. I have a VB application that runs fine on machines withinthe workgroup. There are several computers outside the workgroup butphysically reside on the network that generate OLEDB errors. I knowwith certainty it is establishing a connection to SQL Server. Theerror occurs on a SELECT statement. The user has read and writepermission to the database. I even tried giving the user Admin rightsjust as a test and it still generated the error. Is this a result ofthe cnmputer not being a member of the Workgroup? Thanks.Damon
Good afternoon,so here is a question I've been struggling with that I thought folks onthe forum might have some wisdom kicking around on. I have severalproduction servers that are living within a workgroup where there is nodomain controler. However, I would still like to set up trustedsecurity for my asp.net applications. IIS is living on one server, andSQL server on another. Is there a way I can add a trusted relationshipto the machine and account that the IIS app is running under?My thanks in advance!Jonathan Wiggs*** Sent via Developersdex http://www.developersdex.com ***
Hi have a small network setup and have MS sql server on workstation.Can access it locally but cannot access it from other work stations.I am assuming it is some sort of logon error, being it is not adomain. Any ideas on getting by this ?
I am a Systems Engineer and was sent on a job to a site that has a newly created SBS 2003 R2 Premium box which was OEM pre-installed from Dell. The SBS install was evidently finished off by the I.T. guys at the site. Now along comes some software house to install their propritery application. During this install process, the software guy was unable to find an instance of SQL running and installs SQL 2005 Express and the Express Studio management console. He installs his application and before he leaves says to the I.T. guys "Oh and by the way, there is a 4GB limit per database on SQL Express. You will have to change that to workgroup edition before the data grows too big. Have a nice day byeee!!!".
The I.T. guys go "Huh? Lets call James." So now I have to get this database off the SQL Express instance and onto a workgroup instance. I understand about detaching a database and re-attaching it. No prob there. What is confusing me is when I look at the default instance which should be a Workgroup instance, all I see is an Express instance.
What I am planning to do is rip out all the SQL 2005 stuff, leaving behind only Sharepoint, SBSmonitoring and WSUS stuff. The, using the SBS Premium cd's, install SQL 2005 again and updating the service packs for it again. Then mount the databases under it and get the software guys back in to reconfigure their application if need be.
Thing is, I have no idea how to sort it all out other than "Add remove programs" in control panel and remove the SQL 2005 stuff. What scares me however, is the thought of also removing the Sharepoint, WSUS and SBSMonitoring databases too.
Can someone help me with a procedure for sorting it out? How can I tell what I should uninstall and what I shouldn't? How do I tell if workgroup is already there and why did express steal the default instance?
I have 2 web servers in a workgroup both running SQl 2005 SP2. both servers have a user called sqluser which is the main login for sql on both boxes. When I use the mirroring wizard it creates the end points ok but does not like the fqdn of each server, these are called webserver1 and webserver2. Is the problem because of the name and lack of domain ? Can I add a user for server1 on server2 or do I need to use certificates to get Mirroring working in this type of environment ?
We have got the wrong version of SQL Server 2005 due to not having SSIS. We have loads of DTS packages running and I have tried to import them and its shows no SSIS service installed.
Is the route to upgrade straight forward? We have a couple of databases running on 2005 upgraded from 2000 but most still are active on 2000.
I am a very beginner in setting sql server 2005. I was not sure if sql 2005 workgroup edition supported online database when I compared on MSN comparison chart. Does workgroup edition only work in local computers? Can I install 2005 workgroup edition on a windows server and run a business website requiring database?Thanks in advance.
In the following scenario, I am getting the message 'Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection'.
I am running a Windows Server 2003 with development environment and Sql Server Management Studio in a workgroup on a virtual PC.
My SQL Server 2000 is running on a domain server.
On the virtual Pc I have setup my user login and password to be the same as my domain login and password. Why is the Management Studio not using impersonation and allowing me to connect to the SQL server on the domain?
Hi Guys, I'm trying to connect to a sql express on a workgroup PC through sql server 2005 standard edition remotely but i can't. I have checked and make sure that tcp/ip and other protocals are allowed. There is no firewall on both PCs and the sql browser service is running as well. Somehow i can connect using the IP address but not the name?
HI All, After i installed SQL Server 2005 workgroups edition to my Laptop, P4 and 1 Giga memory. I had a problem. my problem is: when i start my laptop need 4 minutes to start the windows xp pro edition. then I format my laptop and install the windows again, and every thing works fine, but I installed the SQL again and i had same problem with windows startup, there is nothing related to SQL in ;msconfig utilities. do you have any tip about this problem ? Thank You
Would someone please tell my how to share the same NT Login on a Publisher and a Subscriber Server. For example, one of the requirements for Replication is that the Publication Server and Subscription Servers should share the same SQL Executive account. I tried doing this in Control Panel, Services Applet, Startup, and This Account Box. The Subscribing Server is not allowing me to map the login of the Publishing Server. I also tried within NT User Manager for Domains. I am not able to figure this out. I am trying to get Replication to work within a Workgroup on two NT 4.0 Servers SP3, with SQL Server 6.5 SP5a.
Hello -- Please excuse my extreme newbieness -- trying to get up to speed fast on SQL Server Express for work. I've been able to set up the software, create a database, and access it with no problems on my local computer, but I need to make the database available to other computers in my workgroup. I followed instructions -- enabled TCP/IP and Named Pipes and turned on SQL Server Browser, and I was actually able to manipulate one system database (the "master" database) from another computer but not any other databases, not even the other system databases. I can connect to any of the databases with the SQLCMD commands, but if I try to do any SELECT commands (other than in "master") I get an error: "SELECT permission denied on object '[MyTable]', database '[MyDatabase]', schema 'dbo'". I was only able to get into "master" after adding "guest" as a user, but adding this user to the other databases has no effect. One interesting thing: When I used the sp_table_privileges command on each database, all but "master" showed all privileges being granted to and from "dbo", but "master" didn't show anything being granted to or from anybody. Does anyone know what could be going on here? Am I missing something obvious? Thanks for any and all help!
I need to run a trace on a SQL 2005 Workgroup Edition. Profiler is onlyavailable in Standard and Enterprise?SQL 2005 BOL refers to serveral SPs and functions for tracing but I don'thave those in my workgroup edition.Any other options? Can I connect a SQL 2000 Profiler to 2005?Thanks.
In the past if we wanted to provide an application with simple (multi-user) database facilities, we would use an Access mdb database which we could basically xcopy deploy to the client. Share the folder across the network and apart from the limitations of mdb databases it would work !!!
With all the advancements in databases ! we have moved on to SQL Express - touted as the thing to use and the replacement for MSDE and MDB databases. But hang on a minute !! It doesn't work like that ! You can't deploy Express like we used to with MDB databases - the default Express database doesn't allow multi-access ?? and if you can't xcopy deploy the Express database. The 'user Instance' thing is useless - basically every user gets their own copy of the database !!! How many developers asked Microsoft for that one!! It's crazy!!
We just need to copy our exe files and the mdf file share across a workgroup and bingo network version of our software - it's not brain surgery - Is it! We don't need mountains of security - we need (FIRST OF ALL) easy deployment.
Please tell me I've got it wrong and you can deploy a SQL Express based application without jumping thru hoops ????
