Anyone know of any kind of little script or utility that can be placed on an end users PC to backup a specific database whenever they want? All I want it to do is to name it according to the date, place it in a predefined directory, and tell the user that it worked or failed. I am not very good at programing. Also, this is MS SQL 7. This tool needs to be fairly idiot proof. Any ideas?
We have some developers who manage SQL2000 servers from their WinXP workstations using Enterprise Manager. We have now rolled out our first SQL Server 2005.
Can we install the SQL2005 Management Studio side-by-side with Enterprise Manager on these WinXP workstations?
If not, what are most people doing in these cases?
I having a difficult time here trying to figure out what to do here.I need a way to scroll through a recordset and display the resultswith both forward and backward movement on a web page(PHP usingADO/COM)..I know that if I use a client side cursor all the records get shovedto the client everytime that stored procedure is executed..if thisdatabase grows big wont that be an issue?..I know that I can set up a server side cursor that will only send therecord I need to the front end but..Ive been reading around and a lot of people have been saying never touse a server side cursor because of peformance issues.So i guess im weighing network performance needs with the client sidecursor vs server performance with the server side cursor..I am reallyconfused..which one should I use?-Jim
I have a DLL that I have written in VB to automate certain functions in Mapinfo. I can use the DLL from Access or a VB project fine but I have problems in SQL Server 6.5. I can create an instance of the DLL ok using sp_OACreate, but when I call the function to create a Mapinfo Object in the DLL I get a VB error back 'Permission Denied' and my object is not created. Even so, the instance of Mapinfo is started (I can view it in my task manager)which I subsequently cannot close because according to the DLL it was never created!! I think this must be a SQL Server related problem since it works fine in VB/Access.
avaj writes "I was running SQL on my laptop (xp pro) when I load disk it tells me client side only I say okay and it loads using my local machine as server. This worked fine. Then it didn't. Everything was working; then I logged on and received the error message
"sql server does not exist or access is denied"
I have looked online for help and seen this error elsewhere but never in quite the same context as my problem; and the fixes I've read have not worked.
I've uninstalled, deleted and then reloaded the disk; still did not work. I'm at my wits end - I've been trying to fix this for a week.
in merge replication using sql server 2005 and sql server compact, is it possible to have triggers (or business logic) for any changes on the client side? how does a client app know an insert/update/delete has been made? also, if the article is set to download-only, can the client app also be nofied of any changes?
hi friends;I have problem about sql server insert and update in client side.I am coding windows application with c#.When I run my code in databaseserver computer all is fine.I can see data, insert and update.But whenI run same code in client side I can see data but not insert notupdate what can I do about this problem .I use sql server 2000database.Client side connections ok. :( thanks for all
I have a database mirroring session running, and both principal and mirror are working fine. But when i unplug the network cable from principal server, creating a failover scenario, the client doesn´t get redirected to the mirror.
I get an error saying: "A transport-level error has ocurred when received results from the server. The specified network name is no longer available."
I think the error is because the ExecuteNonQuery() method return info about the rows affected on the server. But in this case how can i create a failover scenario with client-side redirect ?
I have set up mirroring and trying to get it to work from my .NET application. Mirroring seems to work ok. When I do a manual failover the witness is updated properly in the sys.database_mirroring_witnesses table so it seems to be configured correctly. I also can shutdown the master database and the mirror takes over.
My application is configured with Server set to my master database and FailOverPartner to my mirror database.
If I am connected to the master database and do a manual fail-over all my attempts to communicate with the database fail with an exception, even after repeated retries. (System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.).)
If I do a manual fail-over and restart my application it connects to the mirror database and everything is working. If I now do a manual fail-over I get the same exception, but after a few retries it connects to the master database.
The field Connection.Datasource always shows the master database regardless if it's connected to the mirror.
What am I doing wrong? Is this how it's supposed to work?
I have been pulling my hair over this problem and I just can't get it to work.
I'm using SQL Server Authentication to access the database and I can connect to the master when it's acting as principal and I can connect to the mirror when it's acting as principal, but when doing a fail-over, manual or shutting down the master server it never tries to connect automatically to the mirror even if it's changed role to principal.
Do the client need access to the witness in any way?
We just moved from SQL 2000 to SQL 2005 Ent. To use SSIS service, I need install this package on client side. But when I install the 2005 on my PC(Win XP Prof), I did not find any place I can include it. Anyone has similar experience or know how to do it?
Windows 2003 backup utility uses the shadow copy option that allows it to copy open files. Therefore, can I use this utility to backup the .mdf and .ldf files for my SQL 2000 database? I can then attach the .mdf files if I need to restore the database to another server. Can anyone tell me if this is safe? I've tried it and it worked but I'm worried there maybe some lurking danger in using this approach.
I'm getting errors in EM when trying to connect to one of my registered servers. When the Client Network utility is using TCP/IP as the default protocol I get:
A connection could not be established to xxxxx - General network error. Check your network documentation. ConnectionOpen (connect())...
But if I switch to use Named Pipes I connect just fine.
This worked just fine up until last week.. We're going through Tokenring to Ethernet conversions.. Is this a bigger network issue?
Could someone please explain to me the client configuration utility in plain English please.
I have VB applications installed on the sales force`s laptops that log onto SQL Server through RAS and an ODBC connection. The client configuration utility is not installed on their machines, but everything works fine. The BOL say that when installing utilities, the user is given the option of selecting the net-library to use. I am not, when installing it on my NT Workstation, or W95 Operating system. The BOL also state that the control panel has an entry to allow selecting which protocol to use. I cannot see it
Who needs the client configuration utility installed, obviously not the clients, is it just the people who want enterprise manager on their desktops ?
I am completely confused by this application This is the one area of SQL Server where I am lost, help !
I know this is a nasty way of doing but I can't think of another way. I'm retrieving an ID from a treeview when it's clicked client side, and I want to pass this to a SQL Procedure and retrieve some other data relating to it and fill a list box. Can this be done?
I want to know what are the configuration I need for the client side to connect to SQL Server Express 2005. Because i'm studying Network Application using SQL Server Express 2005.
Please help me guys, i really appriciated everything.
I have a problem while rendering a report which returns around 5000 rows. At first the server is busy to process the request, when the server is done the rendering client side takes 100% of CPU and never displays the result ("IE is not responding"). It seems that the ReportViewer has trouble to handle the server response.
My apologies if this question seems abit basic, but I'm a DBA by trade and programming .Net isn't my strong point ;)
I've enabled database mirroring on 3 SQL 2005 servers, a principal, a mirror and a witness.
Principal - SQL 2005 Enterprise Edition, SP1
Mirror - SQL 2005 Enterprise Edition, SP1
Witness - SQL 2005 Express, SP1
I've written some test code to test the mirroring but as soon as the connection is pulled from the principal, the client re-direct doesn't work and the program bombs. I'd be grateful fi someone could have a look at my code below and tell me if there's any schoolboy errors??
(NB, the user running the code is a sys admin on all 3 servers)
Thanks in advance.
Imports System.Data.SqlClient
Public Class Form1
Dim DCTADS As New SqlClient.SqlConnection
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
Primary platform is XP as client side and 2003 as server.
When I press F5 in order to see my report from IE appears this error:
An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'SQL1.BDADMIN'. (rsErrorOpeningConnection) For more information about this error navigate to the report server on the local server machine, or enable remote errors
However, preview button works properly and data are showed. Let me know where am I failing.
With Client-Side Redirect, connections can be dinamically redirected in case of failover. But if a long transaction is running on the principal, when it fails the redirect doesn´t work with the current ado.net connection, connected to the database running that transaction.
So if the principal fails, current running transaction will be lost right ?
Until now we worked with SQL Server 7.0, now we're migrating to SQL Server 2005.
With SQL Server 7.0 we had an MS Access application (located on a file server) used by several users, from which's form a batchfile (located on the same server) can be started. The Batchfile deletes an existing TXT-file called import_result.txt, then invokes a DTS-Package (located on a SQL Database server) which imports data to the Access-DB and creates a new file with the result of the DTS-execution (again called import_result.txt). Like that the user gets some information about success (or failure) of the data import.
How could this be implemented with SQL Server 2005 without having to install (and to licencse) SQL Express Engine on the clients? I found some threads about how to invoke an SQL Agent Job from the client to execute the SSIS-Package on the server, but I think that's not exactly what we need. Besides I'm not quite sure how exactly the SQL Agent Job could be invoked from Access.
Is there an INF file or a registry entry for the client network utility that I can move from machine to machine? I hate having to re-enter all of my SQL servers and alias' every time I install Tools on a new machine...Any help is greatly appreciated!!
I'm having to move workstations and was wondering if anybody knew a quick way to move all the alias's from your client network utility from one workstation to another.
I developed database driven .NET application and I need to deploy it. I faced a problem, which is "how to protect my database against direct access". I use MS SQL Server 2005 Express Edition as a DBMS and appropriate database.
I want to make possible to manipulate with data in my database only through my client application.
1. How do I define SA password and instance name in silent mode of MS SQL 2005 EE installation with Mixed type of Authentication?
1.1. Can I change SA password after the installation?
2. If my database be attached to my new instance... Is it possible to copy my database, attach it to another instance and get a direct access to its objects?
Is there solution that make impossible to connect to my database on third-partie's side Idirectly, without using the client application?
1) I am getting back into SQL more than before, in my new job. I need to find the service pack installed on the clients who have the Client Network Utility installed. I do not remember how to do this.
2) Running 'Select @@VERSION' on the server returns 7.00.1063 but does not indicate the service pack. Does this still mean sp4 has been installed?
I'm trying to ensure we'll all up to date since our dual 700 procs are acting eratic...jumps between 10 - 95% or so.
Server info:
NT Server SP6 SQL 7.0 2GB Ram 2 procs @ 700Mhz Roughly 80 network connections. No other programs running on server except Antivirus.
We are currently testing a Replication topology as follows: SQL Server 2005 Developer as publisher and distributor of a push updatable transaction replication 2 SQL Server 2005 Express clients as subscribers.
The replication is working great. If the connection is lost, the subscribers switch from Immediate to Queued Updating, and seem to shift back to Immediate when they regain the connection.
My question is to determine if there is a way that I can ask SQL Express on the client which mode is it currently running, or ask SQL Express if it has a current live connection to the distributor.
I know that they are usually mutliple ways to accomplish tasks, and I would be open any suggestions, preferrable programming in VB (such as with SMO or RMO) or using stored procedures or functions.
I hope this give some people something to chew on during the weekend and thank you to all that have taking the time to read this.
I'm trying to call the SQL 2012 SSIS packages deployed in SSISDB from batch files from another client system. But I couldn't find the DTExec.exe file in the 110Binn folder. How can I install this utility? Can I get this utility with client installation or do I need to install Server components which need license. I donot have license to install server component. how to install the DTExec utility without any licensing and provide me the Setup link where I can download and install.
We have just updated our sql 2005 server with sql SP 1. Should we apply this service pack to the client boxes that access this server or is that unnecessary?
I have a Windows 2003 Server running IIS 6.0 and SQL Server 2005. I have just (Today) deployed the first ASP.NET application (developed in Visual Studio 2003 and, as such, dependent on .NET Framework 1.1) on this server and am getting HTTP Error 403 (You are not authorized to view this page). This ASP.NET application runs fine on another server that is configured with the OS=Windows Server 2003, IIS=6.0 but without SQL Server 2005 and without the .NET Framework version 2.0. I found in the IIS Application configuration (on the troublesome site) that my app (in the Default Web Site folder) was pointing to the version 2.0 aspnet_isapi.dll. All efforts to use aspnet_regiis to "re-align" my app with version 1.1 have been fruitless to eliminate the HTTP Error 403. I granted the NETWORK SERVICE account privledges to the wwwroot folder. At this point, I don't know if I have a Framework error or a privileges problem.