After MSDE Upgrade To SQL 2005, MDF Is Not Found
Sep 12, 2007
After upgrading an MSDE 2000 instance to SQL 2005, the database appears to be intact - according to the log file:
2007-08-28 13:51:13.78 spid11s Starting up database 'HysterSuiteMainSQL'.
Then after a system shutdown:
2007-08-28 13:57:43.57 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.
It appears the MDF file disappeared mysteriously:
2007-08-28 14:03:11.84 spid51 Starting up database 'HysterSuiteMainSQL'.
2007-08-28 14:03:11.85 spid51 Error: 17207, Severity: 16, State: 1.
2007-08-28 14:03:11.85 spid51 FCB:pen: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'C:PROGRAM FILESHYSTER SUITEMSDEDataMSSQL$HS2000DataHyster.mdf'. Diagnose and correct the operating system error, and retry the operation.
Has anyone encountered this issue? Any ideas on what might have gone wrong?
Thanks,
Mike
View 1 Replies
ADVERTISEMENT
Apr 3, 2007
Hi,
I have 2 MSDE 2000 Instances installed on Windows 2003 Server STd w/ SP1.
The application relating to the default instance is being upgraded and will require SQL 2005 Express.
What is the best approach? So the named instance of MSDE 2000 still functions correctly.
Upgrade default instance of MSDE to SQL 2005, or install SQL 2005 Express to own path and restore the DB accross? Then remove the Default Instance of MSDE 2000.
Both MSDE 2000 Instances are listed in Add/Remove Programs.
Thanks
View 1 Replies
View Related
Feb 16, 2007
Hey, This is my first time posting here but here goes nothing...
Ok I upgraded an xp machine running to sql express 2005 by doing the inplace upgrade. The upgrade process went great, after the upgrade I could connect to the databases that had been upgraded using the management studio.
BUT.
When I try to connect to the databases using the third party software which had always worked in the past I get the error when trying to access from both the client and server machines.
[DBNETLIB][Connection open()).]SQL Server does not exist or access denied.
I then tried setting up SQL express 2005 on another xp station just to test how things worked if it wasn't an upgrade. I installed, attached the databases (which I copied to that local machine) and I was able to connect to them through the third party software from the server machine, but not client machines. The client machines gave me the same error as above.
Does anyone have any ideas, I have been talking to the third party support but haven't gotten any where yet... does anyone have any suggestions?
Thanks,
View 4 Replies
View Related
Sep 26, 2007
Hi,
I am trying to upgrade MSDE 2000 to MS SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) using a silent install.
MSDE on our systems is installed as a standalone product. There is only a single default instance (MSSQLSERVER) running on the system. SQL Authentication mode is being used.
When I try and upgrade MSDE 2000 directly to MS SQL Server 2005 Express Edition SP2, the install fails with an error:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I try to upgrade the default instance of MSDE to SQL Server 2005 Express Edition SP2 selecting Windows authentication (logging in as a domain/local administrator to the server), the install fails with an error:
"Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>"
However, MSDE 2000 upgrade to an earlier version of MS SQL Server 2005 Express Edition (Build 9.00.1399.6) using SA Authentication works successfully without any errors.
So I tried to upgrade our MSDE installation to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) as a 2 step process. First by upgrading MSDE to SQL Server 2005 (Build 9.00.1399.6) using SA Authentication which works successfully as mentioned earlier.
However, when I try and upgrade SQL Server 2005 (Build 9.00.1399.6) to SQL Server 2005 SP2 (Build 9.00.3042.0) using SA Authentication, I receive the same error as before:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I upgrade using Windows Authentication, the setup displays the following error:
"[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again"
The log file content for the error is:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=01000, level=0, state=1, native_error=0, msg=[Microsoft][SQL Native Client][SQL Server]Signing sps ...
sqlstate=42000, level=16, state=1, native_error=15119, msg=[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.
sqlstate=HY000, level=0, state=0, native_error=0, msg=[Microsoft][SQL Native Client]Unspecified error occurred on SQL Server. Connection may have been terminated by the server.
sqlstate=42000, level=16, state=2, native_error=2745, msg=[Microsoft][SQL Native Client][SQL Server]Process ID 51 has raised user error 50000, severity 20. SQL Server is terminating this process.
sqlstate=HY000, level=20, state=127, native_error=50000, msg=[Microsoft][SQL Native Client][SQL Server]Cannot create ##MS_AgentSigningCertificate## in msdb. INSTMSDB.SQL terminating.
Error Code: 15119
MSI (s) (08!80) [10:56:13:133]: PROPERTY CHANGE: Adding SqlUpgradeMessage property. Its value is 'SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.'.
SQL Server Setup has encountered the following problem:
Failed to execute the Transact-SQL statement:
/**************************************************************/
/* Sign agent sps and ...
Script file: sqlagent90_msdb_upgrade.sql
The error was: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
Error Code: 0x80073b0f (15119)
Windows Error Text: Source File Name: libodbc_statement.h
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcStatement::execute_batch@sqlagent90_msdb_upgrade.sql@967
Source Line Number: 91
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The registry entries suggest that the version now is 9.00.3042.0. However, I am not sure if the upgrade was successful. I can connect to the database using the old SA user ID and password.
If anyone else has faced similar issues, please let me know the workaround for the same.
Thanks and Regards,
Sahil Girotra
View 3 Replies
View Related
Sep 28, 2007
Hi,
I am planning an upgrade from MSDE to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) for our 2000/2K3 Servers. The MSDE installation on our servers is a standalone installation (default instance) and uses Mixed Mode Authentication. When I execute the setup program for upgrade and choose SQL Server Authentication (and enter the corresponding SA user Id password), the setup program displays an error "SQL Server Setup cannot upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade". However, when I select Windows Authentication for the upgrade, the setup program displays an error €ś[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again€? (Error Code 15119).
I even tried changing the Authentication mode from Mixed Mode to Windows Authentication (by changing the LoginMode registry key value to 1) and running the upgrade using Windows Authentication, but I receive the same error.
1) Is the password policy for SQL Server 2005 Express Edition SP2 different from MSDE or SQL Server 2005 Express Edition (Initial Version), since upgrade from MSDE to SQL Server 2005 Express Edition (Initial Version) worked successfully without any issues.
2) When I am using Windows Authentication for the upgrade, the installer does not prompt me for any password. What password is the installer validating against the password filter DLL? Is there a way to find it out? Also, is it possible to find out what was the reason for the password validation to fail?
I would really appreciate if I could get some answers to all the problems I am facing.
Thanks in Advance.
Regards,
Sahil Girotra
View 1 Replies
View Related
Sep 6, 2007
I have a Windows Server 2000/Windows Server 2003 Environments with MSDE installed (default instance) and SecurityMode is SQL. I want to upgrade from MSDE to SQL Server 2005 Express Edition using a silent install since the number of servers is huge.
I downloaded the latest SQL Server 2005 Express Edition SP2 Version 9.0.3042.0 from http://msdn2.microsoft.com/en-us/express/bb410792.aspx
I am having the following problems:
- When I try to upgrade the default instance of MSDE (MSSQLSERVER) to SQL Server 2005 Express Edition SP2 using the above installer and selecting SQL authentication, the install fails with an error "SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade".
- When I try to upgrade the default instance of MSDE (MSSQLSERVER) to SQL Server 2005 Express Edition SP2 using the above installer and selecting Windows authentication, the install fails with an error "Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>
I had earlier tested upgrading the MSDE installation to SQL Server 2005 Express Edition Version 9.00.1399.6 downloaded from http://www.microsoft.com/downloads/details.aspx?familyid=220549b5-0b07-4448-8848-dcc397514b41&displaylang=en and the upgrade worked successfully using SQL Authentication (SA User and corresponding password), but for some reason it doesn't work when I use the latest version 9.0.3042.0.
Has anyone else faced similar issues. Any tips on how I can upgrade from MSDE to SQL Server 2005 Express Edition SP2 are welcome.
Thanks in Advance.
Sahil Girotra
View 4 Replies
View Related
Jun 21, 2007
I have a database on one server that is running MSDE and I would like to copy it to another server running SQL Server Express.
The process I followed was to create a backup on the first server.
Copy the backup file to the other sever
Then restore using the backed database file on the new server
Is this the right procedure? Everything I see about migrating in on the same server. I do not want to do it on the same server as we are migrating the application to the new server.
View 4 Replies
View Related
Aug 14, 2006
Is it possible to upgrade from MSDE to SQL Server 2005 Standard Edition?
View 1 Replies
View Related
Jun 28, 2006
I'm trying to upgrade the Default Instance of MSDE 2000 Release A which is installed with Mixed Mode and strong password to SQL Server 2005 Express in a Windows 2000 Server with SP4. On the Upgrade Logon Information screen, if I select SQL Server Authentication Mode, it will give me this message:
SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade.
Thanks for any help.
View 1 Replies
View Related
Aug 1, 2006
I have clients that have the MSDE version installed and we need to upgrade there program to the MSSQL 2005. Is there an easy way to convert the data? Should or Could I uninstall MSDE and than install MSSQL2005 WorkGrp? Will there data be affected? Any tips would be appreciated.Thanks!
View 1 Replies
View Related
Jul 3, 2006
According to this http://msdn2.microsoft.com/en-us/library/ms143393(d=robot).aspx, it seems that it cannot. But is this a complete chart?
Thanks for any help,
Peter
View 5 Replies
View Related
Jan 23, 2007
i am working on upgrading the clients and server computers from 2000 MSDE to 2005 SQL Express Adv. Plan to upgrade using the template.ini.
i can find the version of sql server running on th server by @@version but how do i find the version of client connctivity components the computer has installed in order to ugrade?
1. somehow i need to know whether to upgrade a client computer CONNECTIVITY COMPONENTS from 2000 to 2005?
2. is there a way to enable tcp/ip in installation script of SQL Express?
THANKS
View 9 Replies
View Related
Nov 29, 2006
When attemping to install SQL 2005 Express using the following command line arguments
/qb UPGRADE=SQL_Engine INSTANCENAME=MY_INSTANCE
or
/qb UPGRADE=SQL_Engine INSTANCENAME=MY_INSTANCE SECURITYMODE=SQL SAPWD=MY_PASSWORD
the following error occurs.
Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Edition check:
Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
The following version and editions have been verified.
1. .NET 2.0 installed
2. Windows XP SP2
3. MSDE 8.00.2039(SP4)
4. all MSDE databases are owned by sa
5. Instance and SQLAgent running under user that is member of Administrators
What are the possible reasons this error is occurring?
View 4 Replies
View Related
Nov 10, 2003
I am running the MSDE 2000 Setup off the SQL Server 2000 Developer Edition CD.
After installation is complete, there is a service under the Control Panel -> Services window
called MSSQL$GregInstance. I then start that service.
But now when I try to connect to the database using
osql -E -S GregInstance
I get told that the SQL Server does not exist or access denied. Even though the server is running. I have also tried
osql -E -S localhost
but no luck. Why can it not find the instance of SQL Server?
Note : SQL Server 2000 is not installed on the machine, only this MSDE instance.
Thanks
Greg
View 1 Replies
View Related
May 31, 1999
i installed SQL 7.0 on my 6.5 machine and when install completed and reboot. then the SQL Upgrade Wizard run automatically and after i choose data transfer method(named pipe) and the 6.x server name and 7.0 servername and choose next,then the Upgrade Wizard shows
"Switching to SQL server 7.0 ...."
"Restarting MSSQLserver service ..."
"Gather information from ..."
"Switching to SQL server 6.x ...."
"Restarting MSSQLserver service ..."
then the SQL Upgrade Wizard gives the following msg
"An error occured on "SQL_SERVER",specified SQL server not found ConnectOpen(Creatfile())."
and
"An error occured while trying to querry @@servername on 'SQL_SERVER' please make sure that value is not NULL."
and when i tried to switch to SQL 6.5 mannually the 6.5 service can't start with the same error occured, the enterprise manager says can't connect to server "SQL_SERVER"
my computer have windows nt sp4 and ie4.01 sp1 and SQL 6.5 with sp4 installed.
any ideas?
View 3 Replies
View Related
Jul 2, 2013
We installed the SQL Server 2012 GUI tools, including "Upgrade Advisor," on a new virtual machine. We can connect to the old SQL Server 2008 R2 clustered databases just fine over port 1433 using SQL Server Management Studio 2012, but Upgrade Advisor is a mixed bag. Here are the steps we are taking:
- Click on "Start," "All Programs," "Microsoft SQL Server 2012," "SQL Server 2012 Upgrade Advisor"
- Fill in the server name with a valid SQL Server Network Name
- Select "SQL Server" as the only component to be analyzed
- Fill in the instance name with a valid named instance
- Use Windows Authentication (the default)
- The "SQL Server Parameters" window displays valid database names, meaning that we have a successful connection to the desired SQL Server instance at this point
- Leave all of the databased selected (the default)
- Click the "Run" button
- The "Upgrade Advisor Progress" window spins for a while and eventually generates the following error:
TITLE: mscorlib
------------------------------
The network path was not found.
------------------------------
BUTTONS:
OK
------------------------------
Why would Upgrade Advisor be able to display the database names after making a successful connection only to fail later saying that it cannot find the network path?
View 4 Replies
View Related
Aug 26, 2007
hi
i have some problems with my msde 2000
i notice that my server is quite buzy
and only when i disable the bkupexec instance, the cpu relax
i inteand to update msde 2000 sp3a to sp4
it is recommended?
since as far as i know, backup exec should work fine with sp3.
is there any thing to check of this instance before updating?
thanks
View 10 Replies
View Related
Aug 17, 2007
I am trying to upgrade a default instance of MSDE to Sql Express SP2 using command line parameters. The upgrade keeps failing with the message that another instance of SQL Server exists with that name. I am using the following parameters to indicate the upgrade:
UPGRADE=SQL_ENGINE
INSTANCENAME=MSSQLSERVER
It appears to be doing an install rather than an Upgrade. Anybody have any ideas why it is not executing the UPGRADE parameter?
View 6 Replies
View Related
Jun 1, 2006
Hi,
I'm trying to upgrade MSDE with SP4.
I used the following in command prompt.
setup /upgradesp sqlrun INSTANCENAME=MSDEINSTANCE SECURITYMODE=SQL UPGRADEUSER=username UPGRADEPWD=userpassword /L*v C:MSDELog.log
i got the message "Please go the control panel to install and configure system components."
What does it mean?
How to upgrade it?I have tried to edit the line with *V, and using the sa username and password, but i get the same message.
RegardsKenneth Davidsen
View 1 Replies
View Related
Feb 5, 2007
Hi!
Here's the scenario:
I have a MSDE 2000 installation running, already patched to SP3. Instancename is "STO". I've downloaded SQL2000.MSDE-KB884525-SP4-X86-ENU.exe and extracted the archive to C:SQL2KSP4.
After starting setup from the command prompt with "setup /upgradesp sqlrun DISABLENETWORKPROTOCOLS=0 /L*V C:MSDELog.log" i get a message box, telling me "The product is not installed". This happens even if I specify the exact instancename and supply the sa user and pwd!
Any ideas?`
Thanks in advance and regards
Clemens
View 3 Replies
View Related
Feb 7, 2004
I just upgraded for MDSE 1 (came with VB 6 Pro and inculded Enterprise Manager) to MSDE 2000. After the upgrade, Enterprise Manager was removed.
Is there an Enterprise Manager availble for MSDE 2000, or a similar tool out there?
Thanks for any help.
Greg
View 3 Replies
View Related
Jun 14, 2004
I just upgraded my desktop engine MSDE 1.0 to MSDE 2000 SP3a. Everything seemed to go well, MSSQLSERVER AND SQLSERVER Agent Services are running, problem is, I can no longer see the particular instance on the network from Enterprise Manager.
The installation instructions specified that if the Instance was to accept connections from applications on other computers not to specify the DISABLENETWORKPROTOCOLS parameter, so I didn't.
I'm a little green with this, can anyone suggest a place to start troubleshooting?
View 1 Replies
View Related
Nov 8, 2006
I have just done an in-place upgrade from MSDE to SQL Express with Advance Services for my customer. After upgrading, the program was not enable to connect to SQL Express and threw an error (the program connect to the server through OLEDB provider)
Code -2147217843 (80040e4d) - IDispatch error #3149 - Source : Microsoft OLE DB Provider for SQL Server
It only works if I replace the string "Provider=SQLOLEDB.1" with "Provider=SQLNCLI.1". I wonder why I have to do that because in my working PC and other customers, I don't get this.
The customer's PC use Windows 2003 Server for Small Business Server SP1
Thanks in advance
Huy Le
View 4 Replies
View Related
Aug 9, 2004
Hello,
I recently upgraded my MSDE server to SQL Server 2000 database. After the upgrade, I see, every minute,in the logfile that the database is starting whilst in Enterprise manager the database is up and running. I would be grateful if you could bail me out of this anomaly.
Hope to hear from you soon.
Regards,
Albert.
View 2 Replies
View Related
Jan 29, 2007
I need to create the script to upgrade the current named instance of sql 2000 desktop engine to sql server 2005 express edition. I am having difficulty preparing the template.ini and would appreciate help.
[Options]
INSTANCENAME=MY_INSTANCE
SQLBROWSERACCOUNT=NT AUTHORITYNETWORK SERVICE
SECURITYMODE=SQL
SAPWD=music
UPGRADE=SQL_Engine
SQLBROWSERAUTOSTART=1
RSCANINSTALLDEFAULT=0
RSCONFIGURATION=FilesOnly
RSSQLLOCAL=0
I get an error that this file is invalid..Any clues? I am trying to upgrade existing instance of msde 2k to sql express 2005 and uses sql authentication
View 2 Replies
View Related
Feb 8, 2007
Hello,
I have the following scenario. An application using SQL Server 2000 SP3 on the server side and clients using MSDE 2000A (SP3a) on the client machine. Since the client is offline quite often merge replication is used to keep the clients in sync.
Now we try to upgrade to SQL Server 2005 SP1. The publisher and distributor upgrade (on the same box) worked fine and all clients could still synchronize. Fine :-)
Now we try to upgrade the clients to SQL Express SP1. Now the problems start :-(
1) After the upgrade the entry within the Synchronization Manager is gone (we can overcome this by using sp_MSregistersubscription or by manually disable and enable Synchronization manager on the subscription properties)
2) Initial Synchronization (takes a long time but) works fine, if I apply changes to the subscriber or force a reinitialize all following synchronization will fail. With the following messages:
Error messages:
The merge process could not clean up the subscription to 'tstvmw23':'TestBase:'TestBase'. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200965)
Get help: http://help/MSSQL_REPL-2147200965
New request is not allowed to start because it should come with valid transaction descriptor. (Source: MSSQLServer, Error number: 3989)
Get help: http://help/3989
Remark the test system I use is a nearly empty db (only with full schema and a few lookup tables) with 15MB. The same error occures if I create a new database an subscribe to the same publication.
Please help otherwise I'm forced to step back to MSDE.
Thanks in advance,
Thomas Hotz
View 3 Replies
View Related
Jan 19, 2007
Hi,
We are performing a SQL 2005 SP1 upgrade from SQL 2000 on our Windows 2003 SP1 Standard Edition.
When we run the upgrade, we got a error "Upgrade Advisor Return -1" as a pop-up window.
When we run the Upgrade Advisor separately, we get this error :
===================================
Common Language Runtime detected an invalid program.
===================================
Common Language Runtime detected an invalid program. (System.Xml)
------------------------------
Program Location:
at System.Xml.Schema.SchemaInfo..ctor()
at System.Xml.Schema.XmlSchemaSet..ctor(XmlNameTable nameTable)
at System.Xml.XmlReaderSettings.get_Schemas()
at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReportController.LoadAndValidateDataFile()
at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAReport.ValidateDataFile()
at Microsoft.SqlServer.UpgradeAdvisor.ReportViewer.UAIssueReport.Refresh()
at Microsoft.SqlServer.UpgradeAdvisor.ReportPanel.OpenReport(String reportFile)
We are in a lost for solutions. We do hope to hear from anyone asap...
Greatly appreciated for any kind assistance.
Thanks.
View 1 Replies
View Related
Feb 10, 2007
Hi,
We are running a test upgrade form sql 2000 standard edition 32 bit to sql 2005 developer edition 32bit. Followed through all the steps and specified the account(SA priveleges and currently used by the 2000 version) and is the local admin on the box for the services and the setup seemed to move fine, except for when it got to the point of installing database services - This is the error message that I got:
MSSQLServer could not be started. Verify you have sufficient priveleges to start system services. The was no choice but to hit cancel and then the set up progressed with a final message of 'SEtup failed'.
Here is a portion of the error log:
Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
Database Mirroring Transport is disabled in the endpoint configuration.
Starting up database 'master'.
Converting database 'master' from version 589 to the current version 611.
Database 'master' running the upgrade step from version 589 to version 590.
Error: 946, Severity: 14, State: 1.
Cannot open database 'master' version 589. Upgrade the database to the latest version.
System Task Aggregate global counters produced an error that was not handled. Major: 9, Minor: 46, Severity:14, State:1
Error: 928, Severity: 20, State: 1.
During upgrade, database raised exception 15151, severity 16, state 1, address 01C4C50B. Use the exception number to determine the cause.
Error: 15151, Severity: 16, State: 1.
Cannot find the endpoint 'TSQL Local Machine', because it does not exist or you do not have permission.
Any help would be greatly appreciated
Thanks KR
View 7 Replies
View Related
Dec 27, 2006
After my upgrade from MSDE SP 4 to SQL express (backup and restore) my application will not see the data any more.
If I use my application (VB Dot.NET 1.x ; DB= SQL Express) to add new data (rows) this new rows are visible.
Both old and new datas are seen in SQL management studio express.
If i add rows with the SQL management studio express the appliction will not see this rows.
In both cases I connect with sa - account. (Administrator even doesn't work). I search for any restrictions on row basis but i wonder why the management tool display all rows.
Any ideas!
View 1 Replies
View Related
Oct 26, 2006
We have 3 MSDE databases (3 seperate servers) which we need to make into one Sql 2000 server (new server). How is this done? Can't find anything clear about this.
Thanks
View 3 Replies
View Related
Jul 4, 2007
I did:
select city, count(*) from classifieds_address group by city
You would think it would distiguish between "Koh Phangan" and "Koh Phangan ". No!!! It shows them as one row in SQL!!! Is this SQL bug?
Aberdeen 1bayombong 1Brooklyn 4Castle Peak Bay 1Causeway Bay 2Chiang Mai 1Hong Kong 1Hong Kong Wan Chai 1Hong Kong Island 10Hong Kong Sheung Wan 1Karachi 1Koh Phangan 21Koh Samui 37Koh Tao 9Kowloon 13Kowloon, Tsim Sha Tsui 1Lantau Island 1Mid-Levels 3New Territories 2New York 3North Point 1Oligar 1Tsim Sha Tsui 1Wan Chai 5Yau Ma Tei 1Yau Ma Tei, Kowloon 1
View 5 Replies
View Related
Jan 18, 2006
I have uninstall MS SQL 2000 and installed MS SQL 2005, but i cant find nowhere the service manager to run the server
where is it ?
thank you
View 4 Replies
View Related
