When we migrated from SQL 6.5 to 7.0 our users that had DBO privileges moved fine. When we went in and added a new user and tried to give them the same priviledges as the old user, the user looks different and does not have the same priviliges. When the user tries to run the SETUSER stored procedure it tell the user that was newly setup that they do not have the rights to perform the operation. Any help with be greatly appreciated.
Running MSSQL 2000 on Windows2000 in an NT domain. We have several jobs created by the web assistant wizard. They run along just fine for days or weeks, then all of a sudden SOME of them (?!) begin to fail with the message "Unable to perform a SETUSER to the requested username 'dbo' because the username is invalid for database 'xxx'" where xxx is of course the db where the proc resides. SQLAgent service is running as a domain admin and has not changed; job is owned by sa and has not changed; the domain admin in question is in sa role and has not changed. Something sure has changed, but what? Sometimes when this happens we can clear it up by deleting the web job and simply re-creating it. Today we have three culprits and none of our usual tricks are working. Why does this happen? How can we fix it? How can we PREVENT it! Thanks for any words of wisdom out there.
We have 2 servers when you try to change something in a transfer for sql to a text file, it crashes and kicks you out of enterprise manager. I have seen this before. MS recommends applying sp4 or MS03-031: Cumulative Security Patch for SQL Server (815495) This is on a cluster. Has anyone seen this before
We are network admins at a college, with no database experience at all. We use an Altiris product which uses SQL to maintain a database. Our database is OK, but the transaction log has grown to 24 Gb and has caused a slowdown. When we try to back up the database in preparation for shrinking it to the recommended 100 Mb, the server seems to start the backup but crashes (restarts) after a few minutes. Has the situation got out of hand i.e. with files so big, is our server never going to be able to work with it? Or are we missing something obvious?
Any information on resolving the situation gratefully received, thanks in advance.
I am using the DTS wizard to import tables from an AS/400. Some of the tables in the job are quite large and Sql Server either hangs up or completely crashes. My current configuration is WIN NT, SP4.0 SQL Server 7.0 no Service pack. Any suggestions?
I've jumped over from the sister site xtremevbtalk.com to ask the question:
Has anyone ever seen an issue where when installing MSDE, during the installation the pc reboots of its own accord?
After the MDAC is installed as part of the installation the pc reboots and upon boot up, MSDE is not in the program files directory. Instead it's sitting in the C: root. This occurs for a straight MSDE install or with an Instancename install.
There does exist a Microsoft SQL Server folder in the Program Files but it is incomplete. It's missing the Binn folder. Also, there is no reference to MSDE in the Add/Remove programs tool but ther MSDE service does show up in the Services. However I cannot start these as they are pointing to the correct location.
To date, I have tried removing the instance and installation from the registry. I have turned off all AntiVirus software. I have ensured I am using an Admin user profile. I have tried a blank sa passowrd for the installation. all of this is to no avail.
I am seriously stuck with this now and I am in dire need of a resolution so if anybody has any ideas or has seen this one before, I love some help.
I can open a single connection to the database engine successfully but if I try to open another connection ('New Query' or 'query with current connection') Management Studio just goes away without any errors.
I am utilizing a remote desktop connection to the server but if I open a connection from my desktop through Management Studio I can establish multiple connections (database engine, query, etc...) with no problems. There are no errors in the sql logs, event viewer or windows log.
Has anyone seen this? Any suggestions would be appreciated.
My application uses sqldmo to retrieve the list of sql servers in thenetwork, it works fine in some machines, but it is crashing theapplication in others, no error and no exception, it shuts down theapplication. It fails in the following line:SQLDMO.NameList sqlServers = sqlApp.ListAvailableSQLServers();any ideas?thanksmusachy
I was looking to improve the performance of an ASP.NET application bycreating the an indexed view that could be used instead of some of theroot tables.What I didn't realize is that it would affect any future conenctionsto the root tables.This of course crashed the application on any type of insert, update,or delte from the root tables.Funny thing is when I removed the indexed view -- it didn't help.I tried flipping the offending options to the opposite of way theywere set on the database and the errors wouldn't go away.I ended up restoring the database from before my mess up to fix it.I was hoping that the SQL experts out there might shed some light onmy problem before I try again.
Currently we have SQL Server running on a single RAID5 array.The data and the logs are all written to this array. We don'thave huge volume of activity, but it is growing. Most activityis from our website that interacts a lot with the database.We have read that it is a good idea to separate the data filesfrom the log files, having each on separate disks (or in thecase of RAID, separate arrays). So, we are considering addinga separate SCSI hard drive, or maybe a RAID 1 system, and havesql server log to that instead.My question is, what happens if that secondary drive or arraycompletely fails. Let's say it melts. Assuming the OS doesn'tcrash (Windows 2003 Server), what will SQL Server 2000 do whenthe drive stops working and it is trying to write its datalogging to it? Will it continue to function and write alertevents? Will it shutdown? If it shuts down, how do we alter itsconfiguration to tell it to use another drive for the logs?Also, what kind of throughput would we need to be doing to seeany kind of benefit to making this change? It is easier tojustify the expense of another disk or RAID setup if it isactually going to matter. ;-)Thanks all!Thomas
I'm using SQL 2005 Reporting services on Windows 2003 server, my development machine is Windows XP Pro. Attempting to report from a Progress 10.0B database with the DataDirect 4.2 SQL92 driver.
A simple static query executes brilliantly (i.e. SELECT Col1 FROM Tab1 WHERE Col1 = 200) When I change the named parameter to an unnamed (i.e. SELECT Col1 FROM Tab1 WHERE Col1 = ?), then execute the query I'm prompted for the parameter value, I enter a valid value, then receive the error: "Attempted to read or write protected memory. this is often an indication that other memory is corrupt." Then VS crashes. obviously this is bothersome.
An ODBC trace shows the SQL statement (SELECT Col1 FROM Tab1 WHERE Col1 = ?), note: the parameter value I entered is not in the trace. Should it be?
I have created a calculated data field for one of my data set. I use it for a table in my report. But when I try to preview it, visual studio crashes and I get the following error message.
"An error occured during local report processing. An internal error occured on the report server.see the error log for more details."
I have not installd servers on my machine(only the sql tools). So I can not see error logs either.
Every time I do a full backup of my databases, it will go through most of them, then get to the largest database I have (13 Gig) which is the Sharepoint database, and as it starts to back it up, the machine will then freeze up and need to be hard rebooted. I confirmed it was the backup by moving the backup to a different time, which is when the server crashed. Also, if I manually attempt to do a full backup on it, the machine will then crash.
I'm running Windows Server 2003, SP2, fully patched, SQL server 2005 SP2 (32-bit) fully patched. 4 Gigs memory. Have tried setting it to use 3 Gig itself, with and without AWE, but it didn't make a difference. This machine is a dedicated SQL Server machine. Microsoft has had us run perfmon and send them perfmon reports and dumps. They don't see anything that would cause our issues. Nothing shows up in the event viewer. This server has been running just fine since last June when we installed SQL 2005. The problems started occurring on March 8 of this year. I don't see any patches that correspond to that date.
Hardware is all reporting fine according to the Gateway Hardware tool.
I'm the Sharepoint Admin, we have no SQL Admin, so now this is another job of mine. So any advice, anything I should look for, would be extremely helpful.
Will the database get locked if my ASP.Net application that is calling a stored procedure in which a HOLDLOCK for table1 is issued to SQL Server, suddenly crashes just after the stored procedure is called?
I ran a DBCC SHOWCONTIG on a large database. Because the execution was taking longer than I wanted I cancelled and then killed the process running the DBCC. This action seems to have abnormally ended SQLServer and subsequently crashed the entire NT server. Have you experienced any behavior similar to this when using DBCC and/or killed processes?
I am creating an SSIS Package to import some data. The package contains a big for each loop with 3 parallel running nested for each loops. The package crashes within the big loop without returning any error information. It starts up the sqldumper and genreates an dump - but does not report any error to the UI (Visual Studio or dtexec). While I am running only one for each loop and disable the others the package executes successfully. Has anyone an idea what might be wrong ? or is the only chance to submit a bug report ?
I'm trying to use a user defined alias type in a table creation, and everything works as expected, right until the moment where I rightclick on [Indexes] and click [new index] to create a new index.
Then I get this error:
TITLE: Microsoft SQL Server Management Studio ------------------------------ Cannot show requested dialog. ------------------------------ ADDITIONAL INFORMATION: Cannot show requested dialog. (SqlMgmt) ------------------------------ Object reference not set to an instance of an object. (SqlManagerUI) ------------------------------ BUTTONS: OK ------------------------------
When I try to manually run one of my scheduled job, DR. Watson comes up and SQL Server crashes. the following error message is received in the NT event log. "Unable to read local Event log, reason the data area passed to a system call is too small". I am new to SQL and this is causing me some degree of stress!!!! Also please recommend a good book for a newbie like me.
i didnt think my sql qeury was that complicated that it would crash my webapp. all im trying to do is filter data between two tables. heres my query<cfquery name="GetResults" datasource="#datasource#">SELECT *FROM Content, Content_SitesWHERE Content.ContentID <> Content_Sites.ContentIDORDER BY Content.ContentID DESC</cfquery>equals works, but when i try not equals, it all goes haywire. any ideas?TIA
Hello,I am having a problem when using access xp as a frontend for sql server2000.I have been trying to update a number of stored procedures (Just simpleadding fields etc) which results in access crashing with event ID 1000 and1001.Does anyone have any ideas as to what could be the problem?Thanks in advance..
I have a package with numerous data flows in it. (I know - this is not recommended as a best practice.) Anyway, one of the Data Flows just started giving me some trouble. When I opened that particular Data Flow, then BIDS would crash. I tried loading the project again, and opening that Data Flow task, and it just kept crashing. I rebooted - same deal.
The Data Flow was itself very simple. There was an OLE DB Source, and OLE DB Destination, a conditional split, a derived column, a data conversion and a Lookup. Pretty routine stuff. Out of the blue really, and long after I created it - it just starting crashing BIDS when I opened it.
My solution was to copy the Data Flow control flow component and paste it back into the same package. This worked perfectly fine, and didn't see any issues after. So, apparently something in the meta data became corrupt, and caused it to crash.
Anyway, just curious if others have seen this behavior, but also wanted to post this as a solution in case someone else has the same problem.
I'm stuck here when I try to open an existing package which contains several data flows, SSIS tries to validate each data flow and after a while a Visual Studio error message pops up and I can't do anything.
The error message says : "Unable to cast COM object of type 'System._ComObject' to interface type 'Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSObject90'. This operation failed because the QueryInterface call on Com component for the interface with IID '...GUID...' failed due to the following error : The application called an interface that was marshalled for a different thread. (Exception from HResult: RPC_E_WRONG_THREAD)"
I have an application that manage an sql srever compact edition database it worked OK until I got the following problem: Only when debuging the application ("Start Debugging" from visual studio). In the first call to an sql server routine I get an exception "Unspecified error [ sqlceqp30.dll ]"
I am seeing repeated failures installing SP1 database services with crashes in hotfix.exe being reported and the following appearing in log files:
Property(S): SqlUpgradeMessage = SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again. Property(S): UpgradeInstruction = Connect to SQL instance ZENO as sysadmin Launch SQL statement USE master Launch script file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstallsysdbupg.sql Launch script file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstallDbEngine_hotfix_install.sql Launch script file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall epl_hotfix_install.sql Stop service MSSQLSERVER MSI (s) (38:80) [09:35:35:246]: Product: Microsoft SQL Server 2005 - Update 'Service Pack 1 for SQL Server Database Services 2005 ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log.
I have configured a Un-Pivot transform, source to unpivot is sort, when I change the source to derived column (one column name is same for both) and try to open Unpivot it gives me unreferenced lineage id (this is correct). Now When I select Delete Unreferenced Lineage Column and select Apply , it works till here. As soon as I select OK, BIDS crashes and closes.
Hello,I need some help with SQL Server 2000 SP4. I've been using thedeveloper product for a few years now on my PC with very few problems.Today when I try to start up Enterprise Manager, it crashesimmediately. I get the usual "Please tell Microsoft about this problem"dialog and if I click the 'click here' link, I'm presented with adialog that says:-------------------------------------------------Error signatureAppName: mmc.exe AppVer: 5.1.2600.2180 ModName: mmc.exeModVer: 5.1.2600.2180 Offset:0001f07eReporting detailsThis error report includes: blah, blah, blah...-------------------------------------------------I am running Windows XP with SP2. Also installed is Visual Studio 2003,Visual Studio 2005, and SQLServer 2005 (We're in the process ofmigration).All of these products have been running OK together for at least amonth until today. I'm not sure what changed, but obviously somethinghas. I tried uninstalling and reinstalling SQLServer 2000 & it's SP4,but no luck. Enterprise Manager still crashes immediately when I try tolaunch it.Could somebody please help me out?Thanks.
We have successfully built a SSIS ETL implementation for a data mart. Most of our dimension loads are using the slowly changing dimensions task. We successfully built every package and had 1 complete successful load.
We have made a modification to one of the tables that now has 16 mil records in it. I open the dimension's package and it takes 30 sec - 1 minute to validate. When I go to the Data Flow tab and attempt to open the Slowly Changing Dimension task, SSIS will freeze up. I will get no response for hours. I my testing so far SSIS has yet to come back.
My CPU usage is below 5%. devenv.exe memory usage is at 113 Mb. My computer is using 400mb / 1Gb of memory. The status bar at the bottom says "ready". I have let it sit for up to 2 hours with no results. When I kill the process in the Windows Task Manager it ends instantly.
I have also tried deleting the task and adding a new Slowly Changing Dimension Task. When I select the table from the drop down I get the same results. I have noticed this with all my million + record tables that use the slowly changing dimension task but not the smaller tables. I am also seeing the problem when I am in "Work Ofline" mode.
I am accessing a SQL 2005 server over a VPN connection. I am connecting to the server using a Native OLE DB OLE DB for SQL Server connection. My computer is running Windows 2000 SP4, Intel Pentium M1.86 Ghz, 1 Gb of RAM.
Can a Slowly Changing Dimension Task be used on large tables? I can understand the process taking a while to run but I do not understand why I can not edit the task.