Search Results

Search found 3 results on 1 pages for 'msde2000'.

Page 1/1 | 1 

  • How do I shrink my SQL Server Database?

    - by Rory Becker
    I have a Database nearly 1.9Gb Database in size MSDE2000 does not allow DBs that exceed 2.0Gb I need to shrink this DB (and many like it at various client locations) I have found and deleted many 100's of 1000's of records which are considered unneeded. these records account for a large percentage of some of the main (largest) tables in the Database. Therefore it's reasonable to assume much space should now be retrievable. So now I need to shrink the DB to account for the missing records I execute "DBCC ShrinkDatabase('MyDB')"......No effect. I have tried the various shrink facilities provided in MSSMS.... Still no effect. I have backed up the database and restored it... Still no effect. Still 1.9Gb Why? Whatever procedure I eventually find needs to be replayable on a client machine with access to nothing other than OSql or similar.

    Read the article

  • Problem with MSDE 2000 5 minute keepalive over ISDN

    - by mcrick
    We have a SQL Server transactionally pushing replicate data to an MSDE 2000 SP3a subscriber over ISDN. Prior to a recent upgrade to bring us to the MSDE 2000 level we pushed to MSDE 1. We are finding that there is now a 5 minute keepalive being instigated from MSDE 2000 which we cannot account for. Further, we can find no way to either disable it or lengthen the keepalive interval. Not surprisingly, we are finding a marked increase in ISDN line costs due to these previously non-existent keepalive packets! Please note that we are assuming that it is an MSDE 2000 server issue, but it could equally be some behaviour related to the way that replication is operating on MSDE 2000. Unfortunately, as yet, we have not identified a replication configuration parameter that affects the keepalive in any way. Can anyone advise how we might indentify a root cause for this problem (and ideally a fix)?

    Read the article

  • SQL 2000 (MSDE) Hangs When It Receives an Erroneous Query from a Classic ASP Web Application

    - by Jimbo
    I have a SQL interface page in my classic ASP web app that allows admin users to run queries against the app's database (MSDE 2000) - it simply consists of a textarea that the user submits and the app returns the resulting list of records as below Dim oRS Set oRS = Server.CreateObject("ADODB.Recordset") oRS.ActiveConnection = sConnectionString // run the query - this is for the admin only so doesnt check for sql safe commands etc. oRS.Open Request.Form("txtSQL") If Not oRS.EOF Then // list the field names from the recordset For i = 0 to oRS.Fields.Count - 1 Response.Write oRS.Fields(i).name & "&nbsp;" Next // show the data for each record in the recordset While Not oRS.EOF For i = 0 to oRS.Fields.Count - 1 Response.Write oRS.Fields(i).value & "&nbsp;" Next Response.Write "<br />" oRS.Movenext() Wend End If The problem with this is that if you send it an invalid query (with a spelling mistake, invalid join etc.) instead of throwing back an error immediately, it hangs IIS (you can see this by trying to browse the app from another computer, it fails) for a number of minutes and THEN returns the error. I have NO idea why! Can anyone help?

    Read the article

1