Viewing 15 posts - 1,036 through 1,050 (of 1,109 total)
There are stored procedures and extended stored procedures in SQL Server that are not part of the documentation and are not supported by Microsoft. They may disappear in future versions...
August 23, 2007 at 8:06 am
I was wondering about this too, but I thought that well designed schemata have proper domain restrictions. Reducing the size then makes sense. (But I'm just guessing what Aravind's motivation...
August 23, 2007 at 8:01 am
This is actually a limitation of the EXECUTE statement. It can take values and variables only. See ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/bc806b71-cc55-470a-913e-c5f761d5c4b7.htm
Regards,
Andras
August 23, 2007 at 7:54 am
You cannot use a function in the parameter list of sp_updateextendedproperty. You can get around this by declaring a variable of datetime type, and then using this variable in the...
August 23, 2007 at 7:43 am
Hi Andy,
you are right that SSMS can do this in many cases. (I actually did not know this, but it is nice to learn new things). On the other hand...
August 23, 2007 at 6:59 am
It should be as it is in your first screenshot. The second screenshot shows a configuration that is a bit messed up. The server name should be only "Intai", instead...
August 23, 2007 at 5:10 am
For your first question, whether there is something to keep track of new or altered rows, the answer is likely to be about transaction logs. You can read about it...
August 23, 2007 at 3:48 am
This has changed for SQL Server 2005. You now need to use the setup to rebuild system databases. See http://msdn2.microsoft.com/en-us/library/ms143269.aspx
Regards,
start /wait setup.exe /qn REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=-New...
August 23, 2007 at 2:59 am
By default CLR stored procedures cannot do whatever they want in the database. E.g. they cannot pop up a dialog window, etc. This is achieved via code access security. If...
August 23, 2007 at 1:53 am
Since the datatype is the same, you can just use an alter column statement like:
ALTER TABLE [dbo].[alma] ALTER COLUMN [a] [varchar] (30)
However, if the column is part of a primary...
August 23, 2007 at 1:31 am
If you want to do this from inside the database, you would need to allow and use unsafe assemblies in your database. Also, you would probably need to add all...
August 22, 2007 at 11:35 am
You cannot just edit the identity setting for a column. You will need to rebuild the table for that. So basically when you added the column you could not have...
August 22, 2007 at 11:24 am
Table partitioning would have the advantage that individual partitions will have their own indexes, so the cost of deletes will be lower. Of course this is a solution for the...
August 22, 2007 at 10:32 am
nchar and nvarchar columns will have no problems storing these characters. However storing could be a problem. This will affect you if you have any clustered indexes set up on...
August 22, 2007 at 6:04 am
In the case you do run out of ints, moving to bigint would require you to rebuild the table. Generally this would involve creating a temp table, moving the data...
August 21, 2007 at 11:16 am
Viewing 15 posts - 1,036 through 1,050 (of 1,109 total)