|
|
-
RAM Liked 2 Years ago through Just Learned | 1 Point
Careful! If you are using your old scripts to create database in SQL 2012, It might fail. In SQL Server 2012, Minimum database size is increased to 3MB. In before versions it is 2MB. So, if you run the same script with initial size specified as 2MB, it ...
|
-
RAM Learned 2 Years ago through Just Learned | 1 Point
Careful! If you are using your old scripts to create database in SQL 2012, It might fail. In SQL Server 2012, Minimum database size is increased to 3MB. In before versions it is 2MB. So, if you run the same script with initial size specified as 2MB, it ...
|
-
RAM Learned 2 Years ago through Just Learned | 1 Point
Careful! If you are using your old scripts to create database in SQL 2012, It might fail. In SQL Server 2012, Minimum database size is increased to 3MB. In before versions it is 2MB. So, if you run the same script with initial size specified as 2MB, it ...
|
-
RAM Liked 2 Years ago through Just Learned | 1 Point
Careful! If you are using your old scripts to create database in SQL 2012, It might fail. In SQL Server 2012, Minimum database size is increased to 3MB. In before versions it is 2MB. So, if you run the same script with initial size specified as 2MB, it ...
|
-
RAM Liked 2 Years ago through Just Learned | 1 Point
Careful! If you are using your old scripts to create database in SQL 2012, It might fail. In SQL Server 2012, Minimum database size is increased to 3MB. In before versions it is 2MB. So, if you run the same script with initial size specified as 2MB, it wil
|
-
RAM Liked 2 Years ago through Just Learned | 1 Point
During working with replication, encountered with one error to use actual server name for replication. For solution we need to change the SQL Server instance name as actual server name with following,
[CODE]
EXEC sp_dropserver 'Old Server Name'
EXE...
|
-
RAM Learned 2 Years ago through Just Learned | 1 Point
During working with replication, encountered with one error to use actual server name for replication. For solution we need to change the SQL Server instance name as actual server name with following,
[CODE]
EXEC sp_dropserver 'Old Server Name'
EXE...
|
-
RAM Liked 2 Years ago through Just Learned | 1 Point
During working with replication, encountered with one error to use actual server name for replication. For solution we need to change the SQL Server instance name as actual server name with following,
[CODE]
EXEC sp_dropserver 'Old Server Name'
EXE...
|
-
RAM Learned 2 Years ago through Just Learned | 1 Point
During working with replication, encountered with one error to use actual server name for replication. For solution we need to change the SQL Server instance name as actual server name with following,
[CODE]
EXEC sp_dropserver 'Old Server Name'
EXE...
|
-
RAM Liked 2 Years ago through Just Learned | 1 Point
During working with replication, encountered with one error to use actual server name for replication. For solution we need to change the SQL Server instance name as actual server name with following,
[CODE]
EXEC sp_dropserver 'Old Server Name'
EXEC s
|