SQL Server Profiler: File → New Trace The “General” Tab is displayed. Here you can choose “Save to file:” so its logged to a file. View the “Event Selection” Tab Select the items you want to log. TSQL → SQL:BatchStarting will get you sql selects Stored Procedures → RPC:Completed will get you Stored Procedures. More … Read more
Open the design table tab Highlight your two INT fields (Ctrl/Shift+click on the grey blocks in the very first column) Right click -> Set primary key
Go into Tools -> Options -> Designers-> Uncheck “Prevent saving changes that require table re-creation”. Voila. That happens because sometimes it is necessary to drop and recreate a table in order to change something. This can take a while, since all data must be copied to a temp table and then re-inserted in the new … Read more
If the table is already created in the database, then you can add a unique constraint later on by using this SQL query: ALTER TABLE dbo.User ADD CONSTRAINT ucCodes UNIQUE (fcode, scode, dcode)
Open up SQL Server Configuration Manager (search for it in the Start menu). Click on SQL Server Services. The instance name of SQL Server is in parenthesis inline with SQL Server service. If it says MSSQLSERVER, then it’s the default instance. To connect to it in Management Studio, just type . (dot) OR (local) and … Read more
127.0.0.1,6283 Add a comma between the ip and port
So your C# code is sending an ad hoc SQL query to SQL Server, using what method? Have you considered using a stored procedure? That would probably ensure the same performance (at least in the engine) regardless of who called it. Why? The ARITHABORT setting is one of the things the optimizer looks at when … Read more
SqlPubwiz has very limited options compared to the script generation in SSMS. By contrast the options available with SMO almost exactly match those in SSMS, suggesting it is probably even the same code. (I would hope MS didn’t write it twice!) There are several examples on MSDN like this one that show scripting tables as … Read more
From Save (Not Permitted) Dialog Box on MSDN : The Save (Not Permitted) dialog box warns you that saving changes is not permitted because the changes you have made require the listed tables to be dropped and re-created. The following actions might require a table to be re-created: Adding a new column to the middle … Read more
Chances are that you are hitting on a problem with parameter sniffing. I suggest reading Slow in the Application, Fast in SSMS? by Erland Sommarskog to get a full understanding of the issue (long article but very good).