issues when converting SQL Server 2000 database in to SQL Server 2005 database?
448734
I've had a lot of problems with this migration. Upgrading it in place gave me all kinds of security problems. What I finally did is:\n\n- Make a copy of the SQL 2000 db\n- Upgrade the copy\n- Detach the databases \n- Copy in the 2000 mdf and ldf files\n- Reattach the databases\n- Upgrade from 8.0 to 9.0 format.
1107412
I wish i could give you a definite answer but i cant. I have searched the web and there have been few people who had that problem and none of their posts had any replies.\n\nFirst try shutingdown Micrsoft SQL server or any other that you maybe running. then try installing VB6.\n\nOtherwise backup your databases, uninstall Sql server and ODBC components and try installing VB6 then.\n\nBefore you do any of the above mac sure you have the latest MDAC installed.\n\nhttp://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&DisplayLang=en
954519
You will have to save those in a DataBase Management System like SQL Server 2000.
494528
SQL Server 7.0 vs MSDE 1.0\n\nhttp://www.mssqlcity.com/Articles/Compare/SQLvsMSDE.htm\n\nread it v good
1101440
Hi,\nI am database programmer and use MS Access and SQl and others. Give a detailed example what you exactly want to do. Then I will tell you the design. I never designed a database wrong until now, hehe.\n\nA very important tip for you! If you want later export the database to SQL do NOT use the export wizzard of Access. This wizzard does not work and cost only time. Use the Import Wizzard in SQL. This wizzard works. \n\nNice greetings\nFranky
505572
Make sure you have added a reference to Microsoft ActiveX Data Objects 2.x Library to your project.  Then here’s code assuming you’ve created an ODBC Data Source – System DSN with the database named “Customers.”  Good luck!\n\nDim rsRecordset As ADODB.Recordset\nDim cnConn As ADODB.Connection\nDim strSQL As String\n   \nSet rsRecordset = New ADODB.Recordset\nSet cnConn = New ADODB.Connection\n\nWith cnConn\n    .ConnectionString = "DSN=Customers;UID=;PWD=Deleted=No"\n    .Open\nEnd With\n\nstrSQL = "SELECT * FROM CustNames”\n\nrsRecordset.Open strSQL, cnConn, adOpenStatic, adLockReadOnly
1181319
Here is a kb article from microsoft with some suggestions.\nhttp://support.microsoft.com/default.aspx?scid=kb;EN-US;Q195922
265935
Yes you can import them.  The easiest was is to use 3rd party software, I use a package called StatTransfer, it's made by the Stata Corporation.  It's really usefully in that it can convert just about any data source(mdb, sas, db2, etc.) to any other format.
1054783
Dude... whoever said "use the connection wizard" just isn't creative at all...\n---------------------------------------------------------\n\nHere is code that helps you get started:\n\npublic DataTable listExistingForAdmin()\n{\n//a temporary table for storing the data into a dataset\nstring temptable = "yourTableNameHere";\n\n//prepare the SQL statement...\nstring sql = "EXEC df_groups_listExistingForAdmin"; //your SQL code here\n\n//open the connection - use your connection string!!!\nthis.con = new SqlConnection("packet size=4096;user id=dbuser;password=dbuser;data source=YourDbServerName;persist security info=False;initial catalog=yourDbName");\nthis.con.Open();\n\n//instantiate the command\nthis.com = new SqlCommand(sql, this.con);\nthis.com.CommandText = sql;\n\n//instantiate the data adapter\nSqlDataAdapter adapt = new SqlDataAdapter();\nadapt.SelectCommand = this.com;\n\n//instantiate the DataSet\nDataSet ds = new DataSet();\n\n//complete the transaction\nadapt.Fill(ds, temptable);\nDataTable dt = ds.Tables[temptable];\n\n//clean house\nadapt.Dispose();\nthis.com.Dispose();\nthis.con.Close();\n\nreturn dt;\n}//end ()\n\nHope this helps!!
669526
It depends on which version of MS SQL Server 2000 you have. If you have the Standard or Enterprise version, then it can not be installed on Windows XP. The Desktop and Developer version, however, can be installed on WinXP.\n\nFrom Microsoft's SQL Server 2K requirements page:\n\n***SQL Server 2000 Enterprise Edition and Standard Edition can run on the following operating systems:***\nWindows Server 2003, Standard Edition1\nWindows Server 2003, Enterprise Edition2\nWindows Server 2003, Datacenter Edition3\nWindows® 2000 Server\nWindows 2000 Advanced Server\nWindows 2000 Datacenter Server\n\n***SQL Server 2000 Evaluation Edition and Developer Editon and Workgroup Edition can run on the following operating systems:***\nOperating systems listed above for Enterprise and Standard Editions\nWindows XP Professional\nWindows XP Home Edition\nWindows 2000 Professional\n\n***SQL Server 2000 Personal Edition4 and SQL Server 2000 Desktop Engine (MSDE) can run on the following operating systems:***\nOperating systems listed above for Enterprise, Standard, Evaluation, and Developer Editions\nWindows Server 2003, Web Edition5 (MSDE only)\nWindows 98\nWindows Millennium Edition (Windows Me)
1081549
Hey try this you will find the answer yourself \n\nhttp://www.microsoft.com/technet/prodtechnol/sql/2005/UsingRSwithSAPNetWeaver.mspx
636142
you need a connection string that tells your program where to point. then use your ADO datasource and set its command string. then just make a call to the database for whatever you want from it.\n\nhttp://msdn.microsoft.com/vbrun/vbfusion/usingsqlexpress/\n\nThe above resource connects to a sqlexpress database. The concept is the same for connecting to a sql2000 dbase the only thing that changes is the connectionstring.
135369
http://www.microsoft.com/technet/prodtechnol/sql/2005/learning/default.mspx
1333
Sorry in advance if Yahoo eats my indentation, but I think you are looking for something like this (tested under Access 2000):\n\n\nPublic Sub FiddlingWithQueryObjectsViaVBA()\n\n    Dim dbs As DAO.Database\n    Set dbs = CurrentDb\n    Dim qrydef As QueryDef\n    \n    Dim sSQLstring As String\n    Dim sQueryNames As String\n    \n    For Each qrydef In dbs.QueryDefs    ' iterate through all the Access query objects\n    \n        sSQLstring = UCase$(qrydef.SQL) ' Get the SQL for the current query\n        \n        If InStr(sSQLstring, "SOMETHING_I_AM_LOOKING_FOR") > 0 Then   ' I found what I'm looking for?\n        \n            sSQLstring = Replace$(sSQLstring, "SOMETHING_I_AM_LOOKING_FOR", "REPLACEMENT_TEXT") ' replace the text\n            qrydef.SQL = sSQLstring     ' update the query object with the new SQL\n        \n            sQueryNames = sQueryNames & qrydef.Name & vbCrLf    ' Maybe make a list of queries modified?\n        End If\n    \n    Next\n    \n    MsgBox "Modified the following queries:" & vbCrLf & sQueryNames\n    \nEnd Sub
1073711
First, since you didn't mention a particular version of VB, I would recommend using Visual Basic 2005 Express Edition. Associated with SQL Server 2005 Express Edition and Visual Web Developer 2005 Express, you can do really neat things very simply and quickly. Much better than previous editions.\n\nThen I would recommend three books:\n\n\n1. Wrox's Visual Basic 2005 Express Edition Starter Kit \nhttp://www.amazon.co.uk/exec/obidos/ASIN/0764595733\nTo begin. Included is a DVD-Rom containing VB 2005 Express, SQL 2005 Express and all the electronic documentation you'll need in the form of MSDN. The book is clear and good enough for an introduction.\n\n2. Visual Basic 2005 Express Edition for Dummies\nhttp://www.amazon.co.uk/exec/obidos/ASIN/0764597051\nThe book itself contains more ranting and lame jokes typical of the "for dummies" style, so it is pretty much useless, but the included CD-Rom contains very good tutorials and sample files that more than make up for the paucity of the book. Very good for a hands-on approach as opposed to the more theoretical approach of the first book.\n\n3. Beginning SQL Server 2005 Express: Database Applications with Visual Basic Express and Visual Web Developer Express  \nhttp://www.amazon.co.uk/exec/obidos/ASIN/1590595238\nIf the website you need to create relies on database and you need more info than contained in the first two books.
556992
The single biggest problem when converting an Excel file to any database is the field data integrity.  First you should review the data in the Excel file and groom the data - such that date fields only contain valid dates and number fields only contain valid numbers.  People putting information into an Excel file will typically put "extra information" in a cell - which then becomes a problem when converting.  Also, clean up the row headers - which will become the field names in the database.  Make sure they're unique - and all extraneous spaces should be removed from the field names (e.g., "First Name" should be changed to "FirstName" - no space).  Once the data is cleaned up - the data conversion should be successful.  I would also use an intermediate step of converting to an Access database first - then you can use the up-sizing feature in Access and easily convert the data into a SQL Server database.  Good luck!
1125881
Here are links to two utiliites that can correct exchange DB errors.  At different points in my career I have used them.  I would do Isinteg first, but keep in mind that when a database is being fixed that some data will be lost.