Hi Folks,
I have a 2000 remote server that polls the 6.5 server every 2 mins to check for access violation on the server via a query analyzer connection. It then uses xp_sendamil and net send for notifications.
The problem is, I've started to get loads of orphan connections from the remote server, which will not kill when attempted.
Any ideas, apart from stopping and starting sql service?
I have run a NOT EXISTS query comparing a table in test and production, to determine which records have been added to the table in production so I can import those records to test. The count(*) from both tables has a difference of 766 records but the query is showing 768. I am trying to find the easiest/quickest way to identify the orphan records.
View 2 Replies View RelatedLike orphan users, is there a way to figure out orphan logins?
------------------------
I think, therefore I am - Rene Descartes
Hi
Just logged on to one of the SQL Servers.I see a lot of logins there who dont have any database access. Its a SQL Server 2000 box.
Can someone please help me with a script that would get me a list of such Orphan Logins (not orphan users).
Thanks
Regards
Hi,Say, a database has all the FK constraints created properly, would sqlserver 2000 save this kind of meta data into sysforeignkeys table? Orit depends on ...?I'm trying to find all the orphen records in a given database via metadata.TIA.
View 7 Replies View RelatedNot sure if this is the correct place to ask. But it made sense to start here.
I have a legacy stored procedure that had been running under SQL2005 for some time correctly. Now it fails as it is trying to deal with user tables listed in the sys.objects view. The issue appears to be an individual table that no longer exists in the database but is still has a record visible from sys.objects. This entry is an orphan. My question is how do I remove the orphan record from sys.objects?
Thank you
Hello,
I have a VB program which uses ADODB.Connection to make connection to SQL Server DB.
However, under some circumstances, orphan / ghost connections remain in DB even after the VB program closed.
Here are the facts...
(1) Windows Server 2000 + SQL Server 2000
- run the VB program and made connection to the DB, leave it for 3 minutes, the connection closes when the program closes.
- run the VB program and made connection to the DB, leave it for 3 hours, the connection closes when the program closes.
(2) Windows Server 2003 + SQL Server 2000
- run the VB program and made connection to the DB, leave it for 3 minutes, the connection closes when the program closes.
- run the VB program and made connection to the DB, leave it for 3 hours, the connection does not close even after the program is closed.
Does anyone know if there is any problem with Windows Server 2003 + SQL Server 2000 using ADODB.Connection?
Or is there some kind of "timeout" parameter for which I can set to resolve such issue?
Any help is appreciated!!!
Thanks & Regards,
Andy.
I am using a table to display a very large amount of data (a basic list of information) with groups (the group header repeats on each page). Each of the groups can span multiple pages, The problem I have is that in the printed mode (or PDF) the group title may show at the bottom of some pages with no details (there may not be enough space for a detail row) and then the heading repeats on the next with the detail. How do I prevent this widow problem?
This can be controled in Access and Brio but not here seems a little odd.
Here's the DB Connection code for a site (Web.config file)
I was wondering how I could specify an idle timeout or orphan timeout.
I tried idle timeout=x and kept getting errors
<add key="DBConn"
value="server=localhost;Trusted_Connection=true;database=SaltwaterFishing;Min Pool
Size=5;Max Pool Size=150;"></add>
Thank you